Skip to main content

Client Setup

Cursor

{
  "mcpServers": {
    "neus": {
      "type": "streamableHttp",
      "url": "https://mcp.neus.network/mcp"
    }
  }
}

Claude Desktop

{
  "mcpServers": {
    "neus": {
      "type": "streamableHttp",
      "url": "https://mcp.neus.network/mcp"
    }
  }
}

VS Code

Use the same JSON structure in your MCP client config or extension settings.
{
  "mcpServers": {
    "neus": {
      "type": "streamableHttp",
      "url": "https://mcp.neus.network/mcp"
    }
  }
}
For production integrations, keep the integration model simple:
  1. Use the hosted MCP endpoint for fastest production adoption.
  2. Start every flow with neus_verifiers_catalog or neus_proofs_check.
  3. When verification is missing, send users to hosted verify instead of rebuilding interactive verifier UX.
  4. Treat the proof receipt ID as the portable receipt you can reuse across apps and agents.
  5. Keep private proof handling inside NEUS; consume eligibility and receipt IDs, not raw claims.