chatmcp/mcpso #2471 - LogicNodes x402 MCP Bridge

Make the LogicNodes MCP listing safe to accept: one canonical package, clear x402 contract, no buyer confusion.

This no-spend readback is tailored to chatmcp/mcpso#2471 and cmdenney/logicnodes-mcp-bridge. It turns a fresh directory-submission issue into an acceptance checklist for MCP marketplace maintainers and a buyer-agent launch checklist for LogicNodes.

1. Package mismatch

The mcp.so issue proposes @logicnodes/mcp-bridge, but npm registry lookup returned 404. The GitHub README and GitHub page use @logicnodez/mcp-bridge, which exists at v1.0.1.

2. Legacy collision

An unscoped logicnodes-mcp-bridge package exists at v1.0.0 and advertises an older 173-worker/Base-only shape. That can confuse directory reviewers and agent installers.

3. Count/copy drift

The issue says 365+ services; the homepage says 326 services in the hero and 324 tools in the MCP section. Pick one source of truth before listing.

No-spend verification transcript

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

Acceptance checklist for the directory issue

Suggested PR / comment split

Relevant proof