leaseiq-pro.mcpize.run/mcp

Last observed:— recorded as HTTP_5XX (http_502)

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-002OK3701
REL-SNAP-003OK3482
REL-SNAP-004OK3736
REL-SNAP-005OK3237
REL-SNAP-006OK3454
REL-SNAP-007OK3335
REL-SNAP-008OK4090
REL-SNAP-009OK3314
REL-SNAP-010OK3630
REL-SNAP-011OK3347
REL-SNAP-012OK3370
REL-SNAP-013OK3311
REL-SNAP-014OK3680
REL-SNAP-015OK2145
REL-SNAP-016OK2248
REL-SNAP-017OK2009
REL-SNAP-018OK1937
REL-SNAP-019OK2071
REL-SNAP-020OK2137
REL-SNAP-021OK2050
REL-SNAP-022OK2277
REL-SNAP-023OK2503
REL-SNAP-024OK2165
REL-SNAP-025OK2303
REL-SNAP-026HTTP_5XXhttp_502

Identity

Record key
leaseiq-pro.mcpize.run/mcp — the normalised endpoint observed. See the methodology for the rule.
Transport
streamable-http
Registry names (not anchored)
io.github.glennl201/leaseiq-pro 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
Not reported. 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