Remote MCP · Endpoint
OSA Procurement Guard MCP server
No. OSA Procurement Guard answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://pkctqxeydfuiupadaoov.supabase.co/functions/v1/procurement-mcp
The last check completed an MCP handshake.
- Registry name
- io.github.omarfff/osa-procurement-guard
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 1.06 s
- Tools exposed
- 1 tool
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Pre-purchase trust, pricing and budget decisions for AI agents buying APIs and MCP tools.
- Repository
- https://github.com/omarfff/OSA
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 1.06 s |
| 1 day ago | Handshake completed | 867 ms |
| 2 days ago | Handshake completed | 933 ms |
| 3 days ago | Handshake completed | 977 ms |
| 4 days ago | Handshake completed | 994 ms |
| 5 days ago | Handshake completed | 902 ms |
| 6 days ago | Handshake completed | 1.05 s |
| 9 days ago | Handshake completed | 736 ms |
| 11 days ago | Handshake completed | 832 ms |
| 14 days ago | Handshake completed | 917 ms |
| 16 days ago | Handshake completed | 879 ms |
| 18 days ago | Handshake completed | 872 ms |
| 20 days ago | Handshake completed | 1.55 s |
| 22 days ago | Handshake completed | 484 ms |
| 24 days ago | Handshake completed | 795 ms |
| 26 days ago | Handshake completed | 818 ms |
| 27 days ago | Handshake completed | 892 ms |
| 29 days ago | Handshake completed | 1.33 s |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
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 OSA Procurement Guard and makes no claim about it beyond what these checks measured.