Home / MCP registry index / holdings.proof/mcp-server
Proof Holdings
holdings.proof/mcp-server in the official MCP registry.
Endpoint https://api.proof.holdings/mcp. Source: github.com/ProofHoldings/mcp-server.
The registry describes it as: One API, all things verified — control, delegation, human approval, anti-impersonation.
We read its 167 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
create_verification get_verification list_verifications trigger_verification submit_verification_code resend_verification test_verify list_verified_users get_verified_user start_domain_verification check_domain_verification delete_domain_verification wait_for_verification create_multi_channel_verification get_multi_channel_verification_status create_verification_request get_verification_request get_request_proofs list_verification_requests get_request_by_reference cancel_verification_request wait_for_request validate_proof get_proof_status revoke_proof list_revoked_proofs create_session get_session wait_for_session list_assets get_asset revoke_asset get_current_user list_auth_sessions revoke_auth_session get_usage get_platform_summary get_settings update_settings export_data search get_self_api_key get_api_key_usage list_templates get_default_templates get_template update_template delete_template preview_template render_template get_webhook_stats list_webhook_deliveries get_webhook_delivery retry_webhook_delivery get_subscription list_profiles create_profile get_profile update_profile delete_profile and 107 more
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/holdings-proof-mcp-server)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.