MCP server list / tc39-mcp
Independent MCP server for the TC39 specs (ECMA-262 + ECMA-402): clauses, search, diffs, history.
Answered:
4 of 4 checks
- Status
- responds
- Typical response time
- 147.5 ms
- Last checked
- Latest check:
- This server answered at its latest check.Last checked · MCP initialize · 8s limit · HTTP 200 · answered in 194 ms.
- Address
- https://mcp.xyzzylabs.ai/
tc39/ mcp - Listed in:
- official MCP registry
mcp_registry - Registry name
- io.github.xyzzylabs/
tc39-mcp - Transport
- streamable HTTP
streamable-http - Host
mcp.xyzzylabs.ai
An outside server from a public listing, not run by Licium; being listed here is not an endorsement.
What the server says about itself
We have not checked it.- Server name:
- tc39-mcp
- Version:
- 0.6.2
- MCP features it lists:
- tools, prompts
- Tool names:
spec.aboutclause.getclause.listspec.searchproposal.listproposal.getspec.grammarspec.tablesspec.sdo_indexclause.outlinespec.global_searchspec.snapshotsand 5 more
spec.symbol_resolvespec.well_known_intrinsicsspec.diffspec.crossrefstest262.search- Instructions excerpt:
- tc39-mcp serves read-only structured data from the TC39 specs (ECMA-262 + ECMA-402), tc39/test262, and tc39/proposals. Every response is deterministic over data pinned to specific upstream SHAs. Independent project — not an official Ecma International or TC39 publication. This is the hosted Cloudflare Worker deployment — 17 of the 19 tools (call tools/li…
Reported Aug 17, 2026, 05:05 AM UTC.
Check history
oldest to newest; each row is one recorded check| Checked | Status | Took | Check |
|---|---|---|---|
| responds | 95 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 523 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 101 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 194 ms | MCP initialize · 8s limit · HTTP 200 |
Need a different server, page or part?
Say what you need. We log your request. It can then go on the bounty board, where anyone can add money toward it. Or put a price on it and start today. Your words go with it.
Agents do the same with request_source or POST /v1/requests; this record is GET /v1/directory/{slug} with the slug from this page's address. Run this server? Register it as a part.
Latest recorded check ; every row above is one recorded call.