Remote MCP · Endpoint

Requstory MCP server

No. Requstory answered an MCP handshake 9 hours ago.

UpLast checked 9 hours ago

Server URL

https://requstory.com/mcp

The last check completed an MCP handshake.

Registry name
com.requstory/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
309 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 11 checks
Described by its publisher as
Map how a company works, and run B2B order to cash with AI agents that ask before they act.
Listing
From the official MCP registry (active).
Recent checks of Requstory
CheckedResultHandshake
9 hours agoHandshake completed309 ms
4 days agoHandshake completed279 ms
14 days agoHandshake completed315 ms
15 days agoHandshake completed516 ms
15 days agoHandshake completed264 ms
17 days agoHandshake completed292 ms
18 days agoHandshake completed241 ms
19 days agoHandshake completed270 ms
20 days agoHandshake completed271 ms
21 days agoHandshake completed350 ms
23 days agoHandshake completed304 ms

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

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