Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Priority — TypeScript Compiler Intelligence

REMOTE · SEMANTICREADER.DEV · SCANNED SEP 29

Stateless TS/JS compiler facts for agents: references, imports, impact. No repo index or OAuth.

+3 this week 66 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1378 tokens (~114/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
  • Stability check failed: schema churn in the 16 days we've observed: 0 tool removals, 4 breaking changes, 0 auth/transport breaks, 6 additions. See how to fix → Fail
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Priority — TypeScript Compiler Intelligence MCP server?

Priority — TypeScript Compiler Intelligence is a hosted endpoint at https://semanticreader.dev/mcp/registry, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · semanticreader.dev

# add to Claude Code
claude mcp add --transport http dev-semanticreader-semantic-reader 'https://semanticreader.dev/mcp/registry'
// .cursor/mcp.json
{
  "mcpServers": {
    "dev-semanticreader-semantic-reader": {
      "url": "https://semanticreader.dev/mcp/registry"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "dev-semanticreader-semantic-reader": {
      "type": "http",
      "url": "https://semanticreader.dev/mcp/registry"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.dev-semanticreader-semantic-reader]
url = "https://semanticreader.dev/mcp/registry"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-semanticreader-semantic-reader": {
      "type": "remote",
      "url": "https://semanticreader.dev/mcp/registry",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add dev-semanticreader-semantic-reader --url 'https://semanticreader.dev/mcp/registry' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  dev-semanticreader-semantic-reader:
    url: "https://semanticreader.dev/mcp/registry"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "dev-semanticreader-semantic-reader": {
      "Transport": "http",
      "Url": "https://semanticreader.dev/mcp/registry"
    }
  }
}
# add to Vellum
assistant mcp add dev-semanticreader-semantic-reader -t streamable-http -u 'https://semanticreader.dev/mcp/registry'
// mcp.json
{
  "mcpServers": {
    "dev-semanticreader-semantic-reader": {
      "type": "http",
      "url": "https://semanticreader.dev/mcp/registry"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 28 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10.

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 0 to 3.

  • 17 Sept 26 −2
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “analyze_impact” rewrote its description, which is the text the model reads security
    • Tool “find_references” rewrote its description, which is the text the model reads security
    • Tool “find_symbol” rewrote its description, which is the text the model reads security
    • Tool “get_capabilities” rewrote its description, which is the text the model reads security
    • Tool “get_importers” rewrote its description, which is the text the model reads security
    • Tool “get_imports” rewrote its description, which is the text the model reads security
    • Tool “get_symbol_context” rewrote its description, which is the text the model reads security
    • Tool “query_code” rewrote its description, which is the text the model reads security
    • Tool coverage: 100% → 0% ▼ functional
    • Schema quality: 239 → 114 ▲ functional
    • Schema quality: excellent → good functional
    • New tool “get_definition” functional
    • New tool “get_diagnostics” functional
    • New tool “get_type” functional
    • New tool “open_snapshot” functional
    • “analyze_impact” added an optional parameter “snapshot” cosmetic
    • “find_references” added an optional parameter “snapshot” cosmetic
    • “find_symbol” added an optional parameter “compact” cosmetic
    • “find_symbol” added an optional parameter “snapshot” cosmetic
    • “get_importers” added an optional parameter “snapshot” cosmetic
    • “get_imports” added an optional parameter “snapshot” cosmetic
    • “get_symbol_context” added an optional parameter “snapshot” cosmetic
    • “query_code” added an optional parameter “snapshot” cosmetic
    • “analyze_impact” reworded the description of “compact” cosmetic
    • “analyze_impact” reworded the description of “files” cosmetic
    • “analyze_impact” reworded the description of “limit” cosmetic
    • “analyze_impact” reworded the description of “offset” cosmetic
    • “analyze_impact” reworded the description of “symbol” cosmetic
    • “find_references” reworded the description of “compact” cosmetic
    • “find_references” reworded the description of “files” cosmetic
    • “find_references” reworded the description of “limit” cosmetic
    • “find_references” reworded the description of “offset” cosmetic
    • “find_references” reworded the description of “symbol” cosmetic
    • “find_symbol” reworded the description of “files” cosmetic
    • “find_symbol” reworded the description of “kind” cosmetic
    • “find_symbol” reworded the description of “limit” cosmetic
    • “find_symbol” reworded the description of “name” cosmetic
    • “find_symbol” reworded the description of “path” cosmetic
    • “get_importers” reworded the description of “compact” cosmetic
    • “get_importers” reworded the description of “files” cosmetic
    • “get_importers” reworded the description of “limit” cosmetic
    • “get_importers” reworded the description of “offset” cosmetic
    • “get_importers” reworded the description of “symbol” cosmetic
    • “get_imports” reworded the description of “compact” cosmetic
    • “get_imports” reworded the description of “files” cosmetic
    • “get_imports” reworded the description of “limit” cosmetic
    • “get_imports” reworded the description of “offset” cosmetic
    • “get_imports” reworded the description of “symbol” cosmetic
    • “get_symbol_context” reworded the description of “files” cosmetic
    • “get_symbol_context” reworded the description of “include” cosmetic
    • “get_symbol_context” reworded the description of “kind” cosmetic
    • “get_symbol_context” reworded the description of “name” cosmetic
    • “get_symbol_context” reworded the description of “offsets” cosmetic
    • “get_symbol_context” reworded the description of “path” cosmetic
    • “get_symbol_context” reworded the description of “per_section_limit” cosmetic
    • “query_code” reworded the description of “compact” cosmetic
    • “query_code” reworded the description of “files” cosmetic
    • “query_code” reworded the description of “limit” cosmetic
    • “query_code” reworded the description of “offset” cosmetic
    • “query_code” reworded the description of “query” cosmetic
    • “query_code” reworded the description of “symbol” cosmetic
    • “analyze_impact” made “files” optional cosmetic
    • “find_references” made “files” optional cosmetic
    • “find_symbol” made “files” optional cosmetic
    • “get_importers” made “files” optional cosmetic
    • “get_imports” made “files” optional cosmetic
    • “get_symbol_context” made “files” optional cosmetic
    • “query_code” made “files” optional cosmetic
  • 15 Sept 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 191 → 239 ▼ functional
    • New tool “find_symbol” functional
    • New tool “get_symbol_context” functional
    • “analyze_impact” added an optional parameter “compact” cosmetic
    • “find_references” added an optional parameter “compact” cosmetic
    • “get_importers” added an optional parameter “compact” cosmetic
    • “get_imports” added an optional parameter “compact” cosmetic
    • “query_code” added an optional parameter “compact” cosmetic
  • 14 Sept 26 +3
    • Stability: unverified → fail ▼ security
    • Schema quality: pass → fail ▼ functional
    • “analyze_impact” made “symbol” required, so existing callers break ▼ functional
    • “find_references” made “symbol” required, so existing callers break ▼ functional
    • “get_importers” made “symbol” required, so existing callers break ▼ functional
    • “get_imports” made “symbol” required, so existing callers break ▼ functional
    • Tool coverage: 0% → 100% ▲ functional
    • Stability: unverified → 0.03 ▲ functional
    • Tool “analyze_impact” now declares an output schema ▲ functional
    • Tool “find_references” now declares an output schema ▲ functional
    • Tool “get_capabilities” now declares an output schema ▲ functional
    • Tool “get_importers” now declares an output schema ▲ functional
    • Tool “get_imports” now declares an output schema ▲ functional
    • Tool “query_code” now declares an output schema ▲ functional
    • First check of Tool coverage: 100 functional
    • Schema quality: good → excellent functional
    • Server version: 0.2.1 → 0.3.0 functional
    • Server version: 0.2.0 → 0.2.1 functional
    • “analyze_impact” reworded the description of “files” cosmetic
    • “analyze_impact” reworded the description of “limit” cosmetic
    • “analyze_impact” reworded the description of “offset” cosmetic
    • “analyze_impact” reworded the description of “symbol” cosmetic
    • “find_references” reworded the description of “files” cosmetic
    • “find_references” reworded the description of “limit” cosmetic
    • “find_references” reworded the description of “offset” cosmetic
    • “find_references” reworded the description of “symbol” cosmetic
    • “get_importers” reworded the description of “files” cosmetic
    • “get_importers” reworded the description of “limit” cosmetic
    • “get_importers” reworded the description of “offset” cosmetic
    • “get_importers” reworded the description of “symbol” cosmetic
    • “get_imports” reworded the description of “files” cosmetic
    • “get_imports” reworded the description of “limit” cosmetic
    • “get_imports” reworded the description of “offset” cosmetic
    • “get_imports” reworded the description of “symbol” cosmetic
    • “query_code” reworded the description of “files” cosmetic
    • “query_code” reworded the description of “limit” cosmetic
    • “query_code” reworded the description of “offset” cosmetic
    • “query_code” reworded the description of “query” cosmetic
    • “query_code” reworded the description of “symbol” cosmetic
    • Tool “analyze_impact” changed its title: Analyze Impact cosmetic
    • Tool “find_references” changed its title: Find References cosmetic
    • Tool “get_capabilities” changed its title: Get Capabilities cosmetic
    • Tool “get_importers” changed its title: Get Importers cosmetic
    • Tool “get_imports” changed its title: Get Imports cosmetic
    • Tool “query_code” changed its title: Query Code cosmetic
  • 13 Sept 26 62

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 29 Sept 2026 · Probed https://semanticreader.dev/mcp/registry

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=semanticreader.dev CN=WE1,O=Google Trust Services,C=US 13 Sept 2026 12 Dec 2026 ECDSA 256 ECDSA-SHA256 c76ff6d1dbe5f7d80ea6f3b29c5b68e6
SANs: semanticreader.dev, www.semanticreader.dev, *.www.semanticreader.dev
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of semanticreader.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
semanticreader.dev. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
x-content-type-options nosniff
referrer-policy no-referrer

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://semanticreader.dev/mcp/registry Verified 200
http (plaintext) http://semanticreader.dev/mcp/registry Inconclusive 406
MCP tools · 12 exposed · ~731 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
analyze_impact ~63

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

NameTypeReqDescription
compactboolean––
filesarray––
limitinteger––
offsetinteger––
snapshotstring––
symbolstringyes–
NameTypeReqDescription
analyzerstringyes–
coverageobjectyes–
itemsarrayyes–
limitsarrayyes–
next_offsetnumber|nullyes–
querystringyes–
returnednumberyes–
schemastringyes–
snapshotstringyes–
symbol–––
totalnumberyes–
total_foundnumberyes–
truncatedbooleanyes–

No examples provided.

find_references ~61

Return semantic static references to one exact compiler symbol.

NameTypeReqDescription
compactboolean––
filesarray––
limitinteger––
offsetinteger––
snapshotstring––
symbolstringyes–
NameTypeReqDescription
analyzerstringyes–
coverageobjectyes–
itemsarrayyes–
limitsarrayyes–
next_offsetnumber|nullyes–
querystringyes–
returnednumberyes–
schemastringyes–
snapshotstringyes–
symbol–––
totalnumberyes–
total_foundnumberyes–
truncatedbooleanyes–

No examples provided.

find_symbol ~72

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

NameTypeReqDescription
compactboolean––
filesarray––
kindstring––
limitinteger––
namestringyes–
pathstring––
snapshotstring––
NameTypeReqDescription
itemsarray––
nnumber––
querystring––
rstring––
resolutionstring––
returnednumber––
schemastring––
snapshotstring––
tinteger––
totalnumber––
truncatedboolean––
vnumber––
xarray––

No examples provided.

get_capabilities ~21

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

Input schema present but exposes no named parameters.

NameTypeReqDescription
billingobject––
discoveryobject––
inputobject––
languagesarray––
namestringyes–
opsobject––
queriesarray––
stagestring––
versionstringyes–

No examples provided.

get_definition ~55

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

NameTypeReqDescription
filesarray––
kindstring––
namestringyes–
pathstring––
snapshotstring––
NameTypeReqDescription
coverageobjectyes–
definition–yes–
limitsarrayyes–
next_offsetnumber|nullyes–
returnednumberyes–
schemastringyes–
snapshotstringyes–
symbolobjectyes–
totalnumberyes–
truncatedbooleanyes–

No examples provided.

get_diagnostics ~79

Return bounded TypeScript syntactic and semantic diagnostics for supplied files.

NameTypeReqDescription
compactboolean––
filesarray––
limitinteger––
offsetinteger––
packagesarray––
pathstring––
snapshotstring––
tsconfigobject––
NameTypeReqDescription
bobject––
countsobject––
coverageobject––
darray––
farray––
itemsarray––
limitsarray––
nnumber––
nextnumber|null––
next_offsetnumber|null––
pstring|null––
pathstring|null––
returnednumber––
schemastring––
snapshotstring––
totalnumber––
total_foundnumber––
truncatedboolean––
vnumber––

No examples provided.

get_importers ~62

Return supplied files that statically import one target file.

NameTypeReqDescription
compactboolean––
filesarray––
limitinteger––
offsetinteger––
snapshotstring––
symbolstringyes–
NameTypeReqDescription
analyzerstringyes–
coverageobjectyes–
itemsarrayyes–
limitsarrayyes–
next_offsetnumber|nullyes–
querystringyes–
returnednumberyes–
schemastringyes–
snapshotstringyes–
symbol–––
totalnumberyes–
total_foundnumberyes–
truncatedbooleanyes–

No examples provided.

get_imports ~60

Return static imports made by one supplied file.

NameTypeReqDescription
compactboolean––
filesarray––
limitinteger––
offsetinteger––
snapshotstring––
symbolstringyes–
NameTypeReqDescription
analyzerstringyes–
coverageobjectyes–
itemsarrayyes–
limitsarrayyes–
next_offsetnumber|nullyes–
querystringyes–
returnednumberyes–
schemastringyes–
snapshotstringyes–
symbol–––
totalnumberyes–
total_foundnumberyes–
truncatedbooleanyes–

No examples provided.

get_symbol_context ~85

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

NameTypeReqDescription
filesarray––
includearray––
kindstring––
namestringyes–
offsetsobject––
pathstring––
per_section_limitinteger––
snapshotstring––
NameTypeReqDescription
includearrayyes–
paid_sections_requestedarrayyes–
per_section_limitnumberyes–
schemastringyes–
sectionsobjectyes–
snapshotstringyes–
symbolobjectyes–

No examples provided.

get_type ~72

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

NameTypeReqDescription
filesarray––
kindstring––
namestringyes–
packagesarray––
pathstring––
snapshotstring––
tsconfigobject––
NameTypeReqDescription
apparent_typestring|nullyes–
call_signaturesarrayyes–
construct_signaturesarrayyes–
coverageobjectyes–
declared_typestring|nullyes–
limitsarrayyes–
schemastringyes–
snapshotstringyes–
symbolobjectyes–
value_typestring|nullyes–

No examples provided.

open_snapshot ~31

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

NameTypeReqDescription
filesarrayyes–
NameTypeReqDescription
expires_in_secondsintegeryes–
snapshotstringyes–
supplied_filesintegeryes–

No examples provided.

query_code ~70

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

NameTypeReqDescription
compactboolean––
filesarray––
limitinteger––
offsetinteger––
querystringyes–
snapshotstring––
symbolstring––
NameTypeReqDescription
analyzerstringyes–
coverageobjectyes–
itemsarrayyes–
limitsarrayyes–
next_offsetnumber|nullyes–
querystringyes–
returnednumberyes–
schemastringyes–
snapshotstringyes–
symbol–––
totalnumberyes–
total_foundnumberyes–
truncatedbooleanyes–

No examples provided.

Common questions

What is the Priority — TypeScript Compiler Intelligence MCP server?

Priority — TypeScript Compiler Intelligence is an MCP server listed in the public MCP registry as dev.semanticreader/semantic-reader. Stateless TS/JS compiler facts for agents: references, imports, impact. No repo index or OAuth. This page covers its hosted endpoint (https://semanticreader.dev/mcp/registry).

Is the Priority — TypeScript Compiler Intelligence MCP server safe to use?

Priority — TypeScript Compiler Intelligence scores 66 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Priority — TypeScript Compiler Intelligence MCP server expose?

Priority — TypeScript Compiler Intelligence exposes 12 tools: open_snapshot, get_capabilities, find_symbol, get_definition, get_type, and 7 more. Their descriptions and schemas cost roughly 731 tokens of context every time the server is loaded.

Does the Priority — TypeScript Compiler Intelligence MCP server require authentication?

No. We connected to Priority — TypeScript Compiler Intelligence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Priority — TypeScript Compiler Intelligence MCP server still maintained?

Priority — TypeScript Compiler Intelligence is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.