tc39-mcp server
io.github.xyzzylabs/tc39-mcpxyzzylabsstreamable-httpv0.6.6Scanned
Independent MCP server for the TC39 specs (ECMA-262 + ECMA-402): clauses, search, diffs, history.
17 tools: 5 change things and 12 only read.
- Reads private data · 2
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
5 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the tc39-mcp server can do
The tc39-mcp server is published by the GitHub account xyzzylabs. It has 17 tools. It can create or change data (5 tools: spec.about, spec.sdo_index, spec.global_search, spec.well_known_intrinsics and 1 more), but cannot delete data. 12 tools only read.
2 tools read private data (spec.tables and clause.outline); 1 tool brings in text other people can write (spec.symbol_resolve).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 22, 2026, version 0.6.6.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
17 tools
Changes things 5Claude Code: ask
spec.aboutSelf-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 test…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
spec.crossrefsFor 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).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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`: 'in' | 'out' | 'both' (default). Outgoing also carries an `external` category: the clause's citations to external specs (Unicode, IETF, WHATWG) as resolvable URLs. Set `include_cross_spec: true` to also resolve outgoing references from ECMA-262 → ECMA-402 (or vice versa).
spec.global_searchRun spec.search across both ECMA-262 and ECMA-402 in one call and interleave hits by score.No findings
Why it is in this group
- The name "spec.global_search" says "search": a word for reading.
- The description's first verb is "run": a word for a change.
Description, as the server wrote it 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 text.
spec.sdo_indexIndex Syntax-Directed Operations by the grammar production they're defined on.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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 substring (case-insensitive).
spec.well_known_intrinsicsEnumerate the well-known intrinsics in a spec with their probable defining clauses.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Only reads 12Show 12 read-only tools
clause.getFetch a parsed TC39 clause as structured JSON.No findings
Why it is in this group
- The name "clause.get" says "get": a word for reading.
Description, as the server wrote it 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.listList parsed spec clauses with optional filters (kind, section prefix, has_algorithm).No findings
Why it is in this group
- The name "clause.list" says "list": a word for reading.
Description, as the server wrote it List parsed spec clauses with optional filters (kind, section prefix, has_algorithm). `spec` selects '262' or '402'. `at: '<sha>'` queries a historical main snapshot.
clause.outlineReturn the section tree (table of contents) for a parsed (spec, edition).Reads private dataNo findings
Why it is in this group
- The description's first verb is "return": a word for reading.
What it can reach
- private-dataThe description's first sentence says "return" and "table": it reads databases.
Description, as the server wrote it 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.
proposal.getFetch one TC39 proposal by slug (exact) or name (case-insensitive).No findings
Why it is in this group
- The name "proposal.get" says "get": a word for reading.
Description, as the server wrote it Fetch one TC39 proposal by slug (exact) or name (case-insensitive).
proposal.listList TC39 proposals from the static index (tc39/proposals).No findings
Why it is in this group
- The name "proposal.list" says "list": a word for reading.
Description, as the server wrote it 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).
spec.diffClause-level diff of one clause across two editions of a spec.No findings
Why it is in this group
- The name "spec.diff" says "diff": a word for reading.
Description, as the server wrote it 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 latest stable release, `to` to main.
spec.grammarQuery grammar productions captured from the spec's `<emu-grammar>` blocks.No findings
Why it is in this group
- The description's first verb is "query": a word for reading.
Description, as the server wrote it 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 + their production counts. `include_sdo` folds in SDO-attached productions (off by default).
spec.searchSearch the parsed spec by clause id / aoid / title (+ step text with `search_steps`).No findings
Why it is in this group
- The name "spec.search" says "search": a word for reading.
Description, as the server wrote it 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.
spec.snapshotsList the live (spec, edition, sha, fetched_at) snapshots the hosted Worker is serving from R2.No findings
Why it is in this group
- The name "spec.snapshots" says "snapshot": a word for reading.
Description, as the server wrote it 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.search but aren't enumerated here.
spec.symbol_resolveResolve spec notation like `[[Prototype]]` (internal slot), `%Object.prototype%` (well-known intrinsic), or `~number~` (sigil enum): return clauses that mention or define it, ranke…Reads text others writeNo findings
Why it is in this group
- The name "spec.symbol_resolve" says "resolve": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "resolve" and "mention": it reads comments, which other people can write.
Description, as the server wrote it 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.tablesList or fetch parsed `<emu-table>` content.Reads private dataNo findings
Why it is in this group
- The description's first verb is "list": a word for reading.
What it can reach
- private-dataThe name "spec.tables" says "table": it reads databases.
- private-dataThe description's first sentence says "list" and "table": it reads databases.
Description, as the server wrote it 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.
test262.searchSearch the tc39/test262 conformance suite from its indexed front-matter.No findings
Why it is in this group
- The name "test262.search" says "search": a word for reading.
Description, as the server wrote it 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, GitHub url at the indexed SHA, esid, description, features, flags), capped at `limit` (default 20). Supply at least one of `query` / `esid`.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data2
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:13 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 5
- Protocol version
- 2024-11-05
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.xyzzylabs.ai/tc39/mcp: tools/list returned 17 tools to an anonymous client, including spec.about (write), spec.sdo_index (write), spec.global_search (write), spec.well_known_intrinsics (write), spec.crossrefs (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.6.6. Values in angle brackets are yours to fill in.
claude mcp add --transport http tc39 https://mcp.xyzzylabs.ai/tc39/mcpclaude mcp add --transport http tc39 https://mcp.xyzzylabs.ai/tc39/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__tc39__clause_get",
"mcp__tc39__clause_list",
"mcp__tc39__spec_search",
"mcp__tc39__proposal_list",
"mcp__tc39__proposal_get",
"mcp__tc39__spec_grammar",
"mcp__tc39__spec_tables",
"mcp__tc39__clause_outline",
"mcp__tc39__spec_snapshots",
"mcp__tc39__spec_symbol_resolve",
"mcp__tc39__spec_diff",
"mcp__tc39__test262_search"
],
"ask": [
"mcp__tc39__spec_about",
"mcp__tc39__spec_sdo_index",
"mcp__tc39__spec_global_search",
"mcp__tc39__spec_well_known_intrinsics",
"mcp__tc39__spec_crossrefs"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as tc39. Review it before you use it.
Capability tags behind 3 rules
- mcp__tc39__spec_tables private-data
- mcp__tc39__clause_outline private-data
- mcp__tc39__spec_symbol_resolve untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.xyzzylabs/tc39-mcp/verify?hash=4eb3aba21a9d9d97c8cf31af5cc7228059f86df386b602a1a7532f1654cac311" | jq -e '.changed == false'Pinned hash 4eb3aba21a9d, from Nov 22, 2026, 02:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.xyzzylabs/tc39-mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.xyzzylabs/tc39-mcp)Source: MCP Registry · repository. Synced Nov 7, 2026, 21:17 UTC.
tc39-mcp server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the tc39-mcp server safe?
- No scan can promise that. What its definitions show: 17 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the tc39-mcp server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the tc39-mcp server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the tc39-mcp server have?
- 17 tools: 5 write, 12 read. spec.about, spec.sdo_index, spec.global_search, spec.well_known_intrinsics, spec.crossrefs, clause.get, clause.list, spec.search and 9 more.
Does the tc39-mcp server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the tc39-mcp server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the tc39-mcp server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 22, 2026.