Slang-backed SystemVerilog filelist analysis over MCP
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"flist-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# flist-mcp [](https://github.com/Bigyin1/flist-mcp/actions/workflows/ci.yml) [](https://codecov.io/gh/Bigyin1/flist-mcp) [](https://pypi.org/project/flist-mcp/) [](https://github.com/Bigyin1/flist-mcp/tags) [](https://www.python.org/) [](https://docs.astral.sh/uv/) [](https://docs.astral.sh/ruff/) [](https://mypy-lang.org/) [](LICENSE) `flist-mcp` is a Slang-backed MCP server that helps coding agents construct SystemVerilog filelists. Given one or more top modules, it discovers the reachable compilation closure, returns package and source files in topological order, finds include roots, reports ambiguous definitions, and exposes diagnostics and focused dependency graphs. Slang remains the source of truth for parsing, elaboration, diagnostics, and dependency ordering. The server does not parse RTL with regular expressions, invent its own topological order, or emit a build-system-specific manifest. ## Features - Iterative resolution of duplicate module, interface, and package definitions. - Automatic discovery of unique repository-local include roots. - Explicit resolution when several headers satisfy the same include path. - Separate topological `package_order` and `source_order` filelists. - Diagnostics, missing includes, undefined design macros, and unresolved external symbols. - `full`, elaborated `rtl`, and compact `external` dependency graph v…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.