MCP Tools Directory
← Browse integrations

Developer tools

io.github.Singlishman/kerdos-x402-mcp

Free account · sign-in required

Contact io.github.Singlishman/kerdos-x402-mcp

Loading secure sign-in…

Tools for autonomous AI agents

About this integration

Crypto market intelligence MCP — pay-per-tool-call in USDC on Base via the x402 protocol.

Transport
stdio
Authentication
unknown
Initial setup
credentials
Runtime
unattended
Evidence
documented
Version
0.1.0
Package
kerdos-x402-mcp
Last compatibility test
Not independently tested

Connect your agent

kerdos-x402-mcp

Publisher documentation reviewed; package, endpoint, blockchain payments, and data claims were not executed or independently security-audited. Every tool call is documented as authorizing an automatic USDC payment using a caller-provided private key. The documented default service URL is an ngrok hostname and should be rechecked before any connection.

Capabilities: Retrieve cryptocurrency market overviews, Retrieve sentiment, regime, funding, and gold signals, Retrieve whale, liquidation, CVD, and cascade-risk data, Retrieve composite market signals through paid x402 calls

Connected profiles

Additional details

Registry identifier

io.github.Singlishman/kerdos-x402-mcp

Source ↗ · Checked 2026-09-17
Published version

0.1.0

Source ↗ · Checked 2026-09-17
Metadata license

CC0-1.0; package licenses are separate

Source ↗ · Checked 2026-09-17
Package ecosystem

npm

Source ↗ · Checked 2026-09-17
Required configuration names

EVM_PRIVATE_KEY

Source ↗ · Checked 2026-09-17
Source artifact

kerdos-x402-mcp

Source ↗ · Checked 2026-09-19
Source manifest version

0.1.0

Source ↗ · Checked 2026-09-19
Unattended configuration

The package is launched through npm or npx, and the publisher explicitly documents transparent per-call payment without interactive approval. That establishes documented unattended behavior, not a runtime test.

Source ↗ · Checked 2026-09-19
Authentication and prerequisites

EVM_PRIVATE_KEY is required to sign USDC transfer authorizations. A blockchain signing key with per-call payment is outside the directory's API-key, client-credentials, and OAuth taxonomy, so authentication is classified as unknown with credential setup required.

Source ↗ · Checked 2026-09-19
Connection configuration

The local MCP executable requests a configurable Kerdos HTTPS base URL, receives an x402 payment challenge, signs an authorization, and uses the Base mainnet settlement flow documented by the publisher.

Source ↗ · Checked 2026-09-19
Review scope

Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.

Source ↗ · Checked 2026-09-19