api.mcp.ai/p_tribunal_trf2_certidao

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-016OK2407ef37b9c2163c6df4…
REL-SNAP-017OK2607ef37b9c2163c6df4…
REL-SNAP-018OK3197ef37b9c2163c6df4…
REL-SNAP-019OK2637ef37b9c2163c6df4…
REL-SNAP-020OK2217ef37b9c2163c6df4…
REL-SNAP-021OK2867ef37b9c2163c6df4…
REL-SNAP-022OK2287ef37b9c2163c6df4…
REL-SNAP-023OK2377ef37b9c2163c6df4…
REL-SNAP-024OK2337ef37b9c2163c6df4…
REL-SNAP-025OK3277ef37b9c2163c6df4…
REL-SNAP-026OK2377ef37b9c2163c6df4…

Identity

Record key
api.mcp.ai/p_tribunal_trf2_certidao — the normalised endpoint observed. See the methodology for the rule.
Transport
streamable-http
Registry names (not anchored)
io.github.mcp-dir/tribunal_trf2_certidao-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
mcp-ai 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