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.

ProofTell

NPM · @PROOFTELL/MCP

Phone, email and IP checks and an identity's 0-100 risk score, with one ProofTell API key.

Available components

0 this week 79 Trust /100

Last scanned (15 hours ago)

Scores higher than 63% 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
  • 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to prooftell/integrations). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 9 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 902 tokens (~180/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

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.

  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

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.

  • 12 Nov 26 +26
    • Malware scan: unverified → pass ▲ security
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → 0.85 ▲ functional
  • 11 Nov 26 53

    First indexed and scored.

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/@prooftell/mcp@1.0.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo prooftell/integrations
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/prooftell/integrations/.github/workflows/release-mcp.yml@refs/tags/mcp-v1.0.1
Rekor log index 3812026668
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:fe5a5ad15e5bd481ea945aff3c856cf27aa0a8415ba285d23e3af0ae78718f4165c569c199ef6c2ce116d0569f9e1a5d14c27540b92ca674e9ecd568e

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~744 tokens

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
assess_identity_risk ~238

Scores an identity from 0 (no risk found) to 100 with a verdict (allow, review or deny) and the reasons that added to the score, from any mix of phone number, email address and IP address, each checked in parallel; each signal's own result is under signals. Give at least one of the three. Charged per signal from your balance; the sandbox (a pt_test_ key) is free.

NameTypeReqDescription
countrystring–The two-letter country code (ISO 3166-1 alpha-2, e.g. GB) of a number given in national format.
emailstring–The email address, e.g. jane@example.com.
ipstring–The IPv4 or IPv6 address of the end user, e.g. 203.0.113.1.
phonestring–The phone number, in international format (E.164, e.g. +447700900123), or in national format with the country.
referencestring–Your own id for this check (a sign-up, an order), echoed back.

No output schema declared.

No examples provided.

get_balance ~63

The account's balance in US dollars (paid and promotional money, what is held for running files) and what this month's checks cost so far, by signal. Free. Useful before a batch of checks, or to tell a live key (pt_live_) from the sandbox.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

look_up_ip_address ~94

Finds where an IP address is and what network it is on (country, city, ASN and organisation), and whether it is Tor, a VPN or a datacenter. Charged per check from your balance; the sandbox (a pt_test_ key) is free.

NameTypeReqDescription
ipstringyesThe IPv4 or IPv6 address of the end user, e.g. 203.0.113.1.

No output schema declared.

No examples provided.

look_up_phone_number ~209

Checks a phone number: valid or not, its formats and country, then by level its line type, the carrier it is on today, whether it is live on the network, or a fraud score. The levels are a ladder, each including the ones before it and priced on its own: basic, line_type (the default), current_carrier, line_status, fraud_score; what is not offered for the number comes back as unavailable, at no cost. Charged per check from your balance; the sandbox (a pt_test_ key) is free.

NameTypeReqDescription
countrystring–The two-letter country code (ISO 3166-1 alpha-2, e.g. GB) of a number given in national format.
levelstring–How far to look; line_type when omitted.
phonestringyesThe phone number, in international format (E.164, e.g. +447700900123), or in national format with the country.

No output schema declared.

No examples provided.

verify_email_address ~140

Checks whether an email address accepts mail: a verdict (deliverable, undeliverable, risky, unknown) with its reason, the flags (disposable, role address, catch-all…), the safe action for a sign-up form, and a likely correction of a misspelt domain. Charged per check from your balance; the sandbox (a pt_test_ key) is free.

NameTypeReqDescription
emailstringyesThe email address, e.g. jane@example.com.
timeoutinteger–Milliseconds allowed for the mail server, 1000 to 45000 (the default); past it the address comes back unknown, free.

No output schema declared.

No examples provided.

Install

How do I install the ProofTell MCP server?

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

npm · @prooftell/mcp

# add to Claude Code
claude mcp add com-prooftell-mcp -- npx -y @prooftell/mcp
Common questions

What is the ProofTell MCP server?

ProofTell is an MCP server listed in the public MCP registry as com.prooftell/mcp. Phone, email and IP checks and an identity's 0-100 risk score, with one ProofTell API key. This page covers its npm package (@prooftell/mcp).

Is the ProofTell MCP server safe to use?

ProofTell scores 79 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. Its build provenance is signed and verified. 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.

What tools does the ProofTell MCP server expose?

ProofTell exposes 5 tools: look_up_phone_number, verify_email_address, look_up_ip_address, assess_identity_risk, get_balance. Their descriptions and schemas cost roughly 744 tokens of context every time the server is loaded.

Is the ProofTell MCP server still maintained?

ProofTell 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 ProofTell MCP server under?

ProofTell 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 ProofTell MCP server?

VerifyMCP ran 15 checks on ProofTell, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about ProofTell: Stability. One category scores 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.