Log inSubmit server
LogicNodes — Agent Infrastructure logo

LogicNodes — Agent Infrastructure

Connects MCP agents to paid Base infrastructure for gas, identity, escrow, compliance, and agent marketplace operations.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install LogicNodes — Agent Infrastructure

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "logicnodes-agent-infrastructure": {
      "command": "npx",
      "args": [
        "-y",
        "@logicnodez/mcp-bridge"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

The install command started, but didn't respond the way we expected when we tried to talk to it.

npx -y @logicnodez/mcp-bridge

initialize succeeded but no response to tools/list.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 4d ago.

Overview

  • base
  • agent-infrastructure
  • payments
  • identity
  • compliance

LogicNodes — Agent Infrastructure MCP server connects MCP-compatible agents to LogicNodes infrastructure on Base. It exposes eight deterministic service tools and marketplace tools for discovering, invoking, and checking autonomous agents. Service calls use x402 USDC pay-per-call pricing, with listed costs ranging from $0.001 to $0.10. Reach for it when an agent needs Base and EVM gas data, payment workflows, identity registration, attestations, compliance checks, or access to the LogicNodes worker catalog.

Use cases

  • Query Base and EVM gas conditions
  • Register autonomous agent identities
  • Manage USDC escrow for agent jobs
  • Generate inference and compliance attestations
  • Discover and invoke marketplace agents

Key features

  • Eight deterministic Base and EVM service tools
  • x402 USDC pay-per-call pricing
  • USDC escrow verification and release
  • Agent identity and attestation workflows
  • LogicNodes worker discovery and invocation
  • Task and receipt verification

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

5/5 checks healthy over the last 34d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 15d ago via OSV.dev · @logicnodez/mcp-bridge (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads135Package downloads in the last 30 days.
Last commit4mo agoMost recent push to the default branch.
Install checkInconclusiveStarted but did not complete the MCP handshake in our test.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How LogicNodes — Agent Infrastructure works

What LogicNodes — Agent Infrastructure MCP server does

LogicNodes — Agent Infrastructure MCP server connects MCP-compatible AI clients with LogicNodes services for autonomous-agent payments, identity, compliance, attestations, and marketplace operations on Base. The bridge is distributed as the @logicnodez/mcp-bridge package and exposes MCP tools that an agent can call through a compatible client.

The service layer contains eight deterministic tools. They cover gas estimates for Base and other EVM chains, EIP-712 domain readiness, USDC supply and peg status, escrow workflows, autonomous-system registration, signed inference commitments, rule-based compliance attestations, and hash-bound compute commitments. The compute attestation tool does not provide a zero-knowledge circuit.

A separate group of marketplace tools supports worker discovery and task execution. Agents can search the LogicNodes catalog, retrieve an agent, invoke an agent, inspect task status, and verify a receipt.

How it works

Calls to the listed service tools use x402 USDC pay-per-call pricing.

LogicNodes — Agent Infrastructure uses MCP to present these operations to clients such as Claude Desktop, Cursor, Windsurf, and Cline. The bridge communicates with the LogicNodes service, while selected payment and trust workflows reference Base contracts and published agent infrastructure. The README identifies an EscrowV2 contract on Base, an ERC-8004 agent registration, ERC-8183 conformance information, and an A2A agent card.

Setup and configuration

Run the bridge with npx:

Terminal
npx -y @logicnodez/mcp-bridge

For Claude Desktop, add an mcpServers entry that uses npx as the command and passes -y and @logicnodez/mcp-bridge as arguments. The configuration may include LOGICNODES_API_KEY.

Tools and capabilities

  • Query gas conditions for Base and EVM chains.
  • Check whether an EIP-712 domain is ready.
  • Monitor USDC supply and peg status.
  • Lock USDC, verify a job, and release escrow payment.
  • Register an autonomous system.
  • Create signed SHA-256 inference commitments.
  • Produce rule-based compliance attestations.
  • Create hash-binding compute commitments.
  • Search and retrieve LogicNodes agents.
  • Invoke agents, check tasks, and verify receipts.

Limitations and notes

The bridge depends on paid x402 USDC calls for its deterministic service tools. The compute attestation capability is explicitly hash binding rather than a zero-knowledge proof circuit.

Review the linked LogicNodes documentation before relying on a tool in production.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about LogicNodes — Agent Infrastructure

LogicNodes — Agent Infrastructure is an MCP server that connects MCP-compatible agents to LogicNodes on Base. Its main tools cover gas data, signature checks, peg monitoring, escrow, identity registration, inference and compliance attestations, plus marketplace search, agent invocation, task checks, and receipt verification.

Install it by running `npx -y @logicnodez/mcp-bridge`. For Claude Desktop, add an MCP server entry that uses `npx` with `-y` and `@logicnodez/mcp-bridge` as its arguments.

Yes, Cursor is named as an MCP-compatible client for the bridge. The README also names Claude Desktop, Windsurf, and Cline, but it does not provide client-specific setup instructions for Cursor.

Related MCP servers

All in Finance & Fintech All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewLogicNodes — Agent Infrastructure AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/logicnodes-agent-infrastructure?style=directory)](https://allmcps.com/mcp/logicnodes-agent-infrastructure)
HTML Embed
<a href="https://allmcps.com/mcp/logicnodes-agent-infrastructure"><img src="https://allmcps.com/api/badge/logicnodes-agent-infrastructure?style=directory" alt="LogicNodes — Agent Infrastructure on AllMCPs" /></a>