pickfit

BrowseMCP servers

gyrfalcon

MCP server that indexes 1C:Enterprise BSL configs for code navigation and metadata search.

Tested on LinuxKnown vulnerabilities

Use it

Before you install: known vulnerabilities

pickfit found 6 known high or critical vulnerabilities in the packages a fresh install brings (OSV.dev, 3 Nov 2026). Weigh this before you install it.

  • crates:zip 2.4.2 zip: Critical Parser Differential & Security Control Bypass via Dual-Header Inconsistencies (Zip Cloaking) Leading to Arbitrary File Overwrite & RCE (GHSA-m665-v7pm-7grj, critical, fixed in 9.0.5)
  • crates:quick-xml 0.37.5 Quadratic run time when checking a start tag for duplicate attribute names (RUSTSEC-2026-0194, high, fixed in 0.41.0)
See 4 more

Linux x86_64

These steps ran from a folder named work in the home folder, which already existed. Make it and run them from there:

mkdir -p "$HOME/work" && cd "$HOME/work"
  1. git clone the repository and cargo build --release (about 73 s, no errors)

    cd "$HOME"/work && git clone --depth 1 https://github.com/aleksandrgradoboev-svg/gyrfalcon && cd gyrfalcon && cargo build --release
  2. copy target/release/gyrfalcon to ~/.local/bin so it is on PATH

    mkdir -p ~/.local/bin && cp "$HOME"/work/gyrfalcon/target/release/gyrfalcon ~/.local/bin/ && gyrfalcon --version
Verified in pickfit: the commands exactly as its sandbox ran them

For the record only: they name the sandbox's home, /home/sbx.

cd /home/sbx/work && git clone --depth 1 https://github.com/aleksandrgradoboev-svg/gyrfalcon && cd gyrfalcon && cargo build --release
mkdir -p ~/.local/bin && cp /home/sbx/work/gyrfalcon/target/release/gyrfalcon ~/.local/bin/ && gyrfalcon --version
mkdir -p ~/.local/bin && cp /home/sbx/work/gyrfalcon/target/release/gyrfalcon ~/.local/bin/ && gyrfalcon --version
cd /home/sbx/work && gyrfalcon install --plan

Check that it works

mkdir -p ~/.local/bin && cp "$HOME"/work/gyrfalcon/target/release/gyrfalcon ~/.local/bin/ && gyrfalcon --version

The output should contain “gyrfalcon 0.1.25”.

First thing to try

cd "$HOME"/work && gyrfalcon install --plan

Add it to your agent

claude mcp add gyrfalcon -- gyrfalcon serve --db config.db
JSON for Claude Desktop, Cursor and other clients
{
  "mcpServers": {
    "gyrfalcon": {
      "command": "gyrfalcon",
      "args": [
        "serve",
        "--db",
        "config.db"
      ]
    }
  }
}

What it does

  • Call graph with resolution class
    Tested
  • Index a full 1C configuration
    Not shown working
  • Extension intercepts with both addresses
    Not tested
  • Data composition schemas in index
    Not tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Connects
  3. 1 of 4 features work
  4. Works offline

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

An MCP client called one of its tools

  • Replayed from scratch
  • Works offline
  • Checked on 16 Nov 2026
  • Version gyrfalcon 0.1.25

An MCP client handshake over stdio listed 19 tools, and a call to object returned a result.

Differences the test machine hit

  • README: Скачать готовый бинарь / gyrfalcon build <путь к src> --out config.db (1C configuration export required)
    In the test: Built from source with cargo (no network needed at build time beyond crates). Index was built from a tiny synthetic 1C dump written by hand (one common module), because the real export is not available in this box. The server needs a built --db file before it starts.
  • README: gyrfalcon serve --db config.db
    In the test: Works once config.db exists (built with gyrfalcon build). Not tested with a real 1C configuration.
  • README: Сборка из исходников: нужен свежий стабильный Rust
    In the test: cargo build --release succeeded with the box's Rust toolchain in about 73 s.

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.