Proofable MCP MCP server

Proofable MCP serves as a portable trust harness for AI agents, enabling identity verification, permission management, and private context handling. It allows agents to check proofs before sensitive actions, manage agent profiles, and facilitate the selling of protected access to services or digital products through a unified connection across various hosts like IDEs and chat interfaces.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by NEUS

MCP endpoint (Streamable HTTP)

https://mcp.neus.network/mcp

Vendor documentation

What you can do with it

Verify agent identity and permissions before executing sensitive actions
Manage AI agent profiles and generate dedicated spend keys
Create and sell protected access listings for AI services or digital products
Check current proofs to determine if an action is Passed, Action needed, or Blocked

Tools advertised by the last live check:

proofable_context
proofable_verifiers_catalog
proofable_proofs_check
proofable_verify_or_guide

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http proofable-mcp https://mcp.neus.network/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add proofable-mcp --url https://mcp.neus.network/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable proofable-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "proofable-mcp": {
      "url": "https://mcp.neus.network/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "proofable-mcp": {
      "type": "streamableHttp",
      "url": "https://mcp.neus.network/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start proofable-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "proofable-mcp": {
      "type": "http",
      "url": "https://mcp.neus.network/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http proofable-mcp https://mcp.neus.network/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "proofable-mcp": {
      "url": "https://mcp.neus.network/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "proofable-mcp": {
      "serverUrl": "https://mcp.neus.network/mcp"
    }
  }
}

See all 782

Do you run Proofable MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing