TC39 TOOLS

17 tools from the Tc39 MCP Server, categorised by risk level.

READ 15 tools
Read clause.get Fetch a parsed TC39 clause as structured JSON. `spec` selects '262' (default) or '402'. `edition` defaults ... Read clause.list List parsed spec clauses with optional filters (kind, section prefix, has_algorithm). `spec` selects '262' ... Read clause.outline Return the section tree (table of contents) for a parsed (spec, edition). `depth` caps how deep the tree de... Read proposal.get Fetch one TC39 proposal by slug (exact) or name (case-insensitive). Read proposal.list List TC39 proposals from the static index (tc39/proposals). Filter by spec ('262'|'402'), stage ('0'|'1'|'2... Read spec.about Self-description of this MCP server: package name + version, per-snapshot pin metadata (sha, fetched_at, bi... Read spec.diff Clause-level diff of one clause across two editions of a spec. Reports identical / modified / added / remov... Read spec.global_search Run spec.search across both ECMA-262 and ECMA-402 in one call and interleave hits by score. Each hit is tag... Read spec.grammar Query grammar productions captured from the spec's `<emu-grammar>` blocks. `{ nonterminal }` returns every ... Read spec.sdo_index Index Syntax-Directed Operations by the grammar production they're defined on. `by: 'production'` (default)... Read spec.search Search the parsed spec by clause id / aoid / title (+ step text with `search_steps`). Aoid-exact ranks firs... Read spec.snapshots List the live (spec, edition, sha, fetched_at) snapshots the hosted Worker is serving from R2. Filter by `s... Read spec.tables List or fetch parsed `<emu-table>` content. `{ id }` returns exactly that table (full columns + rows); othe... Read spec.well_known_intrinsics Enumerate the well-known intrinsics in a spec with their probable defining clauses. Driven from the canonic... Read test262.search Search the tc39/test262 conformance suite from its indexed front-matter. `query` AND-matches whitespace tok...

The managed route: connect Tc39 through the PolicyLayer gateway — every tool call above is checked against your policy before it runs, with a full audit log.

DIRECT INSTALL (UNMANAGED) npx -y tc39-mcp
How many tools does the Tc39 MCP server have? +

The Tc39 MCP server exposes 17 tools across 2 categories: Read, Write.

How do I enforce policies on Tc39 tools? +

Route the Tc39 server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard — they are enforced on every call before it reaches the server.

What risk categories do Tc39 tools fall into? +

Tc39 tools are categorised as Read (15), Write (2). Each category has a recommended default policy.

Let agents act without letting them run wild.

Route your MCP servers through PolicyLayer and every tool call is checked against your policy before it runs — allow, deny, or require approval. Per-identity grants. Full audit log. Live in minutes.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.