api.humantaste.app/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-002OK52820266238cd4949ed26…
REL-SNAP-003OK54020266238cd4949ed26…
REL-SNAP-004OK56720266238cd4949ed26…
REL-SNAP-005OK57020266238cd4949ed26…
REL-SNAP-006OK53420266238cd4949ed26…
REL-SNAP-007OK55420266238cd4949ed26…
REL-SNAP-008OK60820266238cd4949ed26…
REL-SNAP-009OK56520266238cd4949ed26…
REL-SNAP-010OK59720266238cd4949ed26…
REL-SNAP-011OK58220266238cd4949ed26…
REL-SNAP-012OK56520266238cd4949ed26…
REL-SNAP-013OK55320266238cd4949ed26…
REL-SNAP-014OK57120266238cd4949ed26…
REL-SNAP-015OK61320266238cd4949ed26…
REL-SNAP-016OK44820266238cd4949ed26…

Identity

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