mcp-registry/io.github.atomadictech/aaaa-nexus · v0.5.1
As of 2026-10-24 17:15 UTC, the Atomadictech Aaaa Nexus MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Formally verified AI safety APIs. Pay-per-call via USDC (x402). 75+ endpoints, no signup.
Claude Code
claude mcp add --transport http atomadictech-aaaa-nexus-mcp-server https://aaaa-nexus.atomadictech.workers.dev/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"atomadictech-aaaa-nexus-mcp-server": {
"type": "http",
"url": "https://aaaa-nexus.atomadictech.workers.dev/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
44 of 44 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
44 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.atomadictech%2Faaaa-nexus/fixes
{
"name": "aegis_mcp_proxy_execute",
"description": "NEXUS AEGIS MCP-Sentinel gateway for prompt-injection resistant tool execution",
"inputSchema": {
"type": "object",
"properties": {
"body": {
"type": "object",
"description": "For POST tools: JSON body per the matching path in /openapi.json."
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "keys_validate",
"description": "Validate X-API-Key entitlement tier (paid/extended/master) before gated tool calls.",
"inputSchema": {
"type": "object",
"properties": {
"body": {
"type": "object",
"description": "For POST tools: JSON body per the matching path in /openapi.json."
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "lint_analyze",
"description": "Synthesize lint findings from supplied local analysis artifacts.",
"inputSchema": {
"type": "object",
"properties": {
"body": {
"type": "object",
"description": "For POST tools: JSON body per the matching path in /openapi.json."
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.atomadictech/aaaa-nexus"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.atomadictech/aaaa-nexus"}) over MCP.
vanguard_escrow_lock_and_verify ~82 tokensaegis_router_epistemic_bound ~81 tokensauthorize_action ~81 tokensomega_intent_route ~81 tokensvanguard_continuous_redteam ~81 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.atomadictech%2Faaaa-nexus?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.atomadictech%2Faaaa-nexus?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.atomadictech%2Faaaa-nexus.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.atomadictech%2Faaaa-nexus.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.atomadictech%2Faaaa-nexus?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:9f4c3d1e49582853…, first seen 2026-10-17, included at leaf 10669 of 60,099. Version history · verify what your client received.
Compare: most reliable security servers · most reliable knowledge servers · most reliable code servers · most reliable ml servers · most reliable retrieval servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-24 17:15 UTC, the Atomadictech Aaaa Nexus MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Atomadictech Aaaa Nexus MCP server advertises 44 tools, including aegis_mcp_proxy_execute, aegis_router_epistemic_bound, agents_plan, authorize_action, certify_codebase.
Point your MCP client at this streamable-http endpoint: https://aaaa-nexus.atomadictech.workers.dev/mcp
Glimind scanned all 44 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.