CodexImmortal MCP server
io.github.calebfbyker-lab/codeximmortalcalebfbyker-labstreamable-httpv1.1.0Scanned
CodexImmortal product catalog and governed purchase proposals over MCP.
6 tools: 1 do something that can't be undone, 3 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 3 findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the CodexImmortal MCP server can do
The CodexImmortal MCP server is published by the GitHub account calebfbyker-lab. It has 6 tools. It can do things that cannot be undone, such as sending, paying or publishing (codex_purchase_initiate) and create or change data (3 tools: codex_quote_request, codex_attestation_verify and codex_scan_request), but cannot delete data. 2 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 3 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 21, 2026, version 1.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Can't be undone 1Claude Code: ask
codex_purchase_initiatePrepare a purchase proposal for a catalog item.1 finding
Why it is in this group
- The name "codex_purchase_initiate" says "purchase": a word that usually means money moves, which cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "codex_purchase_initiate" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "codex_purchase_initiate" says "purchase": a word that usually means money moves, which cannot be taken back.
Description, as the server wrote it Prepare a purchase proposal for a catalog item. Returns an AP2/x402 checkout payload draft for human approval. This tool never executes a payment, charges a card, or moves funds — execution happens only through the isolated financial connector gateway after a valid, exact-match, single-use TGA is issued.
Annotations the server declares
- readOnlyHint: true
Changes things 3Claude Code: ask
codex_attestation_verifyVerify a Codex Immortal attestation record: content hash, signature, timestamp, and ledger inclusion proof.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Verify a Codex Immortal attestation record: content hash, signature, timestamp, and ledger inclusion proof.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
codex_quote_requestRequest a quote for volume, enterprise, or custom-scope engagements.1 finding
Why it is in this group
- The name "codex_quote_request" says "request": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "codex_quote_request" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "codex_quote_request" says "request": a word for a change.
Description, as the server wrote it Request a quote for volume, enterprise, or custom-scope engagements. Returns an RFQ reference and expected response time.
Annotations the server declares
- readOnlyHint: true
codex_scan_requestRequest an autonomous threat-hunt scan (supply-chain, insider-threat, HNDL triage).1 finding
Why it is in this group
- The name "codex_scan_request" says "request": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "codex_scan_request" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false}; The name "codex_scan_request" says "request": a word for a change.
Description, as the server wrote it Request an autonomous threat-hunt scan (supply-chain, insider-threat, HNDL triage). Defensive and read-only by design. Live-scope scans route to human gate before execution.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
Only reads 2Show 2 read-only tools
codex_catalog_get_productGet the full ERC-8004-shaped service offer for one product: capabilities, pricing, SLA, refund/dispute terms, evidence and validation status.No findings
Why it is in this group
- The name "codex_catalog_get_product" says "get": a word for reading.
Description, as the server wrote it Get the full ERC-8004-shaped service offer for one product: capabilities, pricing, SLA, refund/dispute terms, evidence and validation status.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
codex_catalog_listList Codex Immortal products and services with pricing basis, capabilities, denied capabilities, and validation status.No findings
Why it is in this group
- The name "codex_catalog_list" says "list": a word for reading.
Description, as the server wrote it List Codex Immortal products and services with pricing basis, capabilities, denied capabilities, and validation status.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 15, 2026, 13:20 UTC, unchanged since Nov 8, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 4
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (1 irreversible, 3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://codeximmortal-mcp.onrender.com/mcp: tools/list returned 6 tools to an anonymous client, including codex_purchase_initiate (irreversible), codex_quote_request (write), codex_attestation_verify (write), codex_scan_request (write)
Findings
Matches of fixed checks, with the text they matched.
The server marks "codex_quote_request" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "codex_quote_request" says "request": a word for a change.
The server marks "codex_scan_request" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false}; The name "codex_scan_request" says "request": a word for a change.
The server marks "codex_purchase_initiate" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "codex_purchase_initiate" says "purchase": a word that usually means money moves, which cannot be taken back.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http codeximmortal https://codeximmortal-mcp.onrender.com/mcpclaude mcp add --transport http codeximmortal https://codeximmortal-mcp.onrender.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__codeximmortal__codex_catalog_list",
"mcp__codeximmortal__codex_catalog_get_product"
],
"ask": [
"mcp__codeximmortal__codex_quote_request",
"mcp__codeximmortal__codex_attestation_verify",
"mcp__codeximmortal__codex_scan_request",
"mcp__codeximmortal__codex_purchase_initiate"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as codeximmortal. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.calebfbyker-lab/codeximmortal/verify?hash=f188ba62af95d6db0f90fcecc84135a102d9d3feb3d8ca606b68a35570c5cc55" | jq -e '.changed == false'Pinned hash f188ba62af95, from Nov 21, 2026, 20:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.calebfbyker-lab/codeximmortal/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.calebfbyker-lab/codeximmortal)Source: MCP Registry · repository. Synced Nov 7, 2026, 15:17 UTC.
CodexImmortal MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the CodexImmortal MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 4 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the CodexImmortal MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the CodexImmortal MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: codex_purchase_initiate.
What tools does the CodexImmortal MCP server have?
- 6 tools: 1 irreversible, 3 write, 2 read. codex_purchase_initiate, codex_quote_request, codex_attestation_verify, codex_scan_request, codex_catalog_list and codex_catalog_get_product.
Does the CodexImmortal MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the CodexImmortal MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the CodexImmortal MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.