api.mcp.ai/p_sefaz_rn_nfce_resumida

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-016OK5367fc4dc30543b9e0e2…
REL-SNAP-017OK2247fc4dc30543b9e0e2…
REL-SNAP-018OK2397fc4dc30543b9e0e2…
REL-SNAP-019OK2257fc4dc30543b9e0e2…
REL-SNAP-020OK2757fc4dc30543b9e0e2…
REL-SNAP-021OK2757fc4dc30543b9e0e2…
REL-SNAP-022OK2797fc4dc30543b9e0e2…
REL-SNAP-023OK2287fc4dc30543b9e0e2…
REL-SNAP-024OK2207fc4dc30543b9e0e2…
REL-SNAP-025OK5187fc4dc30543b9e0e2…
REL-SNAP-026OK2617fc4dc30543b9e0e2…

Identity

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