Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AGTS MCP Server

REMOTE · AGTS-MCP.OBLIGATIONSIGN.COM · 2 COMPONENTS · SCANNED AUG 24

Sovereign MCP Gateway — 64 governed tools with Merkle transparency log. EU AI Act and SOC 2 ready.

−4 this week 0 Trust /100

Dead

Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security11
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety

Not scored yet: our latest scan of this component recorded no findings here. It fills in the next time we score it.

Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 4 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Install

How do I install the AGTS MCP Server server?

AGTS MCP Server is a hosted endpoint at https://agts-mcp.obligationsign.com/mcp/sse, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · agts-mcp.obligationsign.com

# add to Claude Code
claude mcp add --transport http obligationsign-agts-mcp 'https://agts-mcp.obligationsign.com/mcp/sse'
// .cursor/mcp.json
{
  "mcpServers": {
    "obligationsign-agts-mcp": {
      "url": "https://agts-mcp.obligationsign.com/mcp/sse"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "obligationsign-agts-mcp": {
      "type": "http",
      "url": "https://agts-mcp.obligationsign.com/mcp/sse"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.obligationsign-agts-mcp]
url = "https://agts-mcp.obligationsign.com/mcp/sse"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "obligationsign-agts-mcp": {
      "type": "remote",
      "url": "https://agts-mcp.obligationsign.com/mcp/sse",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add obligationsign-agts-mcp --url 'https://agts-mcp.obligationsign.com/mcp/sse' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  obligationsign-agts-mcp:
    url: "https://agts-mcp.obligationsign.com/mcp/sse"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "obligationsign-agts-mcp": {
      "Transport": "http",
      "Url": "https://agts-mcp.obligationsign.com/mcp/sse"
    }
  }
}
# add to Vellum
assistant mcp add obligationsign-agts-mcp -t streamable-http -u 'https://agts-mcp.obligationsign.com/mcp/sse'
// mcp.json
{
  "mcpServers": {
    "obligationsign-agts-mcp": {
      "type": "http",
      "url": "https://agts-mcp.obligationsign.com/mcp/sse"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 24 Aug 26 −4

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 3

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 24 Aug 2026 · Probed https://agts-mcp.obligationsign.com/mcp/sse

TLS unreached
DNSSEC inconclusive

Validation of agts-mcp.obligationsign.com. Inconclusive

Zone DS Keys Algorithms Outcome
agts-mcp.obligationsign.com. Error no A/AAAA/CNAME RRset answered for the name
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
sse https://agts-mcp.obligationsign.com/mcp/sse Unreachable
http (plaintext) http://agts-mcp.obligationsign.com/mcp/sse HTTPS enforced
MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

No tool schema has been captured from this endpoint yet.

Common questions

What is the AGTS MCP Server server?

AGTS MCP Server is listed in the public MCP registry as io.github.ObligationSign/agts-mcp. Sovereign MCP Gateway, 64 governed tools with Merkle transparency log. EU AI Act and SOC 2 ready. This page covers its hosted endpoint (https://agts-mcp.obligationsign.com/mcp/sse).

Is the AGTS MCP Server server safe to use?

AGTS MCP Server scores 0 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

Does the AGTS MCP Server server require authentication?

Its publisher declares no required credentials for AGTS MCP Server. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the AGTS MCP Server server still maintained?

AGTS MCP Server has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.