tc39-mcp
Independent MCP server for the TC39 specs (ECMA-262 + ECMA-402): clauses, search, diffs, history
Reviews
No review yet. Used tc39-mcp? Be the first to help others choose.What it does
tc39-mcp is an MCP server, a connector that lets an AI assistant use it as a tool. It can be used hosted (nothing to install) or installed locally.
No capability identified yet from its description.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 1d ago (live check)Hosted endpoint
https://mcp.xyzzylabs.ai/tc39/mcpstreamable-http
In Claude Code: claude mcp add --transport http tc39-mcp https://mcp.xyzzylabs.ai/tc39/mcp
Install package
- NPM
tc39-mcpv0.6.6 · runs locally (stdio)
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"tc39-mcp": {
"url": "https://mcp.xyzzylabs.ai/tc39/mcp"
}
}
}Live check
Electra Index connected to the hosted endpoint 1d agoONLINE tc39-mcp answered an MCP connection on 12 Nov 2026 and introduced itself as tc39-mcp 0.6.6 (MCP protocol 2024-11-05).
17 tools offered to AI assistants
spec.about· Self-description of this MCP server: package name + version, per-snapshot pin metadata (sha, fetched_at, biblio_commit, clause_count) for every supported (spec, edition), plus test262 + proposals index headers when present.clause.get· Fetch a parsed TC39 clause as structured JSON. `spec` selects '262' (default) or '402'. `edition` defaults to 'latest'. `at: '<sha>'` pins to a historical main snapshot (only valid for edition='main'); omit to query the live snapshot.clause.list· List parsed spec clauses with optional filters (kind, section prefix, has_algorithm). `spec` selects '262' or '402'. `at: '<sha>'` queries a historical main snapshot.spec.search· Search the parsed spec by clause id / aoid / title (+ step text with `search_steps`). Aoid-exact ranks first. `at: '<sha>'` searches a historical main snapshot.proposal.list· List TC39 proposals from the static index (tc39/proposals). Filter by spec ('262'|'402'), stage ('0'|'1'|'2'|'2.7'|'3'|'finished'|'inactive'|'active'), champion (substring), or contains (name/slug substring).proposal.get· Fetch one TC39 proposal by slug (exact) or name (case-insensitive).spec.grammar· Query grammar productions captured from the spec's `<emu-grammar>` blocks. `{ nonterminal }` returns every production for that non-terminal (exact match); `{ contains }` filters by RHS / name substring; neither lists all non-terminals + thespec.tables· List or fetch parsed `<emu-table>` content. `{ id }` returns exactly that table (full columns + rows); otherwise list table summaries, optionally narrowed by a `filter` substring over the caption or id.spec.sdo_index· Index Syntax-Directed Operations by the grammar production they're defined on. `by: 'production'` (default) groups SDOs under each production; `by: 'sdo'` groups productions under each SDO title. `filter` narrows to keys containing a substrclause.outline· Return the section tree (table of contents) for a parsed (spec, edition). `depth` caps how deep the tree descends (1 = top-level only); `under` limits the tree to descendants of one clause id.spec.global_search· Run spec.search across both ECMA-262 and ECMA-402 in one call and interleave hits by score. Each hit is tagged with the spec it came from. Use it when you don't know which spec defines a symbol. `search_steps` also matches algorithm step tespec.snapshots· List the live (spec, edition, sha, fetched_at) snapshots the hosted Worker is serving from R2. Filter by `spec` ('262'|'402') or `edition` (e.g. 'main', 'es2026'). Historical SHA-pinned copies are reachable via `at:` on clause.get / spec.se
Show 5 more
spec.symbol_resolve· Resolve spec notation like `[[Prototype]]` (internal slot), `%Object.prototype%` (well-known intrinsic), or `~number~` (sigil enum): return clauses that mention or define it, ranked by occurrence with a bump for definition-y sections.spec.well_known_intrinsics· Enumerate the well-known intrinsics in a spec with their probable defining clauses. Driven from the canonical §6.1.7.4 WKI table when present (ECMA-262), else a `%X%` prose scan (e.g. ECMA-402). `filter` narrows by bare-name substring.spec.diff· Clause-level diff of one clause across two editions of a spec. Reports identical / modified / added / removed plus a field-level breakdown (title, signature, step count, reworded step indices, notes, crossrefs). `from` defaults to the latesspec.crossrefs· For a clause id, return its outgoing references (clauses it cites) and/or incoming references (clauses that cite it — the back-reference index the parse alone doesn't expose). The reverse index is AOID-densified from step text. `direction`:test262.search· Search the tc39/test262 conformance suite from its indexed front-matter. `query` AND-matches whitespace tokens (case-insensitive) across each test's description + path; `esid` prefix-matches the front-matter esid. Returns ranked hits (path,
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Install package | tc39-mcp | DECLARED | SRC-001 Official MCP Registry | 5d ago |
| Version | 0.6.6 | DECLARED | SRC-001 Official MCP Registry | 5d ago |
| Hosted endpoint | https://mcp.xyzzylabs.ai/tc39/mcp | DECLARED | SRC-001 Official MCP Registry | 5d ago |
| Package registries | npm | DECLARED | SRC-001 Official MCP Registry | 5d ago |
| Local install (package) | yes | DECLARED | SRC-001 Official MCP Registry | 5d ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 5d ago |
| Website | https://mcp.xyzzylabs.ai/tc39 | DECLARED | SRC-001 Official MCP Registry | 5d ago |
| Repository | https://github.com/xyzzylabs/tc39-mcp | DECLARED | SRC-001 Official MCP Registry | 5d ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 5d ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 5d ago |
Change history
- VERSION07 Nov 20260.6.4 → 0.6.6
- VERSION07 Oct 20260.6.3 → 0.6.4
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is tc39-mcp still online?
Free alerts · no account▲ 0Do you run tc39-mcp? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about tc39-mcp
How do I connect tc39-mcp?
Use the hosted endpoint https://mcp.xyzzylabs.ai/tc39/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does tc39-mcp offer?
When Electra Index connected on 12 Nov 2026, it listed 17 tools: spec.about, clause.get, clause.list, spec.search, proposal.list, proposal.get, spec.grammar, spec.tables and more. The full list is in "Live check" above.
Is tc39-mcp online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 1d ago.