Remote MCP · Endpoint

xyz.forkcaster/mcp MCP server

No. xyz.forkcaster/mcp answered an MCP handshake 33 minutes ago.

UpLast checked 33 minutes ago

Server URL

https://forkcaster.xyz/mcp

The last check completed an MCP handshake.

Registry name
xyz.forkcaster/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
84 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Resolve Farcaster casts to deep-link URLs for any supported Farcaster client app. No auth.
Listing
From the official MCP registry (active).
Recent checks of xyz.forkcaster/mcp
CheckedResultHandshake
33 minutes agoHandshake completed84 ms
3 days agoHandshake completed252 ms
13 days agoHandshake completed190 ms
13 days agoHandshake completed213 ms
15 days agoHandshake completed151 ms
16 days agoHandshake completed149 ms
17 days agoHandshake completed190 ms
18 days agoHandshake completed73 ms
18 days agoHandshake completed258 ms
20 days agoHandshake completed351 ms
22 days agoHandshake completed193 ms
25 days agoHandshake completed135 ms
27 days agoHandshake completed286 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 13.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with xyz.forkcaster/mcp and makes no claim about it beyond what these checks measured.