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.
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.
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.
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.
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.
npm view @logicnodes/mcp-bridge -> 404 Not Found.npm view @logicnodez/mcp-bridge -> package exists, version 1.0.1, x402/USDC description.npm view logicnodes-mcp-bridge -> package exists, version 1.0.0, older 173-worker/Base-only description.web_fetch https://logicnodes.io -> public homepage confirms x402/per-call positioning, but shows mixed install/package wording and service counts.web_fetch README -> README confirms scoped package @logicnodez/mcp-bridge and MCP config requiring LOGICNODES_API_KEY.No package execution, API-key use, x402 payment, wallet signing, transfer, paid call, signup, or legal-term acceptance was performed.
npx -y @logicnodez/mcp-bridge.@logicnodez vs @logicnodes.