AGTS MCP Server
Connect your coding agent to a hosted MCP gateway that wraps 64 tools with policy governance and an auditable Merkle transparency log for EU AI Act and SOC 2–aligned workflows.
Overview
AGTS MCP Server is a MCP server for the Ship phase that provides a sovereign hosted gateway with 64 governed tools and a Merkle transparency log for audit-ready agent integrations.
What is this MCP server?
- 64 governed MCP tools exposed through a single sovereign gateway endpoint
- Merkle transparency log for tamper-evident audit of tool and gateway activity
- Positioned as EU AI Act and SOC 2 ready for compliance-conscious agent deployments
- Remote access via streamable HTTP and SSE at agts-mcp.obligationsign.com
- Published server schema 2025-12-11 with version 1.0.1 and GitHub source ObligationSign/agts-mcp
- 64 governed tools advertised on the gateway
- Server version 1.0.1 in the published MCP server manifest
- Two remote transports: streamable-http and SSE on agts-mcp.obligationsign.com
What problem does it solve?
Solo builders stitching together many MCP tools lack a single governed endpoint and verifiable audit trail when regulators or customers ask what their agent actually did.
Who is it for?
Indie builders and small teams shipping agent products who want one compliance-oriented MCP remote instead of unmanaged tool sprawl.
Skip if: Builders who only need a single local MCP integration with no governance, logging, or compliance documentation requirements.
What do I get? / Deliverables
After registering the remote MCP URL in your agent, tool calls route through ObligationSign’s gateway with governed access and transparency-log semantics aligned with EU AI Act and SOC 2 messaging.
- Agent configured to call the AGTS remote MCP endpoint (HTTP or SSE)
- Access to the gateway’s catalog of 64 governed tools through one integration
- Audit-oriented workflow grounded in the advertised Merkle transparency log model
Recommended MCP Servers
Journey fit
Governance, compliance framing, and auditability belong on the shipping path where indie builders harden how agents call external tools before production or regulated use. Security is the canonical shelf because the server’s value proposition is sovereign tool control, transparency logging, and readiness labels for EU AI Act and SOC 2—not generic API wiring.
How it compares
Hosted compliance-oriented MCP gateway with 64 governed tools, not a single-purpose agent skill or generic marketplace listing.
Common Questions / FAQ
Who is AGTS MCP Server for?
It is for solo builders and small teams using Claude Code, Cursor, or Codex who want a centralized, governed MCP endpoint with audit-oriented transparency logging.
When should I use AGTS MCP Server?
Use it during Ship when you are hardening agent tool access, preparing for SOC 2–style reviews, or aligning agent workflows with EU AI Act expectations before wider launch.
How do I add AGTS MCP Server to my agent?
Add the published remote MCP URL (streamable-http at https://agts-mcp.obligationsign.com/mcp or SSE at https://agts-mcp.obligationsign.com/mcp/sse) in your client’s MCP server configuration per obligationsign.com/mcp documentation.