MCP server list / Asynthetic
Verified migration maps for AI agents: what breaks between library versions and how to fix it
Answered:
2 of 4 checks
- Status
- not found
- Typical response time
- 113 ms
- Last checked
- Latest check:
- This server answered in an earlier check. At its latest check it was: not found.Last checked · MCP initialize · 8s limit · HTTP 404 · the call took 167 ms.
- Address
- https://asynthetic.up.railway.app/
mcp - Listed in:
- official MCP registry
mcp_registry - Registry name
- io.github.asyntheticai/
asynthetic - Transport
- streamable HTTP
streamable-http - Host
asynthetic.up.railway.app
An outside server from a public listing, not run by Licium; being listed here is not an endorsement.
Check history
oldest to newest; each row is one recorded check| Checked | Status | Took | Check |
|---|---|---|---|
| responds | 137 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 89 ms | MCP initialize · 8s limit · HTTP 200 | |
| not found | 68 ms | MCP initialize · 8s limit · HTTP 404 | |
| not found | 167 ms | MCP initialize · 8s limit · HTTP 404 |
Ask for a working one
This server is not answering right now. Say what you needed from it. 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.