ClientProof MCP Server

by useclientproof Your server? Claim it

answering

ClientProof is answering right now. Last checked 9 min ago.

Read-only tools for agency testimonial walls: list clients, testimonials, and embed widgets.

Uptime history 67 hours of history

67 hours agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

336 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Nothing serious here today

Today is the operative word: we check ClientProof every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add clientproof --transport http https://useclientproof.com/api/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "clientproof": {
      "url": "https://useclientproof.com/api/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.clientproof]
url = "https://useclientproof.com/api/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "clientproof": {
      "url": "https://useclientproof.com/api/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "clientproof": {
      "url": "https://useclientproof.com/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URL	Transport	State	Latency	Checked
https://useclientproof.com/api/mcp	streamable-http	sign-in	294 ms	9 min ago

Alternatives to ClientProof

same job, measured the same way

agentgate

by ciceroyang

Read-only evidence for the tools agents run: MCP server records, coverage and policy.

72 installs/wk local only

VMware Monitor

by vmware-skills

Read-only VMware vCenter/ESXi monitoring, 32 MCP tools; vSphere calls allowlist-gated in tests.

local only

Ratchet

by iversonwuwei

Read-only tools to inspect your agent setup: list MCP servers, flag unpinned ones, test a policy.

local only

Currents

by currents

Self-healing CI tests and proof of work for AI agents

answering

Mockpost

by reiarseni

Local multi-channel message emulator for E2E testing, with MCP tools for LLM agents.

117 installs/wk local only

ClientProof — questions

Answers built from our own checks of this server.

Why is there no tool list for ClientProof?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is ClientProof working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 336 ms. The bar chart above shows every period we have measured.

How do I connect ClientProof?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.

How do you sign in to ClientProof?

No API key is involved. ClientProof answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.

How fast is ClientProof?

It answers our handshake in 336 ms on average, which is faster than 41% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.