saaskr.com/api/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-006 | OK | — | 1268 | 5 | 8fa8085fb4ac335b… | |
| REL-SNAP-007 | OK | — | 1566 | 5 | 8fa8085fb4ac335b… | |
| REL-SNAP-008 | OK | — | 1441 | 5 | 8fa8085fb4ac335b… | |
| REL-SNAP-009 | OK | — | 1216 | 5 | 8fa8085fb4ac335b… | |
| REL-SNAP-010 | OK | — | 1245 | 5 | 8fa8085fb4ac335b… | |
| REL-SNAP-011 | OK | — | 1329 | 5 | 8fa8085fb4ac335b… | |
| REL-SNAP-012 | OK | — | 1312 | 5 | 8fa8085fb4ac335b… | |
| REL-SNAP-013 | OK | — | 1284 | 5 | 8fa8085fb4ac335b… | |
| REL-SNAP-014 | OK | — | 1384 | 5 | 8fa8085fb4ac335b… | |
| REL-SNAP-015 | OK | — | 979 | 5 | 8fa8085fb4ac335b… | |
| REL-SNAP-016 | OK | — | 939 | 5 | 8fa8085fb4ac335b… | |
| REL-SNAP-017 | OK | — | 978 | 5 | 8fa8085fb4ac335b… | |
| REL-SNAP-018 | OK | — | 693 | 5 | 8fa8085fb4ac335b… | |
| REL-SNAP-019 | OK | — | 583 | 5 | 8fa8085fb4ac335b… | |
| REL-SNAP-020 | OK | — | 561 | 5 | 8fa8085fb4ac335b… | |
| REL-SNAP-021 | OK | — | 1037 | 5 | 8fa8085fb4ac335b… | |
| REL-SNAP-022 | OK | — | 1115 | 5 | 8fa8085fb4ac335b… | |
| REL-SNAP-023 | OK | — | 1311 | 5 | 8fa8085fb4ac335b… | |
| REL-SNAP-024 | OK | — | 1046 | 5 | 8fa8085fb4ac335b… | |
| REL-SNAP-025 | OK | — | 762 | 5 | 8fa8085fb4ac335b… | |
| REL-SNAP-026 | OK | — | 1052 | 5 | 8fa8085fb4ac335b… |
Identity
- Record key
saaskr.com/api/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- com.saaskr/korean-saas-directory 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
- saaskr 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.