api.theartofservice.com/mcp

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-002OK4261040277c0e3cb006ea…
REL-SNAP-003OK4351040277c0e3cb006ea…
REL-SNAP-004OK438
REL-SNAP-005OK435
REL-SNAP-006OK4391040277c0e3cb006ea…
REL-SNAP-007OK860
REL-SNAP-008OK9551040277c0e3cb006ea…
REL-SNAP-009OK1287
REL-SNAP-010OK4341040277c0e3cb006ea…
REL-SNAP-011OK8761040277c0e3cb006ea…
REL-SNAP-012OK490
REL-SNAP-013OK884
REL-SNAP-014OK138816aaaf8f9b58f1e5e8…
REL-SNAP-015OK145
REL-SNAP-016OK160

Identity

Record key
api.theartofservice.com/mcp — the normalised endpoint observed. See the methodology for the rule.
Transport
streamable-http
Registry names (not anchored)
io.github.GJB65/compliance-intelligence, com.theartofservice/compliance-intelligence 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.more than one registry name refers to this single endpoint. We record both rather than choosing between them; the observation covers the endpoint and cannot be attributed to one of them.
Name reported by the server
TheArtOfService Compliance Intelligence 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