SMS Verification Number Registry
Pricing
Pay per usage
Sort and check SMS verification numbers by project, market and team: expiry status and duplicate numbers.
Pricing
Pay per usage
Rating
0.0
(0)
Developer
Nalinee Rattanaporn
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
15 days ago
Last modified
Categories
Features
Share
Connect the SMS Verification Number Registry Actor to an AI application through the Apify MCP server. MCP clients with OAuth support sign you in to Apify without an API token.
{ "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,nalineerattanaporn/sms-verification-number-registry" } }}Add the configuration above to your project's .mcp.json file for Claude Code, then run /mcp in Claude Code to sign in to Apify. It connects to the hosted Apify MCP server with the SMS Verification Number Registry Actor already loaded. Clients without OAuth support can authenticate with an Authorization: Bearer header carrying an API token from API & Integrations in Apify Console.
For other MCP clients, get a client-specific configuration with the SMS Verification Number Registry Actor preconfigured at https://mcp.apify.com/?tools=fetch-actor-details,nalineerattanaporn/sms-verification-number-registry.
You can connect to the Apify MCP server using an MCP client that supports Streamable HTTP.
If you want to learn more about our Apify MCP implementation, check out our MCP documentation. To learn more about the Model Context Protocol in general, refer to the official MCP documentation or read our blog post.