www.machupicchu.org/wp-json/wonders-mcp/v1/jsonrpc

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-002OK3590
REL-SNAP-003OK2943
REL-SNAP-004OK2798
REL-SNAP-005OK2662
REL-SNAP-006OK2336
REL-SNAP-007OK3762
REL-SNAP-008OK2411
REL-SNAP-009OK2323
REL-SNAP-010OK2668
REL-SNAP-011OK3864
REL-SNAP-012OK2239
REL-SNAP-013OK2615
REL-SNAP-014OK2289
REL-SNAP-015OK1285
REL-SNAP-016OK1608
REL-SNAP-017OK3360
REL-SNAP-018OK1266
REL-SNAP-019OK1346
REL-SNAP-020OK1353
REL-SNAP-021OK1262
REL-SNAP-022OK1690
REL-SNAP-023OK1561
REL-SNAP-024OK1409
REL-SNAP-025OK1234
REL-SNAP-026OK3112

Identity

Record key
www.machupicchu.org/wp-json/wonders-mcp/v1/jsonrpc — the normalised endpoint observed. See the methodology for the rule.
Transport
streamable-http
Registry names (not anchored)
org.machupicchu/wonders-mcp 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
wonders-mcp 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