# Abstract Phone (npm · @pipeworx/mcp-abstract-phone) Abstract Phone MCP — wraps Abstract API Phone Validation… - Trust score: 83/100 (high trust) - Change this week: +4 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-11-05 ## Components - remote · `gateway.pipeworx.io`: 79/100, [markdown](https://verifymcp.io/servers/pipeworx-io-abstract-phone/abstract-phone-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-abstract-phone/abstract-phone-mcp) - npm · `@pipeworx/mcp-abstract-phone`: 83/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-abstract-phone/pipeworx-mcp-abstract-phone.md), [page](https://verifymcp.io/servers/pipeworx-io-abstract-phone/pipeworx-mcp-abstract-phone) ## Channel facts - Registry: `npm` - Package: `@pipeworx/mcp-abstract-phone` - Version: `0.2.1` - Transport: `stdio` ## Trust breakdown 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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-11-05. - **Supply Chain Security**: 100/100 - No malware found by supply-chain analysis. - No known CVEs affecting this package version or its production dependencies. - No install/post-install scripts declared. - No production dependencies, so there is no dependency health to assess. - **Provenance & Transparency**: 97/100 - Source repository is publicly reachable at the declared URL. - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-abstract-phone). - Clear OSI-approved license (MIT). - Actively maintained (last published 5 days ago). - Disclosure check failed: no security disclosure policy was found in the source repository. - **Schema Quality & AI Usability**: 66/100 - AI-judged instruction clarity (good). - Context-footprint check failed: tool/resource definitions use about 251 tokens (~251/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 23/100 - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 100/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 100% of tool parameters carry a description. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation. - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. ## Install ### How do I install the Abstract Phone MCP server? Abstract Phone runs locally as an npm package, launched with npx -y @pipeworx/mcp-abstract-phone. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation. ### Claude ```bash claude mcp add pipeworx-io-abstract-phone -- npx -y @pipeworx/mcp-abstract-phone ``` ### Cursor ```json { "mcpServers": { "pipeworx-io-abstract-phone": { "command": "npx", "args": [ "-y", "@pipeworx/mcp-abstract-phone" ] } } } ``` ### VS Code ```json { "servers": { "pipeworx-io-abstract-phone": { "command": "npx", "args": [ "-y", "@pipeworx/mcp-abstract-phone" ] } } } ``` ### Codex ```bash codex mcp add pipeworx-io-abstract-phone -- npx -y @pipeworx/mcp-abstract-phone ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "pipeworx-io-abstract-phone": { "type": "local", "command": [ "npx", "-y", "@pipeworx/mcp-abstract-phone" ], "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add pipeworx-io-abstract-phone --command npx --arg -y --arg @pipeworx/mcp-abstract-phone ``` ### Hermes ```yaml mcp_servers: pipeworx-io-abstract-phone: command: "npx" args: ["-y", "@pipeworx/mcp-abstract-phone"] ``` ### Netclaw ```json { "McpServers": { "pipeworx-io-abstract-phone": { "Transport": "stdio", "Command": "npx", "Arguments": [ "-y", "@pipeworx/mcp-abstract-phone" ] } } } ``` ### Vellum ```bash assistant mcp add pipeworx-io-abstract-phone -t stdio -c npx -a -y @pipeworx/mcp-abstract-phone ``` ### Other ```json { "mcpServers": { "pipeworx-io-abstract-phone": { "command": "npx", "args": [ "-y", "@pipeworx/mcp-abstract-phone" ] } } } ``` ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-11-05 (score 83, +1) No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-11-03 (score 82, +1) No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-11-01 (score 81, +1) No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-30 (score 80, +1) - [functional] Package version: 0.2.0 → 0.2.1 ### 2026-10-29 (score 79) First indexed and scored. ## MCP tools (1) ### `abstractphone_validate` (~198 tokens) Validate and enrich a phone number: returns whether it is valid, international/national formats, carrier, line type (mobile/landline/voip), and country/location. Example: abstractphone_validate({ phone: "14152007986", _apiKey: "your-key" }) Input parameters: - `_apiKey` (string, required): Abstract API key for the Phone Validation API. Get one free at https://www.abstractapi.com/api/phone-validation-api (key is on the dashboard). - `country` (string): Optional ISO 3166-1 alpha-2 country code (e.g. "US", "GB") to help interpret a number given without a country code. - `phone` (string, required): Phone number to validate. Include the country code for best results, e.g. "14152007986" or "+14152007986". If omitted, pass `country` (ISO2) so the number can be interpreted. ## Diagnostics Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-abstract-phone/pipeworx-mcp-abstract-phone#diagnostics ## Score history - 2026-11-05: 83 - 2026-11-04: 82 - 2026-11-03: 82 - 2026-11-02: 81 - 2026-11-01: 81 - 2026-10-31: 80 - 2026-10-30: 80 - 2026-10-29: 79 ## Common questions ### What is the Abstract Phone MCP server? Abstract Phone is an MCP server listed in the public MCP registry as io.github.pipeworx-io/abstract-phone. Abstract Phone MCP, wraps Abstract API Phone Validation… This page covers its npm package (@pipeworx/mcp-abstract-phone). ### Is the Abstract Phone MCP server safe to use? Abstract Phone 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 Abstract Phone MCP server expose? Abstract Phone exposes 1 tool: abstractphone_validate. Their descriptions and schemas cost roughly 198 tokens of context every time the server is loaded. ### Is the Abstract Phone MCP server still maintained? Abstract Phone 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 Abstract Phone MCP server under? Abstract Phone 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 Abstract Phone MCP server? VerifyMCP ran 16 checks on Abstract Phone, 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. ## Links - npm package: https://www.npmjs.com/package/@pipeworx/mcp-abstract-phone - Socket report: https://socket.dev/npm/package/@pipeworx/mcp-abstract-phone - Repository: https://github.com/pipeworx-io/mcp-abstract-phone - Website: https://pipeworx.io/packs/abstract-phone - Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-abstract-phone/pipeworx-mcp-abstract-phone.xml - Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-abstract-phone/pipeworx-mcp-abstract-phone/changelog.json - Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-abstract-phone/pipeworx-mcp-abstract-phone.json - HTML version of this page: https://verifymcp.io/servers/pipeworx-io-abstract-phone/pipeworx-mcp-abstract-phone