tc39-mcp.chicoxyzzy.workers.dev
https://tc39-mcp.chicoxyzzy.workers.dev/mcp
active Production-safe Score 95/100 http no auth
At a glance
| Endpoint | https://tc39-mcp.chicoxyzzy.workers.dev/mcp |
|---|---|
| Source | https://github.com/xyzzylabs/tc39-mcp/blob/main/README.md |
| Transport | http |
| Tools | 17 |
| Auth | none |
| First seen | 2026-05-31 00:18:03 |
| Last checked | 2026-11-17 22:00:44 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 306 / 500 ms |
| Last successful check | 2026-11-17 22:00:44 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (17)
spec.about— Self-description of this MCP server: package name + version, per-snapshot pin metadata (sha, fetched_at, biblio_commit, clause_count) for evclause.get— Fetch a parsed TC39 clause as structured JSON. `spec` selects '262' (default) or '402'. `edition` defaults to 'latest'. `at: '<sha>'` pins tclause.list— List parsed spec clauses with optional filters (kind, section prefix, has_algorithm). `spec` selects '262' or '402'. `at: '<sha>'` queries aspec.search— Search the parsed spec by clause id / aoid / title (+ step text with `search_steps`). Aoid-exact ranks first. `at: '<sha>'` searches a histoproposal.list— List TC39 proposals from the static index (tc39/proposals). Filter by spec ('262'|'402'), stage ('0'|'1'|'2'|'2.7'|'3'|'finished'|'inactive'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-terminalspec.tables— List or fetch parsed `<emu-table>` content. `{ id }` returns exactly that table (full columns + rows); otherwise list table summaries, optiospec.sdo_index— Index Syntax-Directed Operations by the grammar production they're defined on. `by: 'production'` (default) groups SDOs under each productioclause.outline— Return the section tree (table of contents) for a parsed (spec, edition). `depth` caps how deep the tree descends (1 = top-level only); `undspec.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. Uspec.snapshots— List the live (spec, edition, sha, fetched_at) snapshots the hosted Worker is serving from R2. Filter by `spec` ('262'|'402') or `edition` (spec.symbol_resolve— Resolve spec notation like `[[Prototype]]` (internal slot), `%Object.prototype%` (well-known intrinsic), or `~number~` (sigil enum): returnspec.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 presenspec.diff— Clause-level diff of one clause across two editions of a spec. Reports identical / modified / added / removed plus a field-level breakdown (spec.crossrefs— For a clause id, return its outgoing references (clauses it cites) and/or incoming references (clauses that cite it — the back-reference indtest262.search— Search the tc39/test262 conformance suite from its indexed front-matter. `query` AND-matches whitespace tokens (case-insensitive) across eac
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 22:00:44 | ✓ | ✓ | 368 ms | 91 | active |
| 2026-11-17 21:45:39 | ✓ | ✓ | 244 ms | 94 | active |
| 2026-11-17 21:30:32 | ✓ | ✓ | 491 ms | 91 | active |
| 2026-11-17 21:15:11 | ✓ | ✓ | 371 ms | 91 | active |
| 2026-11-17 20:59:50 | ✓ | ✓ | 252 ms | 94 | active |
| 2026-11-17 20:44:49 | ✓ | ✓ | 464 ms | 91 | active |
| 2026-11-17 20:29:48 | ✓ | ✓ | 384 ms | 91 | active |
| 2026-11-17 20:14:45 | ✓ | ✓ | 433 ms | 91 | active |
| 2026-11-17 19:58:51 | ✓ | ✓ | 274 ms | 94 | active |
| 2026-11-17 19:43:45 | ✓ | ✓ | 252 ms | 94 | active |
| 2026-11-17 19:28:43 | ✓ | ✓ | 225 ms | 94 | active |
| 2026-11-17 19:13:40 | ✓ | ✓ | 239 ms | 94 | active |
| 2026-11-17 18:56:13 | ✓ | ✓ | 335 ms | 91 | active |
| 2026-11-17 18:41:06 | ✓ | ✓ | 374 ms | 91 | active |
| 2026-11-17 18:25:58 | ✓ | ✓ | 234 ms | 94 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://tc39-mcp.chicoxyzzy.workers.dev/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/tc39-mcp-chicoxyzzy-workers-dev-mcp # JSON