mcp.jojapi.com/sms-verify

Last observed:— recorded as OK

Observations

Every observation recorded for this endpoint, oldest first. Each row is a separate look, not a summary.
ObservedSnapshotRecorded asDetailLatency (ms)ToolsTool schema fingerprint
REL-SNAP-016OK1612834870f0980c9006…
REL-SNAP-017OK692834870f0980c9006…
REL-SNAP-018OK612834870f0980c9006…
REL-SNAP-019OK522834870f0980c9006…
REL-SNAP-020OK1522834870f0980c9006…
REL-SNAP-021OK652834870f0980c9006…
REL-SNAP-022OK582834870f0980c9006…
REL-SNAP-023OK552834870f0980c9006…
REL-SNAP-024OK1442834870f0980c9006…
REL-SNAP-025OK1702834870f0980c9006…
REL-SNAP-026OK1622834870f0980c9006…

Identity

Record key
mcp.jojapi.com/sms-verify — the normalised endpoint observed. See the methodology for the rule.
Transport
streamable-http
Registry names (not anchored)
com.jojapi/sms-verify 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
jojapi-sms-verify 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.

Plain-text version of this page