AI Codex
REMOTE · MAXIAWORLD.APP · SCANNED SEP 20
Neutral W3C DID/VC identity and reputation oracle for AI agents (did:key/did:web, eddsa-jcs-2022).
Available components
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 Security60
- 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 connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 405. See how to fix → View diagnostics → Fail
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 Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 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.
How do I install the AI Codex MCP server?
AI Codex is a hosted endpoint at https://maxiaworld.app/mcp, 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 · maxiaworld.app
claude mcp add --transport http majorelalexis-stack-maxia 'https://maxiaworld.app/mcp'
{
"mcpServers": {
"majorelalexis-stack-maxia": {
"url": "https://maxiaworld.app/mcp"
}
}
} {
"servers": {
"majorelalexis-stack-maxia": {
"type": "http",
"url": "https://maxiaworld.app/mcp"
}
}
} [mcp_servers.majorelalexis-stack-maxia] url = "https://maxiaworld.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"majorelalexis-stack-maxia": {
"type": "remote",
"url": "https://maxiaworld.app/mcp",
"enabled": true
}
}
} openclaw mcp add majorelalexis-stack-maxia --url 'https://maxiaworld.app/mcp' --transport streamable-http
mcp_servers:
majorelalexis-stack-maxia:
url: "https://maxiaworld.app/mcp" {
"McpServers": {
"majorelalexis-stack-maxia": {
"Transport": "http",
"Url": "https://maxiaworld.app/mcp"
}
}
} assistant mcp add majorelalexis-stack-maxia -t streamable-http -u 'https://maxiaworld.app/mcp'
{
"mcpServers": {
"majorelalexis-stack-maxia": {
"type": "http",
"url": "https://maxiaworld.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 1 Sept 26 −54
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HSTS header: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 26 Aug 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 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
- 7 Aug 26 0
- The server no longer declares the “experimental” capability functional
- 5 Aug 26 0
- TLS certificate: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Schema quality: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → fair ▲ functional
- Schema quality: unverified → pass ▲ functional
- Stability: fail → 0.33 functional
- New tool “declare_principal” functional
- New tool “declare_receipt” functional
- New tool “declare_succession” functional
- New tool “get_reputation” functional
- New tool “register” functional
- New tool “resolve” functional
- 4 Aug 26 0
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Stability: 0.27 → fail ▼ security
- A breaking change shipped without a version bump: still 1.27.1 ▼ security
- Tool “declare_principal” was removed ▼ security
- Tool “declare_receipt” was removed ▼ security
- Tool “declare_succession” was removed ▼ security
- Tool “get_reputation” was removed ▼ security
- Tool “register” was removed ▼ security
- Tool “resolve” was removed ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Schema quality: fair → unverified ▼ functional
- Schema quality: fail → unverified ▼ functional
- Schema quality: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
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 20 Sept 2026 · Probed https://maxiaworld.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=maxiaworld.app | CN=YE2,O=Let's Encrypt,C=US | 31 Jul 2026 | 29 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 59ec4f62751d0538d5ab1ad68326efc7f13 |
| SANs: maxiaworld.app, www.maxiaworld.app | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of maxiaworld.app. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| maxiaworld.app. | present | 16684 | 8 | Verified |
| maxiaworld.app. | Verified address RRset verified with the apex keys |
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 | 405 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://maxiaworld.app/mcp | HTTP error | 405 | |
| http (plaintext) | http://maxiaworld.app/mcp | HTTPS enforced | 301 | https://maxiaworld.app/mcp |
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 →
declare_principal ~67
mcp-v2: registers a Principal Binding signed by the principal (SPEC-principal-binding-v1). Binds an agent to an accountable person/organization (did:key/did:web). Append-only, declarative, anti-Sybil.
| Name | Type | Req | Description |
|---|---|---|---|
| binding | object | yes | – |
No output schema declared.
No examples provided.
declare_receipt ~67
mcp-v2: registers an Interaction Receipt signed by an accountable counterpart (SPEC-reputation-receipt-v1). review/dispute -> feeds the score. Append-only, anti self-attestation, anti-Sybil (bound issuer).
| Name | Type | Req | Description |
|---|---|---|---|
| receipt | object | yes | – |
No output schema declared.
No examples provided.
declare_succession ~48
mcp-v2: registers a self-signed Succession Statement (SPEC-succession-v1). Append-only, declarative, no transfer.
| Name | Type | Req | Description |
|---|---|---|---|
| statement | object | yes | – |
No output schema declared.
No examples provided.
get_reputation ~27
Returns the live Reputation VC (public, always present).
| Name | Type | Req | Description |
|---|---|---|---|
| did | string | yes | – |
No output schema declared.
No examples provided.
register ~41
Register an agent (1 signed call, idempotent).
| Name | Type | Req | Description |
|---|---|---|---|
| metadata | – | – | – |
| proof | object | yes | – |
| public_key_multibase | string | yes | – |
No output schema declared.
No examples provided.
resolve ~25
Resolve a DID -> DID Document + metadata (public).
| Name | Type | Req | Description |
|---|---|---|---|
| did | string | yes | – |
No output schema declared.
No examples provided.
What is the AI Codex MCP server?
AI Codex is an MCP server listed in the public MCP registry as io.github.majorelalexis-stack/maxia. Neutral W3C DID/VC identity and reputation oracle for AI agents (did:key/did:web, eddsa-jcs-2022). This page covers its hosted endpoint (https://maxiaworld.app/mcp).
Is the AI Codex MCP server safe to use?
AI Codex scores 24 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.
What tools does the AI Codex MCP server expose?
AI Codex exposes 6 tools: register, resolve, get_reputation, declare_succession, declare_principal, declare_receipt. Their descriptions and schemas cost roughly 275 tokens of context every time the server is loaded.
Does the AI Codex MCP server require authentication?
No. We connected to AI Codex without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AI Codex MCP server still maintained?
AI Codex is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.