api.pimea.ai/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-002OK6663b8361daae922b334…
REL-SNAP-003OK6823b8361daae922b334…
REL-SNAP-004OK7133b8361daae922b334…
REL-SNAP-005OK8033b8361daae922b334…
REL-SNAP-006OK6893b8361daae922b334…
REL-SNAP-007OK6163b8361daae922b334…
REL-SNAP-008OK6703b8361daae922b334…
REL-SNAP-009OK7943b8361daae922b334…
REL-SNAP-010OK5733b8361daae922b334…
REL-SNAP-011OK7443b8361daae922b334…
REL-SNAP-012OK6773b8361daae922b334…
REL-SNAP-013OK7033b8361daae922b334…
REL-SNAP-014OK6813b8361daae922b334…
REL-SNAP-015OK1003b8361daae922b334…
REL-SNAP-016OK2013b8361daae922b334…

Identity

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