AGTS MCP Server

AGTS MCP server exists for a simple reason — assistants are far more useful when they can act on AGTS directly instead of describing what you should do. Sovereign MCP Gateway — 64 governed tools with Merkle transparency log. EU AI Act ready.

What you get

Model Context Protocol server that turns tool calls into cryptographically authorized, verifiable actions. 115+ governed tools across 6 layers — hybrid Ed25519 + SLH-DSA signed and Merkle-anchored. Designed to support EU AI Act, GDPR, SOC 2, ISO 27001, DORA, NIS2, and FINRA compliance.

AGTS (Autonomous Governance Transparency Standard) is a transparency-backed governance protocol that converts validated machine decisions into append-only cryptographic records, independently verified by a network of witnesses and monitors.

What the assistant can call

Once AGTS is connected, these are the calls the assistant has available:

• Endpoint — Description
• Monitor — The Monitor tool exposed by this server
• GDPR — The GDPR tool exposed by this server
• NIS2 — The NIS2 tool exposed by this server
• FINRA — The closest comparable in the market is not another MCP server — it is what a regulated enterprise would build internally to control what their AI

Configuration and credentials

You will need one environment variable: YOUR_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. AGTS's toolset — Endpoint, Monitor, GDPR and 2 more — is a fair guide to whether it matches your workflow. It is maintained by com.obligationsign.mcp; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the agts mcp server does with a few real requests.