Remote MCP · Endpoint
McpStamp Purchase Requisitions MCP server
No. McpStamp Purchase Requisitions answered an MCP handshake 35 minutes ago.
UpLast checked 35 minutes ago
Server URL
https://mcp.zovo.one/mcp/purchase-requisition
The last check completed an MCP handshake.
- Registry name
- io.github.theluckystrike/onboarding-purchase-requisition-inspection-runs
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 105 ms
- Tools exposed
- 16 tools
- Uptime, last 30 days
- 100% from 14 checks
- Described by its publisher as
- Purchase requisitions as reusable step lists: dated runs, pass or fail per step, and sign-off.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 35 minutes ago | Handshake completed | 105 ms |
| 9 days ago | Handshake completed | 89 ms |
| 10 days ago | Handshake completed | 1.64 s |
| 11 days ago | Handshake completed | 58 ms |
| 12 days ago | Handshake completed | 48 ms |
| 14 days ago | Handshake completed | 84 ms |
| 14 days ago | Handshake completed | 1.05 s |
| 15 days ago | Handshake completed | 57 ms |
| 17 days ago | Handshake completed | 62 ms |
| 19 days ago | Handshake completed | 91 ms |
| 21 days ago | Handshake completed | 762 ms |
| 24 days ago | Handshake completed | 843 ms |
| 26 days ago | Handshake completed | 647 ms |
| 28 days ago | Handshake completed | 151 ms |
The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 16 responding of 16.
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 McpStamp Purchase Requisitions and makes no claim about it beyond what these checks measured.