GitHits
Search public open-source code, documentation, metadata, vulnerabilities, changelogs, and examples.
Sovereign MCP Gateway — 64 governed tools with Merkle transparency log. EU AI Act and SOC 2 ready.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 0/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 3/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 3/100 |
Quality: Passed 1/4 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Passed 1/4 checks · Runs on your computer
We hid some of the commands
Connect by URL: the server address did not answer when we checked
No install path has passed yet. See the maker’s instructions or pick another server in this category · Maker’s install instructions · Others in this category
First: which AI do you use?
Pick your app and the steps appear below.
Claude cannot connect AGTS MCP Server yet
No install path has passed yet. See the maker’s instructions or pick another server in this category
ChatGPT cannot connect AGTS MCP Server yet
No install path has passed yet. See the maker’s instructions or pick another server in this category
B · Others in Cybersecurity that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Claude Code cannot connect AGTS MCP Server yet
No install path has passed yet. See the maker’s instructions or pick another server in this category
Cursor cannot connect AGTS MCP Server yet
No install path has passed yet. See the maker’s instructions or pick another server in this category
VS Code cannot connect AGTS MCP Server yet
No install path has passed yet. See the maker’s instructions or pick another server in this category
No install path has passed yet. See the maker’s instructions or pick another server in this category
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Connect over the internet in
GooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
The server did not answer when we last checked, so we could not read its tools.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
The registry name was verified with the GitHub account ObligationSign, which owns the repo
Code last changed 6 months ago, more than 6 months ago
No licence file found in the repo
Did not respond within 6 seconds when we checked
Did not respond within 6 seconds when we checked
Not checked yet; we read the tool list when we check the endpoint
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/obligationsign-agts-mcp-a9r98)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 4 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed 6 months ago, and the latest version (1.0.1) reached the registry 7 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT on the web (full MCP on Business and above; Pro read-only).
In the same category: GitHits, Dependency Management MCP Server, Snyk MCP, TokenSafe, Draugr
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Search public open-source code, documentation, metadata, vulnerabilities, changelogs, and examples.
Sonatype component intelligence: versions, security analysis, and Trust Score recommendations
Easily find and fix security issues in your applications leveraging Snyk platform capabilities.
Security scanning for AI agents: SAST, SCA, secrets, IaC, DAST, ranked by real risk.
| This one AGTS MCP Server | GitHits | Dependency Management MCP Server | Snyk MCP | TokenSafe | Draugr | |
|---|---|---|---|---|---|---|
| Runs where | Runs in the cloud, nothing to install | Cloud or install on your computer | Runs in the cloud, nothing to install | Installs on your computer | Cloud or install on your computer | Installs on your computer |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 1/4 | 5/5 | 3/4 | 3/3 | 5/5 | 3/3 |
| License | – | Apache-2.0 | – | Apache-2.0 | MIT | Apache-2.0 |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
https://mcp.obligationsign.com/mcp
| Transport | URL | Status |
|---|---|---|
| Streamable HTTP (primary) | https://mcp.obligationsign.com/mcp | Active |
| SSE (deprecated) | https://mcp.obligationsign.com/mcp/sse | Deprecated |
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/.
Add to your MCP configuration:
{
"mcpServers": { "agts": { "url": "https://mcp.obligationsign.com/mcp", "headers": { "Authorization": "Bearer YOUR_TOKEN" } } } }
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": {} }'
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.
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 | Description |
|---|---|
create_tunnel | Establish an attested VPN tunnel (WireGuard/IPSec/TLS) |
tunnel_status | Monitor uptime, transfer bytes, and attestation status |
disconnect_tunnel | Terminate session and log the event |
dns_query | Secure DNS resolution through the Sovereign resolver |
| Tool | Description |
|---|---|
system_health | Probe all mesh workers for status and latency |
check_alerts | Fetch the monitor alert timeline |
subscribe_alerts | Webhook subscription for real-time alerts |
check_equivocations | Fetch conflicting Signed Tree Head proofs |
gossip_status | Current state of gossip protocol and monitor identity |
| Tool | Description |
|---|---|
send_sovereign_mail | Send encrypted (internal) or plaintext (external) messages |
list_inbox | List message metadata from an inbox |
read_message | Retrieve full message content by ID |
lookup_recipient_keys | Retrieve public keys (ECDH P-384 / ML-KEM-512) |
| Tool | Description |
|---|---|
upload_file | Client-side encrypted upload with integrity anchoring |
list_files | List file metadata, sizes, and sharing status |
download_file | Retrieve ciphertext for client-side decryption |
share_file | Share files using ECDH key wrapping |
delete_file | Remove a file and create a death leaf in the log |
| Tool | Description |
|---|---|
register_claw | Create a cryptographic Claw Passport and identity keys |
scan_skill | Scan agent skills through the five-gate firewall |
claw_status | Return trust score, governance history, and quota |
export_passport | Secure export of the identity envelope |
govern_skill_exec | High-level gate for skill execution |
report_skill_execution | Link skill results to authorization |
verify_skill_proof | Cryptographic verification of skill scans |
| Tool | Description |
|---|---|
authenticate_peer | Hybrid PQC (ML-DSA-44) + Classical (ECDSA) auth ceremony |
verify_agent_identity | Fingerprint and revocation check via key registry |
exchange_credentials | Secure transport using hybrid ECDH + ML-KEM-512 |
peer_trust_network | List known peers and mutual trust status |
| Tool | Description |
|---|---|
submit_governance | Pre-execution gate evaluation (ADMIT/QUARANTINE/REFUSE) |
verify_commitment | Verify commitment in transparency log with Merkle proofs |
report_execution | Log outcome of an authorized action |
update_policy | Update firewall parameters |
list_policies | List active governance thresholds and history |
governance_report | Aggregated decision reporting |
governance_stats | Per-gate pass/fail statistics and HCE distribution |
gate_analysis | Detailed breakdown of a specific evaluation decision |
| Tool | Description |
|---|---|
memory_store | Store hierarchical key-value entries |
memory_recall | Retrieve specific entries by path |
memory_list | Prefix-based listing of memories |
memory_search | Semantic similarity search using vector embeddings |
cross_session_recall | Semantic search across historical sessions |
memory_context | Mode-based contextual summary |
consolidate_memory | Compare and compact redundant entries |
memory_gc | Garbage collection of stale entries |
set_memory_ttl | Configure automatic expiration for entries |
memory_delete | Remove specific memory paths |
| Tool | Description |
|---|---|
provision_resource | Create a billing project for an agent |
manage_spending | Freeze/unfreeze spending |
check_project_billing | Detailed usage and charge breakdown |
verify_provision | Check billing project linkage |
set_budget_alert | Configure spending thresholds |
check_budget | Real-time spend vs. cap tracking |
| Tool | Description |
|---|---|
spawn_sub_agent | Launch an isolated asynchronous sub-agent |
sub_agent_status | Poll sub-agent execution status |
sub_agent_result | Retrieve sub-agent results |
chain_delegation | Recursive delegation with budget decay and depth limits |
create_template | Define a reusable multi-step workflow |
apply_template | Instantiate a template into a running task |
list_sub_agents | List active sub-agents |
list_templates | List available workflow templates |
cancel_sub_agent | Terminate a running sub-agent |
merge_sub_results | Aggregate results from parallel sub-agents |
delegation_tree | Reconstruct the full lineage of a delegated chain |
In addition to MCP, the gateway exposes REST endpoints:
| Endpoint | Description |
|---|---|
GET /api/v1/health | Upstream service health checks |
GET /api/v1/audit | Audit log queries |
GET /api/v1/assets | Asset management |
GET /verify?commitment={hash} | Commitment verification with Merkle proof |
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)
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:
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).
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.
| Requirement | AGTS Implementation |
|---|---|
| Art. 9 — Risk management | Five-gate firewall evaluates every action before execution; QUARANTINE decisions enable human intervention |
| Art. 12 — Record-keeping | Append-only Merkle transparency log with signed governance envelopes; automatic recording of every authorization and execution event |
| Art. 13 — Transparency | Every commitment is independently verifiable with cryptographic inclusion proofs; governance decisions are explainable via the HCE (Human-Compatible Explanation) gate |
| Art. 14 — Human oversight | Gate thresholds are configurable; QUARANTINE/REFUSE decisions halt execution; policy updates are themselves governed and logged |
| Trust Principle | AGTS Implementation |
|---|---|
| Security | Hybrid Ed25519 + SLH-DSA signing; post-quantum key exchange (ML-KEM-512); Cloudflare Access authentication with email binding; per-tool rate limiting |
| Availability | Multi-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