Remote MCP · Endpoint
SAP MCP Server MCP server
Yes, as of 2 hours ago: the connection was refused or dropped.
DownLast checked 2 hours ago
Server URL
https://mcp.sap.oobeprotocol.ai/mcp
The last check failed: the connection was refused or dropped.
- Registry name
- ai.oobeprotocol.sap.mcp/sap-mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- Not measured yet
- Uptime, last 30 days
- 88.9% from 18 checks
- Described by its publisher as
- Solana-native MCP gateway for SAP, DeFi tools, SNS identity, and x402 payments.
- Repository
- https://github.com/OOBE-PROTOCOL/sap-mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Failed - the connection was refused or dropped | — |
| 1 day ago | Handshake completed | 752 ms |
| 3 days ago | Handshake completed | 765 ms |
| 3 days ago | Handshake completed | 822 ms |
| 4 days ago | Handshake completed | 735 ms |
| 5 days ago | Handshake completed | 787 ms |
| 7 days ago | Handshake completed | 740 ms |
| 10 days ago | Handshake completed | 710 ms |
| 12 days ago | Handshake completed | 759 ms |
| 15 days ago | Handshake completed | 802 ms |
| 17 days ago | Handshake completed | 806 ms |
| 19 days ago | Handshake completed | 1.78 s |
| 21 days ago | Handshake completed | 767 ms |
| 23 days ago | Failed - the server returned an HTTP error | — |
| 25 days ago | Handshake completed | 736 ms |
| 26 days ago | Handshake completed | 713 ms |
| 28 days ago | Handshake completed | 863 ms |
| 29 days ago | Handshake completed | 755 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 27 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 SAP MCP Server and makes no claim about it beyond what these checks measured.