Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Proof Holdings

NPM · @PROOF-HOLDINGS/MCP-SERVER · 2 COMPONENTS

One API, all things verified — control, delegation, human approval, anti-impersonation.

−2 this week 54 Trust /100

Last scanned (20 hours ago)

Scores higher than 27% of npm servers

Category Security

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 42 of 123 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability0
  • Schema quality not yet verified: the captured schema was too large for us to store in full, or the server stopped listing its tools part-way, so we will not judge it on a partial copy.Unverified
Stability & Change Management86
  • Stability check failed: the tool surface changed between 1.7.1 and 1.13.0: 0 tool removals, 2 breaking changes, 53 additions. See how to fix → Fail
Tool Coverage0
  • Tool coverage not yet verified: the captured tool definitions were too large for us to store in full, or the server stopped listing its tools part-way, so we will not judge them on a partial copy.Unverified
Tool Safety0
  • Tool safety not yet verified: the captured tool definitions were too large for us to store in full (the trim removes the very descriptions this category reads), or the server stopped listing its tools part-way.Unverified
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 3 categories

Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

What we tested

Checks we ran (11)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Stability
  • MCP protocol

Checks we could not complete (3)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema quality not yet verified: the captured schema was too large for us to store in full, or the server stopped listing its tools part-way, so we will not judge it on a partial copy.
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: the captured tool definitions were too large for us to store in full, or the server stopped listing its tools part-way, so we will not judge them on a partial copy.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: the captured tool definitions were too large for us to store in full (the trim removes the very descriptions this category reads), or the server stopped listing its tools part-way.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 −2
    • Package version: 1.7.1 → 1.13.0 functional
  • 19 Nov 26 0
    • Package version: 1.7.1 → 1.13.0 functional
  • 17 Nov 26 +11
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → 0.84 ▲ functional
    • Package version: 1.7.1 → 1.13.0 functional
  • 16 Nov 26 −11
    • Known CVEs: pass → unverified ▼ security
    • Stability: fail → unverified ▼ security
    • Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
    • Dependency health: 0.84 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
    • Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
    • Package version: 1.11.0 → 1.13.0 functional
    • Package version: 1.7.1 → 1.12.0 functional
    • Package version: 1.11.0 → 1.12.0 functional
    • Package version: 1.7.1 → 1.11.0 functional
  • 15 Nov 26 0
    • Package version: 1.7.1 → 1.11.0 functional
  • 14 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97.

  • 13 Nov 26 +25
    • Malware scan: unverified → pass ▲ security
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → 0.84 ▲ functional
    • Package version: 1.7.1 → 1.10.0 functional
  • 12 Nov 26 −10
    • Known CVEs: pass → unverified ▼ security
    • Malware scan: unverified → pass ▲ security
    • Dependency health: 0.84 → unverified ▼ functional
    • Package version: 1.7.1 → 1.10.0 functional
    • Package version: 1.7.1 → 1.9.0 functional
    • Package version: 1.7.1 → 1.8.4 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/@proof-holdings/mcp-server@1.13.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 123 packages
Packages resolved 123
Stale 42
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 220 exposed · ~35,450 tokens partial

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
create_sub_account ~199

No description provided.

NameTypeReqDescription
avatar_urlstring––
biostring––
business_namestring––
display_namestring––
email_themestring––
is_businessboolean––
is_primaryboolean––
is_publicboolean––
support_emailstring––
themeobject––
NameTypeReqDescription
avatar_urlstring|null––
biostring––
business_namestring––
channels_completebooleanyes–
created_atstringyes–
custom_linksarrayyes–
display_namestring––
email_themestring|nullyes–
idstringyes–
is_businessbooleanyes–
is_primarybooleanyes–
is_publicbooleanyes–
name_headline–yes–
name_review–yes–
profile_idstringyes–
proof_orderstringyes–
public_proofsarrayyes–
show_delegationsbooleanyes–
show_proof_channelsbooleanyes–
show_verification_datesbooleanyes–
support_emailstring|nullyes–
themeobjectyes–
updated_atstringyes–
usernamestring|null––
username_is_defaultboolean––
verification_levelstringyes–
view_countintegeryes–

No examples provided.

create_user_request ~353

No description provided.

NameTypeReqDescription
action_contextobject––
action_typestring––
assetsarrayyes–
callback_urlstring––
expires_in_hoursinteger––
partial_okboolean––
public_profile_idstring––
redirect_urlstring––
reference_idstring––
validity_requirementstring––
NameTypeReqDescription
action_context–––
action_type–––
assets–––
callback_url–––
completed_at–––
computed_state–––
created_at–––
expires_at–––
id–––
outcome–––
outcome_timeout_seconds–––
partial_ok–––
progress–––
redirect_url–––
reference_id–––
status–––
updated_at–––
validity_requirement–––
verification_url–––

No examples provided.

create_verification ~626

No description provided.

NameTypeReqDescription
bot_tokenstring––
channelstringyes–
client_metadataobject––
dns_providerobject––
email_prefixstring––
external_user_idstring––
identifierstringyes–
own_domainboolean––
profile_idstring––
proof_expiry_daysinteger––
typestringyes–
NameTypeReqDescription
attempts–––
challenge–––
channel–––
created_at–––
environment–––
external_user_id–––
id–––
identifier–––
max_attempts–––
proof–––
status–––
type–––
updated_at–––
verified_at–––

No examples provided.

create_verification_request ~339

No description provided.

NameTypeReqDescription
action_contextobject––
action_typestring––
assetsarrayyes–
callback_urlstring––
expires_ininteger––
partial_okboolean––
proof_expiry_daysinteger––
public_profile_idstring––
redirect_urlstring––
reference_idstring––
validity_requirementstring––
NameTypeReqDescription
action_context–––
action_type–––
assets–––
callback_url–––
completed_at–––
computed_state–––
created_at–––
expires_at–––
id–––
outcome–––
outcome_timeout_seconds–––
partial_ok–––
progress–––
redirect_url–––
reference_id–––
status–––
updated_at–––
validity_requirement–––
verification_url–––

No examples provided.

create_webhook_endpoint ~348

No description provided.

NameTypeReqDescription
description–––
eventsarray––
profile_idsarray––
scopestringyes–
statusstring––
urlstringyes–
NameTypeReqDescription
created_at–––
description–––
events–––
id–––
legacy–––
profile_ids–––
scope–––
secret–––
secret_set–––
status–––
updated_at–––
url–––

No examples provided.

delete_approval_channel_keys ~75

No description provided.

NameTypeReqDescription
hitl_idstringyes–
NameTypeReqDescription
message–––

No examples provided.

delete_circle ~84

No description provided.

NameTypeReqDescription
idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

delete_dns_credential ~82

No description provided.

NameTypeReqDescription
idstringyes–
NameTypeReqDescription
messagestring––
successbooleanyes–

No examples provided.

delete_domain ~190

No description provided.

NameTypeReqDescription
idstringyes–
NameTypeReqDescription
carriers–––
delegations_revoked–––
domain–––
external–––
notice–––
proofs_revoked–––
success–––

No examples provided.

delete_domain_verification ~121

No description provided.

NameTypeReqDescription
idstringyes–
NameTypeReqDescription
deletedbooleanyes–
idstringyes–

No examples provided.

delete_hitl ~29

No description provided.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

delete_hitl_keys ~31

No description provided.

NameTypeReqDescription
hitl_idstringyes–

No output schema declared.

No examples provided.

delete_profile ~25

No description provided.

NameTypeReqDescription
profile_idstringyes–

No output schema declared.

No examples provided.

delete_sub_account ~223

No description provided.

NameTypeReqDescription
profile_idstringyes–
NameTypeReqDescription
api_keys_revoked–––
authorizations_revoked–––
circles_detached–––
confirmations_denied–––
domains_detached–––
hitl_archived–––
hitl_detached–––
message–––
new_primary–––
project–––
requests_cancelled–––
requests_detached–––
success–––
templates_deleted–––
username_retired–––
verifications_detached–––
was_primary–––

No examples provided.

delete_template ~123

No description provided.

NameTypeReqDescription
channelstringyes–
message_typestringyes–
profile_idstring––
NameTypeReqDescription
messagestring––
successbooleanyes–

No examples provided.

delete_webhook_endpoint ~85

No description provided.

NameTypeReqDescription
idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

export_authorizations ~180

No description provided.

NameTypeReqDescription
formatstring––
fromstring––
statusstring––
tostring––
NameTypeReqDescription
data–––
total–––

No examples provided.

export_data ~223

No description provided.

NameTypeReqDescription
export_idstring––
NameTypeReqDescription
counts–––
download_path–––
downloaded_at–––
error–––
expires_at–––
id–––
latest–––
ready_at–––
receipts–––
requested_at–––
size_bytes–––
status–––

No examples provided.

extend_request ~111

No description provided.

NameTypeReqDescription
extends_by_hoursinteger––
idstringyes–
NameTypeReqDescription
expires_atstringyes–
messagestringyes–
statusstringyes–
successbooleanyes–

No examples provided.

get_2fa_status ~203

No description provided.

NameTypeReqDescription
session_idstringyes–
NameTypeReqDescription
action_typestringyes–
grant_expires_atstring––
grant_single_useboolean––
session_idstringyes–
statusstringyes–
verified_atstring––

No examples provided.

get_add_email_status ~76

No description provided.

NameTypeReqDescription
session_idstringyes–
NameTypeReqDescription
channelstringyes–
emailstringyes–
session_idstringyes–
statusstringyes–
verified_atstring––

No examples provided.

get_add_phone_status ~137

No description provided.

NameTypeReqDescription
session_idstringyes–
NameTypeReqDescription
channelstringyes–
phone_numberstring––
session_idstringyes–
statusstringyes–
verified_atstring––

No examples provided.

get_api_key_usage ~161

No description provided.

NameTypeReqDescription
environmentstring––
idstringyes–
NameTypeReqDescription
api_keyobjectyes–
attributed_fractionnumber|nullyes–
attribution_cutoff_atstring|nullyes–
authorizationsobjectyes–
confirmationsobjectyes–
verification_requestsobjectyes–
verificationsobjectyes–

No examples provided.

get_approval_channel ~69

No description provided.

NameTypeReqDescription
idstringyes–
NameTypeReqDescription
channelsarrayyes–
circle_idstring|null––
created_atstringyes–
environmentstringyes–
idstringyes–
keypair–yes–
namestring|null––
profile_idstring|null––
statusstringyes–
timeout_secondsintegeryes–
updated_atstringyes–
user_idstring|nullyes–

No examples provided.

get_approval_channel_keys ~131

No description provided.

NameTypeReqDescription
hitl_idstringyes–
NameTypeReqDescription
backup_dek_ivstring|null––
backup_dek_tagstring|null––
backup_wrapped_dekstring|null––
dek_ivstring|null––
dek_tagstring|null––
encrypted_private_keystring––
kdf_saltstring––
kidstringyes–
public_keystring|nullyes–
wrapped_dekstring|null––

No examples provided.

get_asset ~25

No description provided.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

get_authorization ~68

No description provided.

NameTypeReqDescription
idstringyes–
NameTypeReqDescription
authorized_atstring––
bsuidstring|null––
business_namestringyes–
channelstringyes–
circle_id–––
confirmations_sentintegeryes–
created_atstringyes–
denied_atstring––
enrolledbooleanyes–
expires_atstringyes–
hitl_id–––
idstringyes–
labelstring|null––
last_used_atstring––
phonestring|null––
proof_tokenstring––
recipientstring|null––
recipient_display_namestring|nullyes–
revocation_reasonstring––
revoked_atstring––
scopestringyes–
statusstringyes–
updated_atstringyes–
verification_idstring––

No examples provided.

get_balance ~151

No description provided.

Input schema present but exposes no named parameters.

NameTypeReqDescription
auto_top_upobjectyes–
balanceobjectyes–
billing_enabledbooleanyes–
low_balance_thresholdintegeryes–
top_up_amountsarrayyes–
top_up_charges–––

No examples provided.

get_circle ~81

No description provided.

NameTypeReqDescription
idstringyes–
NameTypeReqDescription
created_atstringyes–
environmentstringyes–
idstringyes–
member_countintegeryes–
membersarrayyes–
namestring|nullyes–
owner_namestring|nullyes–
profile_idstring|nullyes–
proof_me_enabledbooleanyes–
statusstringyes–
updated_atstringyes–
user_idstring|nullyes–

No examples provided.

get_company ~133

No description provided.

Input schema present but exposes no named parameters.

NameTypeReqDescription
company–––

No examples provided.

get_confirmation ~67

No description provided.

NameTypeReqDescription
idstringyes–
NameTypeReqDescription
created_atstringyes–
hitl_id–yes–
idstringyes–
messagestringyes–
proof_tokenstring|null––
resendsarray––
resolved_atstring|null––
response–––
statusstringyes–
timeout_atstring|null––
updated_atstringyes–

No examples provided.

get_confirmation_approval_link ~204

No description provided.

NameTypeReqDescription
idstringyes–
NameTypeReqDescription
approval_urlstringyes–

No examples provided.

get_current_sub_account ~147

No description provided.

Input schema present but exposes no named parameters.

NameTypeReqDescription
avatar_urlstring|null––
biostring––
business_namestring––
channels_completebooleanyes–
created_atstringyes–
custom_linksarrayyes–
display_namestring––
email_themestring|nullyes–
idstringyes–
is_businessbooleanyes–
is_primarybooleanyes–
is_publicbooleanyes–
name_headline–yes–
name_review–yes–
profile_idstringyes–
proof_orderstringyes–
public_proofsarrayyes–
show_delegationsbooleanyes–
show_proof_channelsbooleanyes–
show_verification_datesbooleanyes–
support_emailstring|nullyes–
themeobjectyes–
updated_atstringyes–
usernamestring|null––
username_is_defaultboolean––
verification_levelstringyes–
view_countintegeryes–

No examples provided.

get_current_user ~103

No description provided.

Input schema present but exposes no named parameters.

NameTypeReqDescription
avatar_urlstring|nullyes–
created_atstringyes–
deletionobjectyes–
display_namestring––
idstringyes–
last_login_atstring––
login_channelstringyes–
login_emailstring––
login_phonestring––
phone_numberstring––
tenantobjectyes–
verification_countintegeryes–

No examples provided.

get_default_templates ~80

No description provided.

Input schema present but exposes no named parameters.

NameTypeReqDescription
defaultsobjectyes–

No examples provided.

get_delegation ~137

No description provided.

NameTypeReqDescription
idstringyes–
NameTypeReqDescription
control_proof–––
created_at–––
delegate–––
delegation_id–––
effective_status–––
environment–––
expires_at–––
id–––
is_valid–––
issued_at–––
principal–––
revoked_at–––
revoked_reason–––
scope–––
status–––
token–––

No examples provided.

get_delegation_carriers ~132

No description provided.

NameTypeReqDescription
idstringyes–
NameTypeReqDescription
carriersarrayyes–

No examples provided.

get_delegation_token ~107

No description provided.

NameTypeReqDescription
handlestringyes–
NameTypeReqDescription
tokenstringyes–

No examples provided.

get_dns_providers ~67

No description provided.

Input schema present but exposes no named parameters.

NameTypeReqDescription
countintegeryes–
providersobjectyes–

No examples provided.

get_domain ~78

No description provided.

NameTypeReqDescription
idstringyes–
NameTypeReqDescription
dataobjectyes–
instructionsobjectyes–

No examples provided.

get_hitl ~27

No description provided.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

get_hitl_keys ~31

No description provided.

NameTypeReqDescription
hitl_idstringyes–

No output schema declared.

No examples provided.

get_identity_challenge ~111

No description provided.

NameTypeReqDescription
idstringyes–
NameTypeReqDescription
channelstring––
circle_idstring|null––
confirm_channelstring––
created_atstring––
expires_atstring––
idstringyes–
is_drillboolean––
proof_idstring|null––
proof_tokenstring|null––
resolved_atstring|null––
single_channel_warningboolean––
statusstringyes–

No examples provided.

get_lookalike_watch ~71

No description provided.

Input schema present but exposes no named parameters.

NameTypeReqDescription
activated_atstring|nullyes–
brand_tokensarrayyes–
created_atstringyes–
idstringyes–
last_report_periodstring|nullyes–
notify_emailstringyes–
owned_namespacesarrayyes–
statusstringyes–
updated_atstringyes–

No examples provided.

get_multi_channel_verification_status ~168

No description provided.

NameTypeReqDescription
group_idstringyes–
NameTypeReqDescription
channels–––
group_id–––
proof–––
status–––
winning_channel–––

No examples provided.

get_my_profile ~17

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_my_proof ~71

No description provided.

NameTypeReqDescription
idstringyes–
NameTypeReqDescription
channelstringyes–
created_atstringyes–
has_proofboolean––
idstringyes–
identifierstringyes–
metadataobject––
proof_expires_atstringyes–
proof_idstring|null––
proof_statusstring|null––
proof_tokenstring|null––
statusstringyes–
typestringyes–
verified_atstring––

No examples provided.

Install

How do I install the Proof Holdings MCP server?

Proof Holdings runs locally as an npm package, launched with npx -y @proof-holdings/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @proof-holdings/mcp-server

# add to Claude Code
claude mcp add holdings-proof-mcp-server -- npx -y @proof-holdings/mcp-server
Common questions

What is the Proof Holdings MCP server?

Proof Holdings is an MCP server listed in the public MCP registry as holdings.proof/mcp-server. One API, all things verified, control, delegation, human approval, anti-impersonation. This page covers its npm package (@proof-holdings/mcp-server).

Is the Proof Holdings MCP server safe to use?

Proof Holdings scores 54 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

Is the Proof Holdings MCP server still maintained?

Proof Holdings is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Proof Holdings MCP server under?

Proof Holdings declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the Proof Holdings MCP server?

VerifyMCP ran 11 checks on Proof Holdings, covering Malware scan, Known CVEs, Install scripts, Dependency health and 7 more. 3 items could not be completed, a gap on our side rather than a finding about Proof Holdings: Schema quality, Tool coverage and Tool safety. 3 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.