com.fetchrelay/fetchrelay
FetchRelay
com.fetchrelay/fetchrelay did not answer the probe on 2026-10-03. Result: not found (HTTP 404).
Extract public webpages as Markdown, map sites, and run bounded crawl jobs. API key required.
not found probed 2026-10-03 · HTTP 404
Streamable HTTP error: Error POSTing to endpoint: {"error": {"code": "404", "message": "The deployment could not be found on Vercel."}}- Endpoint
- https://fetchrelay.com/api/mcp (streamable-http)
- Host
- fetchrelay.com
- Website
- https://fetchrelay.com/integrations/mcp?utm_source=mcp&utm_medium=integration&utm_campaign=mcp-launch
- Registry
- active, updated 2026-09-07 · registry entry
- Reachable
- 0 of the last 2 probes
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Tokens |
|---|---|---|---|---|
| 2026-10-03 20:29 | not found | |||
| 2026-10-03 17:48 | not found |
Badge
[](https://mcp-pulse.ulehla.dev/s/com.fetchrelay/fetchrelay)