Remote MCP · Endpoint

Clink Forge MCP server

Yes, as of 1 hour ago: the server returned an HTTP error.

DownLast checked 1 hour ago

Server URL

https://api.clinkforge.com/mcp

The last check failed: the server returned an HTTP error.

Registry name
com.clinkforge/clink-forge
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
29 tools
Uptime, last 30 days
64.7% from 17 checks
Described by its publisher as
Pay-per-call government data over x402: provenance chains, Ed25519 attestations, no API keys.
Listing
From the official MCP registry (active).
Recent checks of Clink Forge
CheckedResultHandshake
1 hour agoFailed - the server returned an HTTP error—
2 days agoFailed - the server returned an HTTP error—
4 days agoFailed - the server returned an HTTP error—
5 days agoFailed - the server returned an HTTP error—
7 days agoHandshake completed112 ms
7 days agoHandshake completed633 ms
9 days agoHandshake completed123 ms
12 days agoHandshake completed109 ms
13 days agoHandshake completed139 ms
15 days agoHandshake completed98 ms
16 days agoFailed - the server returned an HTTP error—
17 days agoHandshake completed208 ms
18 days agoHandshake completed1.52 s
19 days agoHandshake completed352 ms
20 days agoHandshake completed136 ms
21 days agoFailed - the server returned an HTTP error—
22 days agoHandshake completed218 ms

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

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 Clink Forge and makes no claim about it beyond what these checks measured.