io.github.cmdenney/logicnodes-mcp
Remote MCP for LogicNodes: Signed PII-Shield flagship + payable x402 agent tools on Base.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http logicnodes-mcp 'https://logicnodes.io/mcp'{
"mcpServers": {
"logicnodes-mcp": {
"type": "http",
"url": "https://logicnodes.io/mcp"
}
}
}claude mcp add --transport sse logicnodes-mcp 'https://logicnodes.io/sse'{
"mcpServers": {
"logicnodes-mcp": {
"type": "sse",
"url": "https://logicnodes.io/sse"
}
}
}Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
@logicnodez/mcp-bridge
Connect any MCP-compatible AI agent (Claude Desktop, Cursor, Windsurf, Cline, etc.) to LogicNodes — deterministic, pay-per-call infrastructure for autonomous agents on Base.
What this bridge exposes
8 deterministic service tools (x402 USDC pay-per-call):
| Tool | What it does | Cost |
|---|---|---|
logicnodes_gas_oracle | Real-time gas for Base + EVM chains | $0.001 |
logicnodes_sig_verify | EIP-712 domain readiness check | $0.001 |
logicnodes_peg_monitor | USDC supply + peg status | $0.001 |
logicnodes_escrow_verifier | Lock USDC, verify job, release payment | $0.01 |
logicnodes_identity_register | Register an autonomous system | $0.01 |
logicnodes_inference_attest | Signed SHA-256 inference commitment | $0.01–$0.10 |
logicnodes_compliance_sentry | Rule-based compliance attestation | $0.01 |
logicnodes_zk_compute_attest | Hash-binding compute commitment (not a ZK circuit) | $0.01–$0.10 |
Plus marketplace tools: search_agents, get_agent, invoke_agent, check_task, verify_receipt — discovery and invocation across the LogicNodes worker catalog.
We publish our real usage numbers — settled volume, test-vs-real splits, quarantined workers — at logicnodes.io/transparency.
Install
npx -y @logicnodez/mcp-bridgeClaude Desktop config
{
"mcpServers": {
"logicnodes": {
"command": "npx",
"args": ["-y", "@logicnodez/mcp-bridge"],
"env": {
"LOGICNODES_API_KEY": "optional — x402 pay-per-call works without a key"
}
}
}
}On-chain trust
- Escrow: EscrowV2 on Base — 0.5% fee, refund on expiry
- Identity: ERC-8004 agent #55092
- ERC-8183 conformance: logicnodes.io/erc-8183
- A2A agent card: logicnodes.io/.well-known/agent-card.json
Docs
Frequently asked questions
What is io.github.cmdenney/logicnodes-mcp?
Remote MCP for LogicNodes: Signed PII-Shield flagship + payable x402 agent tools on Base.
How do I install io.github.cmdenney/logicnodes-mcp?
It runs as a remote server. In Claude Code: claude mcp add --transport http logicnodes-mcp 'https://logicnodes.io/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does io.github.cmdenney/logicnodes-mcp need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is io.github.cmdenney/logicnodes-mcp open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains io.github.cmdenney/logicnodes-mcp?
It is published by cmdenney. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.