datacommenter.com/wp-json/tdc/v1/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-002OK824174011e6522b517191…
REL-SNAP-003OK837174011e6522b517191…
REL-SNAP-004OK859174011e6522b517191…
REL-SNAP-005OK854174011e6522b517191…
REL-SNAP-006OK942174011e6522b517191…
REL-SNAP-007OK844174011e6522b517191…
REL-SNAP-008OK876174011e6522b517191…
REL-SNAP-009OK832174011e6522b517191…
REL-SNAP-010OK904174011e6522b517191…
REL-SNAP-011OK887174011e6522b517191…
REL-SNAP-012OK897174011e6522b517191…
REL-SNAP-013OK922174011e6522b517191…
REL-SNAP-014OK841174011e6522b517191…
REL-SNAP-015OK622174011e6522b517191…
REL-SNAP-016OK619174011e6522b517191…

Identity

Record key
datacommenter.com/wp-json/tdc/v1/mcp — the normalised endpoint observed. See the methodology for the rule.
Transport
streamable-http
Registry names (not anchored)
com.datacommenter/the-data-commenter 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
the-data-commenter 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