Decionis MCP

Decionis publishes @decionis/mcp, a Model Context Protocol server that reads a repository's DECIONIS_POLICY.md and evaluates candidate agent actions against it before they run. In its default local mode the server operates over stdio with, per its own documentation, zero network access, zero credentials, and nothing recorded; an opt-in remote mode instead sends evaluation requests to protocol.decionis.com. The repository lists three tools: decionis_read_policy, decionis_evaluate, and decionis_verdict_help. The registry record separately names two Presence-verification tools gated behind an optional DECIONIS_PRESENCE_API_KEY, added with the 0.2.0 release on 2026-09-14, after the documented repository's last push; they are not confirmed in the fetched tool list and are not counted above.

Authority rests on decionis.com, a domain-verified surface: the GitHub organization decionis carries a verified badge listing decionis.com as its site, and decionis.com/docs/protocol-mcp documents @decionis/mcp as its own product. The registry record's repository field, however, points to https://github.com/decionis/agent-safe-pipeline, a real and active Decionis monorepo that contains no trace of this server's code anywhere in its tree. The repository that actually documents @decionis/mcp is a separate one, https://github.com/decionis/mcp, whose own README states that the published npm package's source of truth lives in a private Decionis platform monorepo, and that this public repository exists only to host setup guides, samples, and issue reports; repo_url here points at that repository rather than the one the registry cites.

The documented remote endpoint at https://protocol.decionis.com/mcp is live. A plain GET sent without a JSON-RPC body returned a self-descriptive JSON document naming streamable_http as its transport and listing supported protocol versions through 2025-11-25, advertised metadata rather than a negotiated session. Separate probes on 2026-09-15, a server/discover at protocol revision 2026-07-28 and a legacy initialize at 2025-11-25, both returned HTTP 401 with a WWW-Authenticate header pointing at the endpoint's own OAuth protected-resource metadata, an invalid_token error, and a JSON-RPC error body. No probe or document negotiated a revision, so spec support remains unverified.