Veriphone
NPM · @PIPEWORX/MCP-VERIPHONE · 2 COMPONENTS
Veriphone MCP — wraps the Veriphone phone-validation API (veriphone.io)
Available components
Last scanned (18 hours ago)
Scores higher than 77% of npm servers
Category CRM and Sales
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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-veriphone). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 327 tokens (~163/item across 2 items; 2 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 Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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 →
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.
- 4 Nov 26 +3
- Stability: unverified → 0.20 ▲ functional
- 29 Oct 26 80
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-veriphone@0.2.0
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 | pipeworx-io/mcp-veriphone |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-veriphone/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3560938097 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:b098cf214e37b6e95e4204ac6ac17429951be42c558d998c82105a100b258928a7f512fbaf050db89402965fe6b0bab7e6454209df5e78708eed99f85 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
veriphone_credits ~77
Check the remaining verification credits / quota for your Veriphone API key — usage counter, plan limit, and pay-as-you-go balance. Example: veriphone_credits({ _apiKey: "your-key" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Your Veriphone API key (free signup at https://veriphone.io/signup). |
No output schema declared.
No examples provided.
veriphone_verify ~198
Validate a phone number and return whether it is valid, its line type (mobile/fixed_line/voip/etc), carrier, region, country, and canonical formats (E.164, international, local). Pass numbers in E.164 form (e.g. "+14155552671"); for local numbers supply default_country. Example: veriphone_verify({ phone: "+14155552671", _apiKey: "your-key" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Your Veriphone API key (free signup at https://veriphone.io/signup). |
| default_country | string | – | Optional ISO-3166 alpha-2 country code (e.g. "US", "GB") used to interpret a number that has no leading "+" country prefix. |
| phone | string | yes | Phone number to validate. Prefer E.164 format, e.g. "+14155552671". Local numbers are allowed if default_country is supplied. |
No output schema declared.
No examples provided.
How do I install the Veriphone MCP server?
Veriphone runs locally as an npm package, launched with npx -y @pipeworx/mcp-veriphone. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-veriphone
claude mcp add pipeworx-io-veriphone -- npx -y @pipeworx/mcp-veriphone
What is the Veriphone MCP server?
Veriphone is an MCP server listed in the public MCP registry as io.github.pipeworx-io/veriphone. Veriphone MCP, wraps the Veriphone phone-validation API (veriphone.io). This page covers its npm package (@pipeworx/mcp-veriphone).
Is the Veriphone MCP server safe to use?
Veriphone scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 Veriphone MCP server expose?
Veriphone exposes 2 tools: veriphone_verify, veriphone_credits. Their descriptions and schemas cost roughly 275 tokens of context every time the server is loaded.
Is the Veriphone MCP server still maintained?
Veriphone is still listed as active in the MCP registry. We last reached this channel on 5 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 Veriphone MCP server under?
Veriphone 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 Veriphone MCP server?
VerifyMCP ran 16 checks on Veriphone, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. 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.