原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

AGTS MCP Server

作者:ObligationSign版本 1.0.1i★ 0i在云端运行官方网站 ↗
注册名称io.github.ObligationSign/agts-mcp

安装方法

What it does

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

  • Connects 在云端运行
  • Account or key No key needed
  • Category 网络安全

为什么排在这里

列表按使用分(满分 100)排序,由以下部分组成

热度0/80GitHub 星标或每周下载量:较大的计 60,较小的计 20
新鲜度3/1230 天内有发布或代码更新得满分
仍在响应0/8上次检查时云端端点有响应
使用分3/100

质量: 基础检查通过 1/4 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)

安装

选择你使用的 AI 应用,然后复制设置。

通过 1/4 项检查 · 在你的电脑上运行

我们隐藏了部分命令

通过地址连接:检查时服务器地址没有响应

还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器 · 作者的安装说明 · 同类的其他服务器

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

Claude 暂时无法连接 AGTS MCP Server

还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器

ChatGPT 暂时无法连接 AGTS MCP Server

还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器

你可以改用这些方式

B · 网络安全 类中能连接 ChatGPT 的其他服务器

从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的

Claude Code 暂时无法连接 AGTS MCP Server

还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器

Cursor 暂时无法连接 AGTS MCP Server

还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器

VS Code 暂时无法连接 AGTS MCP Server

还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器

还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器

卡住了?问问正在用 AGTS MCP Server 的人💬 讨论 →

一览

每周下载量i
不在 npm/PyPI 上
许可证i
未注明许可证
连接方式
在云端运行
传输方式
streamable-http, sse
最新版本i
1.0.1
发布到注册中心i
2026年4月14日
代码最后更新i
2026年5月13日
最近检查
2026年11月16日
作者
ObligationSign
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

通过互联网连接,适用于

GooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

全部应用及其优缺点 →

它能做什么

我们上次检查时服务器没有响应,所以无法读取它的工具。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 ObligationSign 验证,该账户拥有此仓库

  • ! 注意

    仍在维护

    代码最后更新于6个月前,已超过 6 个月

  • ✕ 未通过

    有许可证

    仓库中没有找到许可证文件

  • ✕ 未通过

    端点有响应

    我们检查时,6 秒内没有响应

  • – 不适用

    使用 OAuth 登录

    我们检查时,6 秒内没有响应

  • … 尚未检查

    工具描述中没有隐藏指令

    尚未检查;我们会在检查端点时读取工具列表

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/obligationsign-agts-mcp-a9r98.svg)](https://mcp.popnx.com/en/servers/obligationsign-agts-mcp-a9r98)

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

与“网络安全”中的其他服务器比较i

  • 星标数多于此分类中其他 1106 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 1106 个服务器的 10% 更新
  • 基础检查结果等于或优于此分类中其他 1106 个服务器的 8%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

AGTS MCP Server 安全吗?

它在 4 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。

它还在维护吗?

GitHub 仓库最后更新于6个月前,最新版本(1.0.1)于7个月前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。

有什么可以替代它?

同一分类中有:GitHits, Dependency Management MCP Server, Snyk MCP, TokenSafe, Draugr

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

GitHits

Search public open-source code, documentation, metadata, vulnerabilities, changelogs, and examples.

作者:githits-com正在增长↓ 3807/周★ 13810天前更新

电脑或云端✓ 服务方 · githits.com

Snyk MCP

Easily find and fix security issues in your applications leveraging Snyk platform capabilities.

作者:snyk广泛使用↓ 76.2万/周★ 617个月前更新

在你的电脑上运行✓ 服务方 · snyk.io

TokenSafe

Your AI agent is smart enough to code all day. Local firewall & zero-loss runtime.

作者:tokensafe-dev广泛使用↓ 6785/周★ 46今天更新

电脑或云端✓ 服务方 · tokensafe.dev

Draugr

Security scanning for AI agents: SAST, SCA, secrets, IaC, DAST, ranked by real risk.

作者:draugr-dev起步阶段★ 30前天更新

在你的电脑上运行✓ 服务方 · draugr.dev
与相似项目对比
本项
AGTS MCP Server
GitHitsDependency Management MCP ServerSnyk MCPTokenSafeDraugr
运行位置在云端运行,无需安装云端或安装在电脑上都可以在云端运行,无需安装需要安装在电脑上云端或安装在电脑上都可以需要安装在电脑上
需要密钥否否否否否否
可在 Claude 中按 + 添加否否否否否否
基础检查1/45/53/43/35/53/3
许可证–Apache-2.0–Apache-2.0MITApache-2.0
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

AGTS MCP Server

Sovereign MCP Gateway — Governed Tool Invocation for Autonomous Agents

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.


Server URL

https://mcp.obligationsign.com/mcp
TransportURLStatus
Streamable HTTP (primary)https://mcp.obligationsign.com/mcpActive
SSE (deprecated)https://mcp.obligationsign.com/mcp/sseDeprecated

Authentication

The gateway requires a Bearer token issued through the ObligationSign platform. All requests must include an Authorization header.

To obtain a token, register at obligationsign.com/start/.

Quick Start

Claude Desktop / Cursor / Windsurf

Add to your MCP configuration:

{

"mcpServers": { "agts": { "url": "https://mcp.obligationsign.com/mcp", "headers": { "Authorization": "Bearer YOUR_TOKEN" } } } }

Programmatic (JSON-RPC over HTTP)
curl -X POST https://mcp.obligationsign.com/mcp \

-H "Content-Type: application/json" \ -H "Authorization: Bearer YOUR_TOKEN" \ -d '{ "jsonrpc": "2.0", "id": 1, "method": "tools/list", "params": {} }'


What is AGTS?

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.

decision → record → immutable history → verifiable truth

Every tool call passes through a five-gate firewall (Statistical, Causal, Regression, Evidence, Human-Compatible Explanation) before execution. Admitted actions are Merkle-anchored into an append-only transparency log and signed with hybrid post-quantum cryptography.


Cryptography & Validator Quorum

Every governance envelope produced by this server is signed with a hybrid post-quantum signature: classical Ed25519 in parallel with SLH-DSA-SHAKE-128f. The signature is verifiable today with Ed25519-only tooling and remains forgery-resistant against future quantum adversaries via SLH-DSA. Sovereign Mail additionally uses ML-KEM-512 for encrypted key exchange, and peer-trust ceremonies use ML-DSA-44.

Admit decisions for governed tool calls require an independent 3-of-4 validator quorum with constraint regulator_count ≥ 1 and auditor_count ≥ 1. Validators are deployed as separate Cloudflare Workers (agts-validator-{a,b,c,d}) with distinct ECDSA P-256 keypairs; each validator independently re-evaluates the proof bundle and signs an AGTS_VOTE_V1 certificate. The quorum certificate is then anchored alongside the governance envelope in the Merkle transparency log, so any external party can reconstruct the four signed votes and verify that quorum was honestly met.

Tool Catalog (115+ Tools)

Layer 1 — Infrastructure
VPN & Network
ToolDescription
create_tunnelEstablish an attested VPN tunnel (WireGuard/IPSec/TLS)
tunnel_statusMonitor uptime, transfer bytes, and attestation status
disconnect_tunnelTerminate session and log the event
dns_querySecure DNS resolution through the Sovereign resolver
Monitor
ToolDescription
system_healthProbe all mesh workers for status and latency
check_alertsFetch the monitor alert timeline
subscribe_alertsWebhook subscription for real-time alerts
check_equivocationsFetch conflicting Signed Tree Head proofs
gossip_statusCurrent state of gossip protocol and monitor identity
Layer 2 — Identity & Communications
Sovereign Mail
ToolDescription
send_sovereign_mailSend encrypted (internal) or plaintext (external) messages
list_inboxList message metadata from an inbox
read_messageRetrieve full message content by ID
lookup_recipient_keysRetrieve public keys (ECDH P-384 / ML-KEM-512)
Sovereign Drive
ToolDescription
upload_fileClient-side encrypted upload with integrity anchoring
list_filesList file metadata, sizes, and sharing status
download_fileRetrieve ciphertext for client-side decryption
share_fileShare files using ECDH key wrapping
delete_fileRemove a file and create a death leaf in the log
OpenClaw (Agent Identity)
ToolDescription
register_clawCreate a cryptographic Claw Passport and identity keys
scan_skillScan agent skills through the five-gate firewall
claw_statusReturn trust score, governance history, and quota
export_passportSecure export of the identity envelope
govern_skill_execHigh-level gate for skill execution
report_skill_executionLink skill results to authorization
verify_skill_proofCryptographic verification of skill scans
Peer Trust (Post-Quantum)
ToolDescription
authenticate_peerHybrid PQC (ML-DSA-44) + Classical (ECDSA) auth ceremony
verify_agent_identityFingerprint and revocation check via key registry
exchange_credentialsSecure transport using hybrid ECDH + ML-KEM-512
peer_trust_networkList known peers and mutual trust status
Layer 3 — Governance
ToolDescription
submit_governancePre-execution gate evaluation (ADMIT/QUARANTINE/REFUSE)
verify_commitmentVerify commitment in transparency log with Merkle proofs
report_executionLog outcome of an authorized action
update_policyUpdate firewall parameters
list_policiesList active governance thresholds and history
governance_reportAggregated decision reporting
governance_statsPer-gate pass/fail statistics and HCE distribution
gate_analysisDetailed breakdown of a specific evaluation decision
Layer 4 — Memory
ToolDescription
memory_storeStore hierarchical key-value entries
memory_recallRetrieve specific entries by path
memory_listPrefix-based listing of memories
memory_searchSemantic similarity search using vector embeddings
cross_session_recallSemantic search across historical sessions
memory_contextMode-based contextual summary
consolidate_memoryCompare and compact redundant entries
memory_gcGarbage collection of stale entries
set_memory_ttlConfigure automatic expiration for entries
memory_deleteRemove specific memory paths
Layer 5 — Billing
ToolDescription
provision_resourceCreate a billing project for an agent
manage_spendingFreeze/unfreeze spending
check_project_billingDetailed usage and charge breakdown
verify_provisionCheck billing project linkage
set_budget_alertConfigure spending thresholds
check_budgetReal-time spend vs. cap tracking
Layer 6 — Orchestration
ToolDescription
spawn_sub_agentLaunch an isolated asynchronous sub-agent
sub_agent_statusPoll sub-agent execution status
sub_agent_resultRetrieve sub-agent results
chain_delegationRecursive delegation with budget decay and depth limits
create_templateDefine a reusable multi-step workflow
apply_templateInstantiate a template into a running task
list_sub_agentsList active sub-agents
list_templatesList available workflow templates
cancel_sub_agentTerminate a running sub-agent
merge_sub_resultsAggregate results from parallel sub-agents
delegation_treeReconstruct the full lineage of a delegated chain

REST API

In addition to MCP, the gateway exposes REST endpoints:

EndpointDescription
GET /api/v1/healthUpstream service health checks
GET /api/v1/auditAudit log queries
GET /api/v1/assetsAsset management
GET /verify?commitment={hash}Commitment verification with Merkle proof

Architecture

The MCP server is one access surface to the AGTS protocol. The full clearinghouse specification is published separately.

Agent ─── MCP Gateway ─── Five-Gate Firewall ─── Transparency Log

│ │ ├── Mail Worker (E2EE) ├── Merkle Tree ├── Drive Worker (Encrypted Storage) ├── Signed Tree Heads ├── OpenClaw (Identity) └── Gossip Protocol ├── Tunnel Worker (VPN) ├── Monitor Worker (Health) └── Protocol Worker (Governance)


How This Server Differs

Most MCP servers in the ecosystem (~83%) are thin API wrappers — a single connector exposed as one or two tools, running locally via stdio, with no authentication or validation. The production-tier servers from vendors like GitHub, Slack, and AWS (~2%) are well-built but architecturally simple: they translate tools/call into API requests for their own service.

This server operates at a different level. It is not a wrapper around an external API — it implements a full governance protocol where:

  • Every action must pass through five evaluation gates before execution is authorized
  • Admitted actions are cryptographically signed (hybrid Ed25519 + SLH-DSA) and Merkle-anchored in an append-only transparency log
  • Execution outcomes are traced back to their authorization, creating a closed governance loop
  • Independent monitors verify log consistency through a gossip protocol, detecting equivocation or tampering
  • Identity is handled through post-quantum cryptography (ML-DSA-44, ML-KEM-512) for forward security

The result is that every tool call produces independently verifiable cryptographic evidence of what was authorized, what was executed, and whether the outcome matched the authorization — the kind of audit trail required in regulated industries (financial services, healthcare, legal, critical infrastructure).

Regulatory Readiness

The gateway's architecture is designed to support compliance across multiple regulatory frameworks. The table below maps specific requirements to the AGTS features that address them.

EU AI Act
RequirementAGTS Implementation
Art. 9 — Risk managementFive-gate firewall evaluates every action before execution; QUARANTINE decisions enable human intervention
Art. 12 — Record-keepingAppend-only Merkle transparency log with signed governance envelopes; automatic recording of every authorization and execution event
Art. 13 — TransparencyEvery commitment is independently verifiable with cryptographic inclusion proofs; governance decisions are explainable via the HCE (Human-Compatible Explanation) gate
Art. 14 — Human oversightGate thresholds are configurable; QUARANTINE/REFUSE decisions halt execution; policy updates are themselves governed and logged
SOC 2
Trust PrincipleAGTS Implementation
SecurityHybrid Ed25519 + SLH-DSA signing; post-quantum key exchange (ML-KEM-512); Cloudflare Access authentication with email binding; per-tool rate limiting
AvailabilityMulti-worker mesh architecture with independent health monitoring; gossip protocol detects node failures; system_health probes all upstream services

| Processing Integrity | Five-gate firewall validates every action before execution; execution outcomes are traced back to authorization; variance dete

只显示了开头部分;其余内容请在仓库中阅读