Remote MCP · Endpoint
SAP MCP Server MCP server
No. SAP MCP Server answered an MCP handshake 8 hours ago.
UpLast checked 8 hours ago
Server URL
https://mcp.sap.oobeprotocol.ai/mcp
The last check completed an MCP handshake.
- Registry name
- ai.oobeprotocol.sap.mcp/sap-mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 767 ms
- Tools exposed
- Not measured yet
- Uptime, last 30 days
- 94.1% from 17 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 |
|---|---|---|
| 8 hours ago | Handshake completed | 767 ms |
| 2 days ago | Failed - the server returned an HTTP error | — |
| 4 days ago | Handshake completed | 736 ms |
| 5 days ago | Handshake completed | 713 ms |
| 7 days ago | Handshake completed | 863 ms |
| 8 days ago | Handshake completed | 755 ms |
| 9 days ago | Handshake completed | 695 ms |
| 12 days ago | Handshake completed | 709 ms |
| 13 days ago | Handshake completed | 740 ms |
| 15 days ago | Handshake completed | 736 ms |
| 16 days ago | Handshake completed | 723 ms |
| 17 days ago | Handshake completed | 800 ms |
| 18 days ago | Handshake completed | 729 ms |
| 19 days ago | Handshake completed | 766 ms |
| 20 days ago | Handshake completed | 734 ms |
| 21 days ago | Handshake completed | 778 ms |
| 23 days ago | Handshake completed | 746 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 16 responding of 17.
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.