Plugged.in Proxy vs Proof Holdings
Plugged.in Proxy is an MCP server published by VeriTeknik. Marketplaces we read that list it: 1 (Docker MCP Catalog). Proof Holdings is an MCP server published by proof.holdings. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Plugged.in Proxy |   Proof Holdings |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:b7c32590b270 Forks (GitHub): 30 Pulls (Docker Hub): 36 074 Stars (Docker Hub): 3 Stars (GitHub): 137 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.7.0 Downloads/month (npm): 739 Downloads/week (npm): 422 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Plugged.in Proxy | Proof Holdings |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 137 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 36 074 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 30 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-16 |
| Where it runs (differs) | On your machine (mcp/pluggedin-mcp-proxy) | Remote server (api.proof.holdings/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 6 | Not published |
| Environment variables it asks for | 2, secrets among them: 1 | 2, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/veriteknik/pluggedin-mcp-proxy | github.com/proofholdings/mcp-server |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 3 days ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Plugged.in Proxy
A unified MCP proxy that aggregates multiple MCP servers into one interface, enabling seamless tool discovery and management across all your AI interactions. Manage all your MCP servers from a single connection point with RAG capabilities and real-time notifications.
Proof Holdings
One API, all things verified — control, delegation, human approval, anti-impersonation.
How to run each
Plugged.in Proxy As a local MCP server: Docker image
claude mcp add --env "PLUGGEDIN_API_KEY=<YOUR_PLUGGEDIN_API_KEY>" --transport stdio pluggedin-mcp-proxy -- docker run -i --rm -e PLUGGEDIN_API_KEY mcp/pluggedin-mcp-proxyRequires: PLUGGEDIN_API_KEY (secret)
Proof Holdings As a remote MCP server
claude mcp add --transport http proof-holdings https://api.proof.holdings/mcpRequires: PROOF_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Proof Holdings has a remote endpoint we check. How we check endpoints
Tools each declares
Only Plugged.in Proxy has
pluggedin_ask_knowledge_basepluggedin_delete_notificationpluggedin_discover_toolspluggedin_list_notificationspluggedin_mark_notification_donepluggedin_send_notification
Only Proof Holdings has
add_circle_memberadd_circle_member_channeladd_domainadd_verification_providercancel_user_requestcancel_verification_requestcheck_domain_credentialscheck_domain_email_statuscheck_domain_verificationcheck_user_domain_verificationclaim_usernameconfirm_domain_email_code
Show the remaining 155
connect_cloudflareconnect_dns_providerconnect_godaddycreate_accountcreate_api_keycreate_authorizationcreate_chat_id_discoverycreate_circlecreate_circle_member_drillcreate_confirmationcreate_delegationcreate_dns_credentialcreate_hitlcreate_identity_challengecreate_multi_channel_verificationcreate_profilecreate_sessioncreate_user_requestcreate_verificationcreate_verification_requestdelete_circledelete_dns_credentialdelete_domaindelete_domain_verificationdelete_hitldelete_hitl_keysdelete_profiledelete_templateexport_authorizationsexport_dataextend_requestget_2fa_statusget_add_email_statusget_add_phone_statusget_api_key_usageget_assetget_authorizationget_circleget_confirmationget_confirmation_approval_linkget_current_userget_default_templatesget_delegationget_dns_providersget_domainget_hitlget_hitl_keysget_identity_challengeget_multi_channel_verification_statusget_my_profileget_platform_summaryget_profileget_profile_assetsget_proof_statusget_request_by_referenceget_request_proofsget_self_api_keyget_sessionget_settingsget_subscriptionget_templateget_usageget_user_domain_verification_statusget_verificationget_verification_requestget_verified_userget_webhook_deliveryget_webhook_statsinvite_circle_memberlist_api_keyslist_assetslist_auth_sessionslist_authorizationslist_circle_member_channelslist_circle_memberslist_circleslist_confirmationslist_delegationslist_dns_credentialslist_domainslist_emailslist_hitlslist_incoming_requestslist_my_requestslist_phoneslist_profileslist_revoked_proofslist_templateslist_verification_requestslist_verificationslist_verified_userslist_webhook_deliveriespoll_chat_id_discoverypreview_templateregenerate_api_keyremove_circle_memberremove_circle_member_channelremove_emailremove_phonerender_auth_linkrender_templaterequest_hitl_authorizationresend_domain_emailresend_email_otpresend_verificationretry_webhook_deliveryrevoke_api_keyrevoke_assetrevoke_auth_sessionrevoke_authorizationrevoke_delegationrevoke_proofsearchsend_account_emailset_primary_emailset_primary_phoneset_primary_profilesetup_domain_emailshare_request_emailstart_2fastart_2fa_for_actionstart_add_emailstart_add_phonestart_domain_email_verificationstart_domain_verificationstart_loginstart_user_domain_verificationsubmit_verification_codetest_verifytrigger_verificationupdate_circleupdate_hitlupdate_my_profileupdate_profileupdate_profile_proofsupdate_public_proofsupdate_settingsupdate_templateupload_hitl_keysvalidate_proofverify_2faverify_2fa_magic_linkverify_delegationverify_delegationsverify_domainverify_domain_with_credentialsverify_email_otpwait_for_2fawait_for_account_creationwait_for_chat_id_discoverywait_for_confirmationwait_for_loginwait_for_requestwait_for_sessionwait_for_verification
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (Proof Holdings as of 2026-10-21). More tools is not better in itself: compare what each needs for the job.
Settings each asks for
Only Plugged.in Proxy asks for
PLUGGEDIN_API_BASE_URLPLUGGEDIN_API_KEY (secret)
Only Proof Holdings asks for
PROOF_API_KEY (secret)PROOF_BASE_URL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Plugged.in Proxy · What it can do: Proof Holdings · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.