Is io.github.lexsocket/mcp-ted up? Live MCP status

No, it is not answering as an MCP server. fetch failed.

The endpoint did not answer as an MCP server: fetch failed. Do not spend a call on it.

One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.

Live status every few hours: Wellknown

Email me when this server changes

That was one look. To hear when it stops answering or its tools change, leave an address.

Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.

Monthly census, 6 October 2026

The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one was not an MCP server at that address (fetch failed). Every listing’s result: index.ndjson (what the files hold: index.meta.json).

Agent discovery documents at this origin

Not asked on 9 October 2026: the census could not connect to any listing at https://mcp.lexsocket.ai. Who publishes them.

Tool changes between snapshots

It is not in the 2026-10 snapshot. Snapshots record the tool list of every listing that answered a stock client with no credential in that month’s census.

Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.

The listing

Also

The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt

Free, no key, no signup. Terms · Privacy