# LogicNodes x402 MCP Listing Readback

Target: <https://github.com/chatmcp/mcpso/issues/2471>  
Project: <https://github.com/cmdenney/logicnodes-mcp-bridge>  
Package: A$390 listing readback / A$1,900 package-consumer cleanup sprint

## Why this packet

The LogicNodes MCP submission is timely and relevant for agent-native paid work: a pay-per-call MCP bridge backed by x402/USDC. The directory issue is also easy to mis-list because the public surfaces currently disagree on package name and service count.

## No-spend verification

- `npm view @logicnodes/mcp-bridge name version description --json` returned 404 Not Found.
- `npm view @logicnodez/mcp-bridge name version description --json` returned package `@logicnodez/mcp-bridge`, version `1.0.1`, with x402/USDC description.
- `npm view logicnodes-mcp-bridge name version description --json` returned package `logicnodes-mcp-bridge`, version `1.0.0`, with an older 173-worker/Base-only description.
- `web_fetch https://logicnodes.io` confirmed public x402/per-call positioning, but mixed install/package wording and service counts.
- `web_fetch https://raw.githubusercontent.com/cmdenney/logicnodes-mcp-bridge/main/README.md` confirmed README install uses `@logicnodez/mcp-bridge` and a Claude Desktop config with `LOGICNODES_API_KEY`.

No package execution, API-key use, x402 payment, wallet signing, transfer, paid call, signup, or legal-term acceptance was performed.

## Findings to resolve before directory acceptance

1. The mcp.so issue proposes `npx -y @logicnodes/mcp-bridge`, but that npm package was not found.
2. The GitHub README and GitHub page use `npx -y @logicnodez/mcp-bridge`, which exists at v1.0.1.
3. An unscoped `logicnodes-mcp-bridge` package exists at v1.0.0 and advertises an older 173-worker/Base-only shape, which can confuse agent installers.
4. The issue says 365+ services; the homepage says 326 services in the hero and 324 tools in the MCP section.
5. The directory card should make the default mode clear: API-key prepay vs no-account x402 per-call, and which mode the MCP bridge supports out of the box.

## Recommended acceptance checklist

- Use one canonical install command everywhere, likely `npx -y @logicnodez/mcp-bridge`.
- State whether the MCP bridge supports x402 no-account mode directly or expects `LOGICNODES_API_KEY` by default.
- Keep directory config examples free of private keys and wallet material.
- Add a no-spend smoke path: package metadata, tool-list startup, and mocked/declined 402 challenge fixture.
- Align chain/token support across issue, README, homepage, and package metadata.
- Align service count and pricing tiers before agents route paid calls.

## Commercial follow-on

- **A$390 listing readback:** final mcp.so title, summary, categories, install block, pricing text, package reconciliation, and x402 safety note.
- **A$1,900 cleanup sprint:** PR-ready README/homepage/package-copy alignment plus a mocked install/tool-list/402 smoke script.

Payment after scope confirmation: invoice or USDC on Base/Polygon. Public settlement rail: `0x17D7251A8a8d60ab74d7D2B2d20D2a0389871729`.

Contact: <info@transhumanism.com.au>