Remote MCP · Endpoint

Venue Toll Facts MCP server

No. Venue Toll Facts answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://venuetoll.com/mcp

The last check completed an MCP handshake.

Registry name
com.venuetoll/toll
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
359 ms
Tools exposed
2 tools
Uptime, last 30 days
92.3% from 13 checks
Described by its publisher as
Measured venue tolls: fee, spread, slippage, with evidence. list_venues free; get_toll paid.
Listing
From the official MCP registry (active).
Recent checks of Venue Toll Facts
CheckedResultHandshake
1 hour agoHandshake completed359 ms
2 days agoHandshake completed369 ms
5 days agoHandshake completed363 ms
7 days agoHandshake completed368 ms
9 days agoFailed - the server returned an HTTP error—
11 days agoHandshake completed411 ms
13 days agoHandshake completed366 ms
15 days agoHandshake completed369 ms
17 days agoHandshake completed313 ms
19 days agoHandshake completed329 ms
20 days agoHandshake completed397 ms
21 days agoHandshake completed438 ms
23 days agoHandshake completed303 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 12 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Venue Toll Facts and makes no claim about it beyond what these checks measured.