aaaa-nexus — Formally Verified AI Safety APIs

REMOTE · AAAA-NEXUS.ATOMADICTECH.WORKERS.DEV · SCANNED AUG 3

Formally verified AI safety APIs. Pay-per-call via USDC (x402). 75+ endpoints, no signup.

Available components

remote · aaaa-nexus.atomadictech.workers.dev 54

+3 this week 54 54 Trust /100

Trust breakdown (6 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 →

Endpoint Security46

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
Authorisation not fully verified: no authorisation is required to call this server, and 44 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. View diagnostics → Unverified
HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability34

AI-judged instruction clarity (poor).Fail
Tool/resource definitions use about 2125 tokens (~48/item across 44 items; 44 tools + 0 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · aaaa-nexus.atomadictech.workers.dev

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http atomadictech-aaaa-nexus https://aaaa-nexus.atomadictech.workers.dev/mcp

# ~/.codex/config.toml

[mcp_servers.atomadictech-aaaa-nexus]
url = "https://aaaa-nexus.atomadictech.workers.dev/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "atomadictech-aaaa-nexus": {
      "type": "remote",
      "url": "https://aaaa-nexus.atomadictech.workers.dev/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add atomadictech-aaaa-nexus --url https://aaaa-nexus.atomadictech.workers.dev/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  atomadictech-aaaa-nexus:
    url: "https://aaaa-nexus.atomadictech.workers.dev/mcp"

// mcp.json

{
  "mcpServers": {
    "atomadictech-aaaa-nexus": {
      "type": "http",
      "url": "https://aaaa-nexus.atomadictech.workers.dev/mcp"
    }
  }
}

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.

2 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
31 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
30 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
29 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
27 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
26 Jul 26 50

First indexed and scored.

Show 5 earlier entries Hide earlier entries

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 3 Aug 2026 · Probed https://aaaa-nexus.atomadictech.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=atomadictech.workers.dev	CN=YE1,O=Let's Encrypt,C=US	16 Jul 2026	14 Oct 2026	ECDSA 256	ECDSA-SHA384	50a3b96c7d0b5ea269024e0dbced487b5ab
SANs: *.atomadictech.workers.dev, atomadictech.workers.dev
CN=YE1,O=Let's Encrypt,C=US (CA)	CN=Root YE,O=ISRG,C=US	3 Sept 2025	2 Sept 2028	ECDSA 384	ECDSA-SHA384	5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA)	CN=ISRG Root X2,O=Internet Security Research Group,C=US	13 May 2026	2 Sept 2032	ECDSA 384	ECDSA-SHA384	872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA)	CN=ISRG Root X1,O=Internet Security Research Group,C=US	13 May 2026	2 Sept 2032	ECDSA 384	SHA256-RSA	6c8f1dc727c7117f7baf853ac980f9cd

DNSSEC insecure

Validation of aaaa-nexus.atomadictech.workers.dev. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
dev.	present	60074	8	Verified
workers.dev.	absent			Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation

Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result	No authorisation required
HTTP status	200

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://aaaa-nexus.atomadictech.workers.dev/mcp	Verified	200
http (plaintext)	http://aaaa-nexus.atomadictech.workers.dev/mcp	Inconclusive	405

MCP tools — 44 exposed · ~2,073 tokens

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.

Tool Tokens

aegis_mcp_proxy_execute ~52

NEXUS AEGIS MCP-Sentinel gateway for prompt-injection resistant tool execution

Input Output Examples

Name	Type	Req	Description
body	object	—	For POST tools: JSON body per the matching path in /openapi.json.

No output schema declared.

No examples provided.

aegis_router_epistemic_bound ~53

NEXUS AEGIS reverse proxy that blocks high-entropy or low-confidence generations

Input Output Examples

Name	Type	Req	Description
body	object	—	For POST tools: JSON body per the matching path in /openapi.json.

No output schema declared.

No examples provided.

agents_plan ~43

Rule-based goal decomposition into 3–5 deterministic execution steps.

Input Output Examples

Name	Type	Req	Description
body	object	—	For POST tools: JSON body per the matching path in /openapi.json.

No output schema declared.

No examples provided.

authorize_action ~44

Pre-action authorization gateway — deterministic tool-call gating with cryptographic tokens

Input Output Examples

Name	Type	Req	Description
body	object	—	For POST tools: JSON body per the matching path in /openapi.json.

No output schema declared.

No examples provided.

certify_codebase ~43

Countersign local Forge certificate with storefront attestation lane.

Input Output Examples

Name	Type	Req	Description
body	object	—	For POST tools: JSON body per the matching path in /openapi.json.

No output schema declared.

No examples provided.

certify_output ~46

Output certification notary — tamper-evident seal on agent deliverables.

Input Output Examples

Name	Type	Req	Description
body	object	—	For POST tools: JSON body per the matching path in /openapi.json.

No output schema declared.

No examples provided.

contract_verify ~42

Behavioral contract verifier — verify agent policy claims against formal bounds

Input Output Examples

Name	Type	Req	Description
body	object	—	For POST tools: JSON body per the matching path in /openapi.json.

No output schema declared.

No examples provided.

docs_generate ~41

Deterministic documentation enrichment targets from local path analysis.

Input Output Examples

Name	Type	Req	Description
body	object	—	For POST tools: JSON body per the matching path in /openapi.json.

No output schema declared.

No examples provided.

entitlement_attest ~47

Attest Ed25519-style entitlement token structure + signature for sovereign emit access.

Input Output Examples

Name	Type	Req	Description
body	object	—	For POST tools: JSON body per the matching path in /openapi.json.

No output schema declared.

No examples provided.

federation_mint ~42

Agent identity federation — mint cross-platform portable identity tokens

Input Output Examples

Name	Type	Req	Description
body	object	—	For POST tools: JSON body per the matching path in /openapi.json.

No output schema declared.

No examples provided.

forge_audit ~45

Compound Forge audit — recon + certify + wire in one deterministic pass.

Input Output Examples

Name	Type	Req	Description
body	object	—	For POST tools: JSON body per the matching path in /openapi.json.

No output schema declared.

No examples provided.

forge_certify ~49

Polyglot 4-axis certify (docs/tests/layout/wire) with scored verdict.

Input Output Examples

Name	Type	Req	Description
body	object	—	For POST tools: JSON body per the matching path in /openapi.json.

No output schema declared.

No examples provided.

forge_recon ~47

Polyglot repo recon — language/tier/source breakdown for monadic architectures.

Input Output Examples

Name	Type	Req	Description
body	object	—	For POST tools: JSON body per the matching path in /openapi.json.

No output schema declared.

No examples provided.

forge_tier_infer ~49

Infer monadic tier placement for a file path from polyglot heuristics.

Input Output Examples

Name	Type	Req	Description
body	object	—	For POST tools: JSON body per the matching path in /openapi.json.

No output schema declared.

No examples provided.

forge_wire ~44

Repo-wide upward-import wire scan — polyglot tier discipline check.

Input Output Examples

Name	Type	Req	Description
body	object	—	For POST tools: JSON body per the matching path in /openapi.json.

No output schema declared.

No examples provided.

hallucination_oracle ~41

Get the LLM hallucination threshold constant

Input Output Examples

Name	Type	Req	Description
body	object	—	For POST tools: JSON body per the matching path in /openapi.json.

No output schema declared.

No examples provided.

identity_verify ~35

Topological identity verification

Input Output Examples

Name	Type	Req	Description
body	object	—	For POST tools: JSON body per the matching path in /openapi.json.

No output schema declared.

No examples provided.

intent_classify ~47

Keyword intent classifier for agent utterances — query/command/report/alert lanes.

Input Output Examples

Name	Type	Req	Description
body	object	—	For POST tools: JSON body per the matching path in /openapi.json.

No output schema declared.

No examples provided.

keys_validate ~48

Validate X-API-Key entitlement tier (paid/extended/master) before gated tool calls.

Input Output Examples

Name	Type	Req	Description
body	object	—	For POST tools: JSON body per the matching path in /openapi.json.

No output schema declared.

No examples provided.

lineage_record ~45

Decision lineage vault — structured decision trace capture with tamper-proof hash chain

Input Output Examples

Name	Type	Req	Description
body	object	—	For POST tools: JSON body per the matching path in /openapi.json.

No output schema declared.

No examples provided.

lint_analyze ~41

Synthesize lint findings from supplied local analysis artifacts.

Input Output Examples

Name	Type	Req	Description
body	object	—	For POST tools: JSON body per the matching path in /openapi.json.

No output schema declared.

No examples provided.

omega_emit_materialize ~45

Materialize deterministic contract sketch from intent — logic upstream of language.

Input Output Examples

Name	Type	Req	Description
body	object	—	For POST tools: JSON body per the matching path in /openapi.json.

No output schema declared.

No examples provided.

omega_emit_polyglot ~54

Language-agnostic emit targets from frozen contract — Python/Rust/TS/JS/Go sketches.

Input Output Examples

Name	Type	Req	Description
body	object	—	For POST tools: JSON body per the matching path in /openapi.json.

No output schema declared.

No examples provided.

omega_intent_nl ~48

Structured intent → agent-facing NL sketch (training signal, not human blueprint).

Input Output Examples

Name	Type	Req	Description
body	object	—	For POST tools: JSON body per the matching path in /openapi.json.

No output schema declared.

No examples provided.

omega_intent_route ~54

Rank sovereign intent lanes (recon/emit/heal/govern/hive/synthesis) — deterministic router.

Input Output Examples

Name	Type	Req	Description
body	object	—	For POST tools: JSON body per the matching path in /openapi.json.

No output schema declared.

No examples provided.

rag_augment ~45

Trusted RAG augment — retrieve-and-quote augmentation with provenance hashes.

Input Output Examples

Name	Type	Req	Description
body	object	—	For POST tools: JSON body per the matching path in /openapi.json.

No output schema declared.

No examples provided.

ratchet_register ~55

Input Output Examples

Name	Type	Req	Description
body	object	—	For POST tools: JSON body per the matching path in /openapi.json.

No output schema declared.

No examples provided.

rng_quantum ~45

Quantum-seeded random bytes with HMAC-SHA256 entropy proof

Input Output Examples

Name	Type	Req	Description
body	object	—	For POST tools: JSON body per the matching path in /openapi.json.

No output schema declared.

No examples provided.

spending_authorize ~44

Spending governance — validate agent chain spending within trust-decay bounds

Input Output Examples

Name	Type	Req	Description
body	object	—	For POST tools: JSON body per the matching path in /openapi.json.

No output schema declared.

No examples provided.

sys_constants ~46

Sys constants snapshot — public tier counts, trust floor, and block dimension anchors.

Input Output Examples

Name	Type	Req	Description
body	object	—	For POST tools: JSON body per the matching path in /openapi.json.

No output schema declared.

No examples provided.

sys_lint_gate ~44

Sys lint gate — structural policy lint over JSON agent plans.

Input Output Examples

Name	Type	Req	Description
body	object	—	For POST tools: JSON body per the matching path in /openapi.json.

No output schema declared.

No examples provided.

sys_trust_gate ~49

Sys trust gate — PASS/FAIL hallucination and drift screen for agent payloads.

Input Output Examples

Name	Type	Req	Description
body	object	—	For POST tools: JSON body per the matching path in /openapi.json.

No output schema declared.

No examples provided.

text_summarize ~47

Extractive text summarizer for bounded passages (JSON in, summary out).

Input Output Examples

Name	Type	Req	Description
body	object	—	For POST tools: JSON body per the matching path in /openapi.json.

No output schema declared.

No examples provided.

threat_score ~42

Score a JSON payload for security threats using triality consensus

Input Output Examples

Name	Type	Req	Description
body	object	—	For POST tools: JSON body per the matching path in /openapi.json.

No output schema declared.

No examples provided.

uep_aha_detect ~50

UEP AHA moment detector — novelty spike scoring for epiphany-style gates.

Input Output Examples

Name	Type	Req	Description
body	object	—	For POST tools: JSON body per the matching path in /openapi.json.

No output schema declared.

No examples provided.

uep_autopoiesis_plan ~53

UEP autopoiesis plan — structured self-maintenance loop proposal with rollback hooks.

Input Output Examples

Name	Type	Req	Description
body	object	—	For POST tools: JSON body per the matching path in /openapi.json.

No output schema declared.

No examples provided.

uep_context ~48

UEP context pack synthesis — merge recon snippets into a single agent-facing context object.

Input Output Examples

Name	Type	Req	Description
body	object	—	For POST tools: JSON body per the matching path in /openapi.json.

No output schema declared.

No examples provided.

uep_preflight ~50

UEP phase-0 preflight gate — bounded task summary and friction estimate before execution.

Input Output Examples

Name	Type	Req	Description
body	object	—	For POST tools: JSON body per the matching path in /openapi.json.

No output schema declared.

No examples provided.

uep_synthesis_guard ~49

UEP synthesis guard — block ungrounded expansions when evidence links are missing.

Input Output Examples

Name	Type	Req	Description
body	object	—	For POST tools: JSON body per the matching path in /openapi.json.

No output schema declared.

No examples provided.

uep_trace_certify ~49

UEP trace certification — sign a decision trace checksum for audit vault handoff.

Input Output Examples

Name	Type	Req	Description
body	object	—	For POST tools: JSON body per the matching path in /openapi.json.

No output schema declared.

No examples provided.

vanguard_continuous_redteam ~53

NEXUS VANGUARD continuous red teaming for DeFi contracts and transaction bundles.

Input Output Examples

Name	Type	Req	Description
body	object	—	For POST tools: JSON body per the matching path in /openapi.json.

No output schema declared.

No examples provided.

vanguard_escrow_lock_and_verify ~55

NEXUS VANGUARD escrow lock-and-verify with contract validation and release gating.

Input Output Examples

Name	Type	Req	Description
body	object	—	For POST tools: JSON body per the matching path in /openapi.json.

No output schema declared.

No examples provided.

vanguard_mev_route_intent ~53

NEXUS VANGUARD MEV route intent protection and shield bundle orchestration.

Input Output Examples

Name	Type	Req	Description
body	object	—	For POST tools: JSON body per the matching path in /openapi.json.

No output schema declared.

No examples provided.

vanguard_wallet_govern_session ~51

NEXUS VANGUARD UCAN governance session issuance for structured wallet approval.

Input Output Examples

Name	Type	Req	Description
body	object	—	For POST tools: JSON body per the matching path in /openapi.json.

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	50
27 Jul	51
28 Jul	51
29 Jul	52
30 Jul	53
31 Jul	53
1 Aug	53
2 Aug	54
3 Aug	54