mcp.sap.oobeprotocol.ai/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-002 | OK | — | 178 | — | — | |
| REL-SNAP-003 | OK | — | 169 | — | — | |
| REL-SNAP-004 | OK | — | 281 | — | — | |
| REL-SNAP-005 | OK | — | 307 | — | — | |
| REL-SNAP-006 | OK | — | 626 | — | — | |
| REL-SNAP-007 | OK | — | 392 | — | — | |
| REL-SNAP-008 | OK | — | 260 | — | — | |
| REL-SNAP-009 | OK | — | 273 | — | — | |
| REL-SNAP-010 | OK | — | 298 | — | — | |
| REL-SNAP-011 | OK | — | 283 | — | — | |
| REL-SNAP-012 | OK | — | 564 | — | — | |
| REL-SNAP-013 | OK | — | 284 | — | — | |
| REL-SNAP-014 | OK | — | 299 | — | — | |
| REL-SNAP-015 | OK | — | 892 | — | — | |
| REL-SNAP-016 | OK | — | 860 | — | — | |
| REL-SNAP-017 | OK | — | 878 | — | — | |
| REL-SNAP-018 | OK | — | 446 | — | — | |
| REL-SNAP-019 | OK | — | 898 | — | — | |
| REL-SNAP-020 | OK | — | 850 | — | — | |
| REL-SNAP-021 | OK | — | 458 | — | — | |
| REL-SNAP-022 | OK | — | 875 | — | — | |
| REL-SNAP-023 | OK | — | 1287 | — | — | |
| REL-SNAP-024 | OK | — | 878 | — | — | |
| REL-SNAP-025 | OK | — | 878 | — | — | |
| REL-SNAP-026 | OK | — | 837 | — | — |
Identity
- Record key
mcp.sap.oobeprotocol.ai/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- ai.oobeprotocol.sap.mcp/sap-mcp What the registry said when we swept it, as observed by us — not evidence that the registry was correct, that the name belongs to whoever registered it, or that it still resolves. Not covered by the chain: no inclusion proof reaches this field.
- Name reported by the server
- sap-mcp-server Self-reported and unverified — never used as identity.
Verifying this record
Each observation above carries a merkle leaf in the published snapshot it belongs to. Verify the chain explains how to walk a leaf to a published root without taking our word for any of it.