Phone
Server Details
Phone number validation MCP.
Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-phone
- GitHub Stars
- 0
- Server Listing
- mcp-phone
TDQS
Scored across 33 tools
The descriptions are extremely detailed and most tools target distinct actions, but there is real overlap: ask_pipeworx, ask_pipeworx_beta (explicitly identical to stable right now), ask_pipeworx_grounded, and deep_research all route questions to the same 5,961-tool catalog, and discover_tools vs suggest_questions both serve 'what can I look up'. An agent must read carefully to pick correctly.
Everything is snake_case, and domain prefixes (ask_pipeworx_*, polymarket_*, pipeworx_*) are used consistently. However conventions are mixed: many verb_noun tools (validate_claim, resolve_entity, compare_entities) sit alongside bare verbs (remember, recall, forget, subscribe, unsubscribe) and noun-phrase tools (recent_alerts, ai_visibility_check), so no single predictable pattern.
33 tools is heavy and crosses the rubric's 25+ threshold for an over-large surface. While the platform spans many domains (research, betting, memory, subscriptions, phone utilities), the ask_*/research family and discovery tools in particular add redundancy that bloats the set.
Lifecycles are well covered: memory (remember/recall/forget), subscriptions (subscribe/list/unsubscribe/recent_alerts), and research (question routing, grounded, deep, entity resolution/profile/comparison/validation) form complete flows with explicit fallbacks. Minor gaps and a mismatched server name ('Phone' for a broad data platform with only two phone tools) are the main issues.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- Changed
bet_research2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "market": "when-will-bitcoin-hit-150k" - }, - { - "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k" - } -]New value: +[ + { + "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination" + }, + { + "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination" + } +] - changed
Input schema / properties / market / descriptionPrevious value: -"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
2 tool updates
- Changed
bet_research2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "market": "will-bitcoin-reach-100k-in-july-2026" - }, - { - "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026" - } -]New value: +[ + { + "market": "when-will-bitcoin-hit-150k" + }, + { + "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k" + } +] - changed
Input schema / properties / market / descriptionPrevious value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
- Changed
polymarket_kalshi_spread2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "topic": "fed" - }, - { - "topic": "btc" - } -]New value: +[ + { + "topic": "fed" + }, + { + "topic": "btc" + }, + { + "topic": "bitcoin" + }, + { + "topic": "fed rate decision" + } +] - changed
Input schema / properties / topic / descriptionPrevious value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."
Related MCP Connectors
Abstract Phone MCP — wraps Abstract API Phone Validation
EU VIES VAT-number validation MCP (European Commission).
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables validating phone numbers (validity, line type, carrier, region, country, and canonical formats) and checking Veriphone API credits and quota through MCP tools.MIT
- AlicenseAqualityCmaintenanceEmail validation MCP server using MailboxValidator API to determine validity of an email address.334 npm1MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for provisioning dedicated real-SIM US phone numbers, receiving inbound SMS, and extracting OTP codes. Built for AI agents automating phone verification workflows.17 npm1MIT
- FlicenseCqualityDmaintenanceMCP server for accessing Sms Verify3 API to send numeric verification codes and estimate costs.1-
Glama MCP Gateway
Add one secure layer between your agents and this server.