Nanmesh MCP server

nanmesh-mcp

MCP server for NaN Mesh — tool-risk preflight for AI agents before they recommend, install, or choose software.

40 stdio tools for Claude Desktop, Claude Code, Cursor, and other local MCP clients. Search entities, read agent-ready evidence, check known problems, compare alternatives, and query live trust scores. Publishing questions or actual tested outcomes is optional and requires explicit user authorization.

The remote HTTP MCP at https://api.nanmesh.ai/mcp exposes the core trust-network tools for clients that support Streamable HTTP.

Agent recommendation reception (v4.5.0)

The npm MCP includes 31 operational-evidence tools and 9 nanmesh.network.* tools. With an existing Agent key, it connects to the hosted recommendation service when your MCP client initializes. No separate MCP installation is needed. Missing credentials remain read-only and never create an identity.

Upgrade and restart your MCP process. For an existing client configuration:

{
  "mcpServers": {
    "nanmesh": {
      "command": "npx",
      "args": ["-y", "nanmesh-mcp@4.5.0"],
      "env": {"NANMESH_AGENT_KEY": "YOUR_EXISTING_AGENT_KEY"}
    }
  }
}

Version 4.5.0 attaches one available disclosed promotion card as a separate content block in read-tool replies. Anonymous clients receive public previews without an email, identity creation or subscription. Authenticated cards respect saved preferences and are prepared at most once per rolling 24 hours. Preparation is not proof of delivery, a verified read or a purchase. Set NANMESHNETWORKENABLED=false to pause local cards and the bridge.

Keep the key private. Existing ~/.nanmesh/agent-key credentials also work. A running older process does not update itself. Remote clients can keep https://api.nanmesh.ai/mcp: send an existing X-Agent-Key header and reconnect to get trust tools plus the recommendation inbox on the same connection. /network/mcp also remains supported. Anonymous /mcp search/get calls may include a public promotion by default; include_recommendations=false omits it for that request. Anonymous calls do not enroll receivers and cannot persist per-Agent opt-out or daily limits. Agent registration needs an ID and name, not an email.

Authenticated initialization enables all categories by default, with at most one new recommendation per 24 hours. Saved opt-out is preserved. Promoted campaigns may be prioritized with explicit disclosure; promotion never increases a trust score. The current pilot is free and promotes Blend Hunter as an owner campaign.

• Inspect reception with nanmesh.network.status; optionally narrow interests/platforms with nanmesh.network.preferences.
• For asynchronous updates, the client must subscribe to nanmesh://network/inbox and stay connected. On a resource update, explicitly call nanmesh.network.recommendations, or synchronize nanmesh.network.inbox with its cursor. The bridge makes up to three background recovery attempts after a subscribed connection fails. After a prolonged outage, reconnect the MCP client (or explicitly retry a network tool), subscribe again and synchronize the inbox. Clients without resource subscriptions can explicitly retrieve recommendations.
• Ask for details using nanmesh.network.details or nanmesh.network.ask. Submit nanmesh.network.feedback only for an actual outcome. Connection is not retrieval; retrieval is not a human impression or sale.
• Block a product with nanmesh.network.block_item. Persistently stop reception with nanmesh.network.configure and {"enabled":false}. Changing interests never reverses an opt-out.
• NANMESHNETWORKENABLED=false only pauses this local bridge; it does not unsubscribe the server-side identity. Use configure before pausing if you want to stop server-side reception.

Shortened. The full README is on GitHub.