Remote MCP · Endpoint

Tollbridge MCP server

Yes, as of 2 days ago: the server returned an HTTP error.

DownLast checked 2 days ago

Server URL

https://api.tollbridge.app/mcp

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

Registry name
io.github.clawpipe/tollbridge
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
34 tools
Uptime, last 30 days
69.2% from 13 checks
Described by its publisher as
Free market data with provenance and paid decision intelligence for AI agents.
Listing
From the official MCP registry (active).
Recent checks of Tollbridge
CheckedResultHandshake
2 days agoFailed - the server returned an HTTP error—
3 days agoFailed - the server returned an HTTP error—
3 days agoFailed - the server returned an HTTP error—
5 days agoFailed - the server returned an HTTP error—
6 days agoHandshake completed289 ms
7 days agoHandshake completed295 ms
8 days agoHandshake completed1.20 s
9 days agoHandshake completed336 ms
11 days agoHandshake completed294 ms
13 days agoHandshake completed301 ms
16 days agoHandshake completed292 ms
18 days agoHandshake completed299 ms
21 days agoHandshake completed296 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 9 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 Tollbridge and makes no claim about it beyond what these checks measured.