china-export-rebate-mcp.rainbow686.workers.dev/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-005OK383fb762f49514c9f46…
REL-SNAP-006OK443fb762f49514c9f46…
REL-SNAP-007OK973fb762f49514c9f46…
REL-SNAP-008OK983fb762f49514c9f46…
REL-SNAP-009OK353fb762f49514c9f46…
REL-SNAP-010OK453fb762f49514c9f46…
REL-SNAP-011OK25313fb762f49514c9f46…
REL-SNAP-012OK23133fb762f49514c9f46…
REL-SNAP-013OK25503fb762f49514c9f46…
REL-SNAP-014OK22873fb762f49514c9f46…
REL-SNAP-015OK4403fb762f49514c9f46…
REL-SNAP-016OK3873fb762f49514c9f46…

Identity

Record key
china-export-rebate-mcp.rainbow686.workers.dev/mcp — the normalised endpoint observed. See the methodology for the rule.
Transport
streamable-http
Registry names (not anchored)
io.github.rainbow686/china-export-rebate-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
china-export-rebate 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