Veriphone MCP server
4 operations0 webhooks
Phone number validation API for verifying numbers, listing supported countries, checking credit usage, and fetching example numbers.
Try Veriphone with your agent
Connect Veriphone, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.
Using Corsair, show me what you can do in Veriphone on my account, then run one read-only example and show me the result.
Veriphone tools and triggers
Tools are what your agent can do in Veriphone through Corsair's MCP server. Triggers are the Veriphone events a routine can start from.
Coverage
- CoverageRead-only
List countries where Current (mode=current) lookups are available
coverage
Credits
- CreditsRead-only
Get the account credit balance and usage by lookup mode
credits
Get Example Phone Number
- Get Example Phone NumberRead-only
Tool to retrieve an example phone number for a specified country and type. Use after confirming the country code. Example: 'Get an example mobile number for US'.
getExamplePhoneNumber
Verify Phone Number
- Verify Phone NumberWrite
Tool to verify if a phone number is valid. Use when you need to confirm formatting, region, and carrier details.
verifyPhoneNumber
Connect Veriphone to Claude, ChatGPT or Cursor
- 1
Connect Veriphone in Corsair
Add your Veriphone API key once in Corsair. Corsair stores the credential encrypted and makes the Veriphone API calls for your agent, so it never goes into a prompt or a config file. Connect Veriphone
If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Veriphone. On a ChatGPT personal plan, connect Veriphone here first.
- 2
Add Corsair's MCP server to your agent
Every client uses the same address:
https://mcp.corsair.dev/mcpOpen Customize → Connectors → Add custom connector, paste the address, then select Connect.Add a custom MCP server with the address and choose OAuth. Personal plans get read tools only.Add to CursorOr add this to~/.cursor/mcp.json. Cursor opens Corsair to sign in the first time it connects.{ "mcpServers": { "corsair": { "url": "https://mcp.corsair.dev/mcp" } } }Run this, then run/mcpin Claude Code to sign in.claude mcp add --transport http corsair https://mcp.corsair.dev/mcpCodex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client
- 3
Sign in and choose what needs your approval
Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. None of Veriphone's operations are destructive, so in the default Cautious mode they all run right away. Strict mode asks before each of its 1 write, and Read mode allows reads only.
FAQ
Install corsair and @corsair-dev/veriphone, add the Veriphone plugin, and connect with an API key. Then call methods like corsair.veriphone.api.coverage() from your app. Corsair keeps each tenant isolated.
Yes. Veriphone requires an API key from your Veriphone account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.
Yes. One Corsair client can hit Veriphone, GitHub, Notion, Stripe, and the rest. Trigger Veriphone from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.
Teams use Corsair for phone number validation api for verifying numbers, listing supported countries, checking credit usage, and fetching example numbers. Common builds include sync jobs, admin tooling, and agents that call Veriphone APIs from your backend.
The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Veriphone API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.
We maintain @corsair-dev/veriphone in the open repo. When Veriphone ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.
No. Corsair does not read your Veriphone data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Veriphone data on your behalf.
Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.
Yes. Put Veriphone on a link in Strict mode and every write waits for your approval, while destructive actions are refused. None of the Veriphone operations are destructive, so the default Cautious mode runs them all without asking. You can change a link's mode at hub.corsair.dev/me.