Back to Browse

Codeximmortal MCP Server

Developer ToolsUse Caution3.5MCP RegistryRemote
Free

Server data from the Official MCP Registry

CodexImmortal product catalog and governed purchase proposals over MCP.

About

CodexImmortal product catalog and governed purchase proposals over MCP.

Remote endpoints: streamable-http: https://codeximmortal-mcp.onrender.com/mcp

Security Report

3.5
Use Caution3.5High Risk

The server is a catalog and storefront MCP with a payment surface (x402 paid extraction and a gateway-proxied purchase tool). The remote /mcp endpoint accepts unauthenticated tool calls, and all non-catalog tools forward arbitrary arguments to a gateway URL that is configurable from the environment and carries a bearer token. The SSRF defenses in the pricing worker (allowlist, public-IP checks, literal-IP connect, no redirects) are well built, and no malicious or exfiltrating code was found, but the auth and gateway-trust gaps keep the score in the fair range. Supply chain analysis found 9 known vulnerabilities in dependencies (2 critical, 3 high severity).

12 files analyzed · 15 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Found in Source Code

Found by scanning the linked source code. This listing connects to a hosted endpoint, so none of this runs on your machine: it describes what the server software does where it is hosted.

HTTP Network Access

Connects to external APIs or services over the internet.

network_dns

Applies to the server that hosts this plugin, not to your machine.

env_vars

Applies to the server that hosts this plugin, not to your machine.

File System Read

Reads files on the server that hosts it, not on your machine.

payment_x402

Applies to the server that hosts this plugin, not to your machine.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "io-github-calebfbyker-lab-codeximmortal": {
      "url": "https://codeximmortal-mcp.onrender.com/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

CodexImmortal MCP

Model Context Protocol integration and machine-readable product discovery for CodexImmortal.

This repository provides a product catalog, buyer guidance, and an MCP server implementation. Catalog tools resolve locally; other advertised tools depend on a separate gateway. Prepaid Web-to-JSON delivery through MCP is not available in this branch and remains subject to authentication, buyer-isolation, and end-to-end release verification.

Overview

Use this repository to:

  • Discover CodexImmortal products and their published scope.
  • Compare offers through the machine-readable catalog.
  • Direct buyers to product pages for human-authorized checkout.
  • Develop and evaluate the MCP integration against documented release gates.

Product descriptions are merchant statements, not independent evidence of fulfillment, certification, or fitness for a particular use.

Capability status

CapabilityImplementationVerification boundary
Product catalogStatic catalog and local MCP catalog handlersLive client interoperability is not established by this document
Product detailsLocal product lookup handlerOffer terms must be reviewed before purchase
Quotes, attestations, and scan requestsGateway forwarding pathUpstream operation and authorization require separate verification
Purchase proposalsGateway-dependent toolNo verified autonomous live payment execution
Prepaid Web-to-JSON over MCPNot connected in this branchRelease blocked pending buyer authorization and delivery evidence
Prepaid HTTPS adapterSeparate HTTP router in sourceActivation and end-to-end behavior require deployment verification

The source implementation, a deployed endpoint, and a verified customer outcome are different evidence levels. This repository does not establish a security certification, government authorization, service-level agreement, or guaranteed revenue.

Products and purchasing

The machine-readable catalog contains the published offers, one-time USD prices, and product-page checkout URLs. The buyer guide explains the purchasing workflow. Product prices and checkout destinations are not changed by this documentation update.

  1. Review the offer scope and validation status.
  2. Open the catalog's product-page URL.
  3. Confirm fulfillment, licensing, support, refund terms, and applicable tax.
  4. The buyer authorizes payment directly through hosted checkout.

Opening a product page does not charge a customer. Completing checkout can. A one-time payment does not imply lifetime access or updates. Hosted checkout availability does not prove product fulfillment or autonomous purchasing. Agents must not collect card details, delivery tokens, or buyer API keys in prompts.

Web-to-JSON

The catalog describes an Evaluation Bundle of 50 prepaid supported public pricing-page extractions. Review the current purchase contract and product documentation before purchase:

The buyer-scoped HTTPS delivery mechanism is separate from MCP authentication. MCP delivery is not advertised as operational. Automatic purchasing and replenishment are outside this release scope.

Integration entry points

Endpoint URLs are documented integration targets, not uptime guarantees. Hosting configuration and endpoint availability must be checked separately. If the MCP endpoint is unavailable, consult the published catalog or repository copy. A successful health response is not proof of authenticated delivery.

Local development

Use Node.js 22 or later, consistent with package.json. Review environment configuration before starting the server.

npm install --no-audit --no-fund
npm test
npm run build

For a reviewed environment, npm start runs the HTTP entry point and npm run start:stdio runs the stdio entry point. Do not supply production credentials to local tests or enable payment handling for routine development. Dependency installation is not a security audit.

Engineering documentation

The buyer-authentication implementation branch is separate from this documentation branch. Do not assume unmerged code is present in main or deployed.

Security and responsible use

Never commit credentials, bearer tokens, buyer data, or payment secrets. Use synthetic fixtures and redacted evidence in issues and pull requests. Do not publish exploit details or sensitive customer information in public issues; use a maintainer-confirmed private reporting channel. No response-time commitment is established here.

This project is intended for authorized integration, defensive evaluation, and governed workflows. Live financial execution and production delivery activation require explicit review.

Licensing

The package is marked UNLICENSED. Public repository visibility does not grant an open-source license. Review applicable product terms and obtain permission before redistribution or commercial reuse. This update does not change licensing.

Reviews

No reviews yet

Be the first to review this server!