api.envoisms.ma/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-008OK395f5a335723b8652a0…
REL-SNAP-009OK405f5a335723b8652a0…
REL-SNAP-010OK3957b5d61a80e15e2e4…
REL-SNAP-011OK305f5a335723b8652a0…
REL-SNAP-012OK875f5a335723b8652a0…
REL-SNAP-013OK305f5a335723b8652a0…
REL-SNAP-014OK3757b5d61a80e15e2e4…
REL-SNAP-015OK5057b5d61a80e15e2e4…
REL-SNAP-016OK4957b5d61a80e15e2e4…

Tool schema changed 3 times across this history — the fingerprint differs between consecutive observations. A change can occur while the tool count stays identical, which is why the fingerprint is recorded alongside the count.

Identity

Record key
api.envoisms.ma/v1/mcp — the normalised endpoint observed. See the methodology for the rule.
Transport
streamable-http
Registry names (not anchored)
ma.envoisms/envoisms 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
EnvoiSMS Platform MCP Server 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