MCP servers observed by Lowdown
holdings.proof/mcp-server MCP server: daily status and tool changes
Answered initialize and tools/list on all 4 checks recorded in the last 30 days (2026-11-09 to 2026-11-18) (Lowdown checks this server every 3 days); 219 tools listed. On 2026-11-15 a tool description with a URL appeared (new domain: proof.holdings). MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-09; tool definitions last changed on 2026-11-18 after 3 days without change; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:holdings.proof/mcp-server
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:holdings.proof/mcp-server?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-18: the server answered initialize and tools/list.
- Observed days in the last 30: 4
- Answered initialize and tools/list: 4
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 4 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 3 of 3 compared days.
- 2026-11-18: input or output schemas changed, descriptions changed, tool names changed, server version changed; tool count 216 → 219
- 2026-11-15: input or output schemas changed, descriptions changed, tool names changed, server version changed; tool count 180 → 216; a tool description with a URL appeared (proof.holdings)
- 2026-11-12: input or output schemas changed, descriptions changed, tool names changed, server version changed; tool count 179 → 180
What tools does it list?
200 tools on 2026-11-18:
add_circle_memberadd_circle_member_channeladd_domainadd_verification_providerarchive_approval_channelcancel_lookalike_watchcancel_user_requestcancel_verification_requestcheck_domain_credentialscheck_domain_email_statuscheck_domain_verificationcheck_user_domain_verificationclaim_usernameconfirm_domain_email_codeconnect_cloudflareconnect_dns_providerconnect_godaddycreate_accountcreate_api_keycreate_approval_channelcreate_authorizationcreate_chat_id_discoverycreate_circlecreate_circle_member_drillcreate_confirmationcreate_delegationcreate_dns_credentialcreate_hitlcreate_identity_challengecreate_multi_channel_verificationcreate_profilecreate_sessioncreate_sub_accountcreate_user_requestcreate_verificationcreate_verification_requestcreate_webhook_endpointdelete_approval_channel_keysdelete_circledelete_dns_credentialdelete_domaindelete_domain_verificationdelete_hitldelete_hitl_keysdelete_profiledelete_sub_accountdelete_templatedelete_webhook_endpointexport_authorizationsexport_dataextend_requestget_2fa_statusget_add_email_statusget_add_phone_statusget_api_key_usageget_approval_channelget_approval_channel_keysget_assetget_authorizationget_balanceget_circleget_companyget_confirmationget_confirmation_approval_linkget_current_sub_accountget_current_userget_default_templatesget_delegationget_delegation_carriersget_delegation_tokenget_dns_providersget_domainget_hitlget_hitl_keysget_identity_challengeget_lookalike_watchget_multi_channel_verification_statusget_my_profileget_my_proofget_platform_summaryget_profileget_profile_assetsget_proof_statusget_proof_tokenget_request_by_referenceget_request_proofsget_self_api_keyget_sessionget_settingsget_sub_accountget_subscriptionget_templateget_usageget_user_domain_verification_statusget_verificationget_verification_requestget_verified_userget_webhook_deliveryget_webhook_endpointget_webhook_statsinvite_circle_memberlist_api_keyslist_approval_channelslist_assetslist_auth_sessionslist_authorizationslist_balance_ledgerlist_circle_member_channelslist_circle_memberslist_circleslist_confirmationslist_delegationslist_dns_credentialslist_domainslist_emailslist_hitlslist_incoming_requestslist_lookalike_alertslist_lookalike_reportslist_my_proofslist_my_requestslist_phoneslist_profileslist_public_page_proof_optionslist_reissued_proofslist_revoked_proofslist_sub_accountslist_templateslist_verification_requestslist_verificationslist_verified_userslist_webhook_deliverieslist_webhook_endpointspause_proofpoll_chat_id_discoverypreview_email_removalpreview_phone_removalpreview_profile_deletionpreview_sub_account_deletionpreview_templateproof_holdings_statusregenerate_api_keyremove_circle_memberremove_circle_member_channelremove_emailremove_phonerender_auth_linkrender_templaterequest_approval_channel_authorizationrequest_hitl_authorizationresend_confirmationresend_domain_emailresend_email_otpresend_verificationresume_proofretry_webhook_deliveryrevoke_api_keyrevoke_assetrevoke_auth_sessionrevoke_authorizationrevoke_delegationrevoke_my_proofrevoke_proofrotate_callback_secretrotate_webhook_endpoint_secretsearchsend_account_emailset_email_account_accessset_phone_account_accessset_primary_emailset_primary_phoneset_primary_profileset_primary_sub_accountsetup_domain_emailshare_request_emailstart_2fastart_2fa_for_actionstart_add_emailstart_add_phonestart_domain_email_verificationstart_domain_verificationstart_loginstart_user_domain_verificationsubmit_verification_codesubscribe_lookalike_watchtest_verifytrigger_verificationupdate_approval_channelupdate_circleupdate_hitlupdate_my_profileupdate_profileupdate_profile_proofsupdate_public_pageupdate_public_page_proofsupdate_public_proofsupdate_settingsupdate_sub_accountupdate_sub_account_page_proofsupdate_template
MCP Registry declaration
- Registry name:
holdings.proof/mcp-server - Declared version: 1.13.0
- Status: active
- Declared hosts:
api.proof.holdings
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:holdings.proof/mcp-server", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:holdings.proof/mcp-server?menu=install-check
When running its declared package, wrap it with the stdio proxy. Since lowdown-proxy 0.1.22 the proxy adds this record (install-check) to the server's initialize response; it changes no tool result and blocks nothing:
npx -y lowdown-proxy --target mcp:holdings.proof/mcp-server -- npx -y @proof-holdings/mcp-server
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).