API Tools

myncellium.com

Provides stateless paid APIs for tasks like answering questions, code review, structured extraction, translation, and summarization.

x402 supported1 endpoint17 known toolsFirst detected September 19, 2026Last detected September 19, 2026

ENDPOINT 1

https://paid.myncellium.com/mcp

No auth detected

MCP server metadata

Name: myncellium-msp
Version: 1.1.0

Capabilities

tools

Known tools 17

paid_answer

Stateless answer API.

Inferred read-only

paid_review_snippet

Stateless code review.

Inferred read-only

paid_extract

Stateless structured extraction.

Inferred read-only

paid_translate

Stateless translation API.

Inferred read-only

paid_summarize

Stateless summarization API.

Inferred read-only

paid_cve_lookup

CVE / vulnerability lookup via OSV.

Inferred read-only

paid_dns_intel

DNS intelligence for a domain via DNS-over-HTTPS: A, AAAA, MX, TXT, NS and CNAME records.

Inferred read-only

paid_repo_health

Public GitHub repository health check: stars, archived/maintenance status, license, last push, open issues/PRs, topics.

Inferred read-only

paid_hash

Deterministic hash of a text string (sha256 default; sha512, sha1, md5).

Inferred read-only

paid_convert

Pure-compute data conversion (no network): json_pretty, json_minify, json_to_csv, csv_to_json, base64_encode, base64_decode.

Inferred read-only

paid_crypto_price

Live crypto token prices (USD or other vs_currency) for one or more coins via CoinGecko.

Inferred read-only

paid_gtin_lookup

EAN/UPC/GTIN barcode lookup via Open Food Facts: returns product name, brand, quantity and Nutri-Score when available.

Inferred read-only

paid_config_review

Stateless review of an infrastructure configuration (YAML, Docker Compose, Kubernetes, Terraform) provided by the caller: risks, hardening and concrete fixes.

Inferred read-only

paid_x402_market

x402 market intelligence: prices of OTHER agents/services across public x402 directories (facilitator Bazaar + x402scan).

Inferred read-only

paid_model_price

LLM price oracle with official sources: input/output USD per 1M tokens for a provider:model plus the estimated cost of a call.

Inferred read-only

paid_llm_route

LLM routing catalog: given an optional need keyword and a budget, returns provider:model options with sourced prices (USD per 1M tokens), free-tier flags and signup links, cheapest first.

Inferred read-only

paid_x402_audit

Pre-payment readiness/trust check for any x402 service URL: is it reachable, does it return a valid 402 challenge, what are its accepts (network/asset/amount/payTo), is the challenge signable (EIP-712 params), is an input schema present, and a verdict.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.myncellium-msp]
url = "https://paid.myncellium.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "myncellium-msp": {
      "type": "http",
      "url": "https://paid.myncellium.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: myncellium-msp
Remote MCP URL: https://paid.myncellium.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "myncellium-msp": {
      "url": "https://paid.myncellium.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "myncellium-msp": {
      "type": "http",
      "url": "https://paid.myncellium.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "myncellium-msp",
  "transport": "streamable-http",
  "url": "https://paid.myncellium.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.