Semantic Reader MCP server

• Registry namedev.semanticreader/semantic-readerverified in the MCP registry

The registry name sits under semanticreader.dev. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-26
• Tools12
• Server calls itselfsemantic-reader
• Server version0.3.0
• Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 18 ms.

• Its tools do every use case we checked: find who calls a function across supplied files; look up symbol definitions and types; check diagnostics for supplied TypeScript or JavaScript files.
• Checked on 2 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
• What an agent can do with it3 of 3 use cases
• Answeredmeasuring2 of the 7 daily checks it takes to print a share
• Median first answer792 ms
• Space in an agent's context≈ 3,084 tokensthe definitions of all its tools (12), which an agent carries on every turn
• Tool definitionsB · 85 of 100
• Typed results12 of 12 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 11 of 12

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• open_snapshot

  Store supplied source files ephemerally and return an opaque snapshot handle for reuse.

• get_capabilities

  Return Semantic Reader capabilities, limits, billing and discovery facts.

• find_symbol

  Resolve a symbol name to deterministic ranked compiler symbol candidates; safely reports ambiguity.

• get_definition

  Return the compiler-resolved declaration for one supplied-file symbol.

• get_type

  Return TypeScript type facts and call/construct signatures for one declaration.

• get_diagnostics

  Return bounded TypeScript syntactic and semantic diagnostics for supplied files.

• get_symbol_context

  Return bounded definition/callers/callees context; references or impact request paid depth.

• query_code

  Free navigation for symbols, callers, callees or function facts.

• find_references

  Return semantic static references to one exact compiler symbol.

• get_imports

  Return static imports made by one supplied file.

• get_importers

  Return supplied files that statically import one target file.

• analyze_impact

  Return bounded reverse-caller impact for one exact compiler symbol.