Ip2Proxy
IP2Proxy is a proxy detection web service that identifies anonymous proxies, VPNs, TOR exit nodes, search engine robots, and residential proxies by IP address.
Verdict
Common use cases
- Flag VPN traffic in fraud investigations
- Audit IP sources before firewall changes
- Verify user locations during account reviews
- Detect Tor usage in abuse reports
- Screen signup IPs for bot prevention
Integration
- Vendor
- Ip2Proxy
- Category
- other
- Auth
- API_KEY
- Tools
- 1
- Composio slug
ip2proxy
Tools
- Check Proxy Status of an IP
Tool to check if an IP address is a proxy. Use after obtaining an IP to detect proxy, VPN, or Tor status.
Setup
Setup guide
- 11. Open your Switchy workspace and navigate to Settings > Integrations. 2. Find Ip2Proxy in the MCP directory and click Connect. 3. You'll be prompted to enter an API key — obtain this by signing up at ip2proxy.com and copying the key from your account dashboard. 4. Paste the key into Switchy and click Authorize. 5. Switchy confirms the connection with a green checkmark. 6. Open any Space and type '@Ip2Proxy check proxy status of 203.0.113.45' to test. 7. The MCP returns proxy type, country, provider, and threat level within seconds. 8. If the test fails, verify your API key is active and your subscription tier supports the query volume.
What teammates see: by default, memories from Ip2Proxy are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Check Suspicious Login IP
@Ip2Proxy check proxy status of 198.51.100.22 and tell me if this IP is flagged as high-risk or associated with known proxy providers.
Audit Traffic Source
@Ip2Proxy check proxy status of 192.0.2.88 and summarize whether it's a datacenter proxy, residential VPN, or clean IP.
Investigate Fraud Report
@Ip2Proxy check proxy status of 203.0.113.17 and indicate if it's a Tor exit node or commercial VPN endpoint.
Validate Signup IP
@Ip2Proxy check proxy status of 198.51.100.5 and report the threat level plus any known proxy provider associations.
Review API Access Request
@Ip2Proxy check proxy status of 192.0.2.44 and confirm if this is a residential IP or a datacenter proxy service.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Ip2Proxy check if 203.0.113.45 is a proxy or VPN connection
The IP address 203.0.113.45 is flagged as a datacenter proxy. Detection details: proxy type is DCH (datacenter/hosting), threat level is low, provider is identified as DigitalOcean Singapore. The IP is not associated with VPN or Tor exit nodes. This suggests the connection originates from cloud infrastructure rather than a residential ISP.
This read-only check is useful for fraud detection or access control decisions. Requires an API key with sufficient query credits. Detection accuracy depends on Ip2Proxy's database freshness — newly provisioned proxy IPs may not be flagged immediately. No side effects; purely informational.
@Ip2Proxy verify the last 5 login IPs from our access logs and flag any that route through anonymizers
Analyzed 5 IP addresses from your access logs. Results: 198.51.100.22 (clean, residential ISP), 203.0.113.67 (VPN detected, provider NordVPN), 192.0.2.101 (clean, corporate network), 198.51.100.88 (Tor exit node flagged), 203.0.113.12 (clean, mobile carrier). Two IPs show anonymization: one VPN, one Tor. Consider reviewing associated sessions for policy compliance.
This synthesis example pairs the MCP's detection capability with AI reasoning to triage multiple IPs. Each lookup consumes one API credit, so batch queries can deplete quotas quickly. The MCP returns structured data; the AI interprets threat levels and suggests next steps. No write actions occur.
@Ip2Proxy is 192.0.2.50 coming from a residential connection or a proxy service?
The IP address 192.0.2.50 is classified as a residential connection. Detection shows: proxy type is negative (not a proxy), ISP is Comcast Cable Communications, usage type is fixed-line ISP. No VPN, datacenter, or Tor indicators present. This suggests a legitimate home or small-office internet connection.
Demonstrates the MCP's ability to confirm clean IPs, not just flag proxies. Useful for allowlisting trusted sources or reducing false positives in security workflows. API key must have active credits. Detection relies on Ip2Proxy's proprietary database; edge cases like residential proxies may not always be caught.
Use-case deep-dives
When one-tool proxy checks make sense for signup flows
A 6-person B2B SaaS team sees 40-60 trial signups weekly and wants to flag suspicious accounts before they hit the CRM. The Ip2Proxy MCP works here because the decision is binary: proxy detected or not. You wire it into your onboarding Slack channel so the team sees flagged IPs in real time during morning standup. The single-tool constraint is fine when you're checking one IP at a time and the action is manual review, not automated blocking. If you're processing hundreds of signups daily or need geolocation data alongside proxy status, you'll outgrow this fast and want a fuller IP intelligence stack. For small-team triage where a human makes the call, this MCP gives you the signal without the overhead.
Spotting VPN users in customer support queues
A 3-person support team for a regional fintech app gets 15-20 tickets daily, mostly password resets and account lockouts. They use the Ip2Proxy MCP to check if the requester's IP is a VPN or Tor exit node before escalating to engineering. The workflow is simple: paste the IP from the ticket metadata into Switchy, run the check, and decide whether to ask for secondary verification. This works because the volume is low and the team already triages manually. The MCP's API key auth means one shared credential across the workspace. If your support load exceeds 50 tickets daily or you need automated decisioning, you'll want a tool that integrates directly with your helpdesk. For human-in-the-loop verification at small scale, this is the right call.
Flagging anonymous posters in small forums
A 4-person team runs a niche community forum with 200 active users and sees occasional spam waves from proxy networks. They use the Ip2Proxy MCP during weekly moderation sweeps to check IPs of flagged accounts before issuing bans. The single-tool design fits because they're not building real-time blocking; they're reviewing a batch of 10-15 suspicious accounts and making judgment calls. The MCP surfaces proxy status in seconds, and the team cross-references it with post history in their moderation dashboard. If your community scales past 1,000 active users or you need automated rate-limiting, this manual approach breaks down. For small forums where moderation is a weekly ritual, not a 24/7 operation, this MCP delivers the data you need without overengineering the stack.
Frequently asked
What does the Ip2Proxy MCP do in Switchy?
It checks whether an IP address is a proxy, VPN, or Tor exit node. You feed it an IP and it returns detection data from Ip2Proxy's database. Useful for fraud prevention workflows, security audits, or validating traffic sources before taking action on suspicious activity.
Do I need an Ip2Proxy account to use this MCP?
Yes. You need an Ip2Proxy API key, which means signing up for their service and choosing a plan. The MCP uses API_KEY authentication, so you paste your key into Switchy's connection settings. No OAuth dance—just the key from your Ip2Proxy dashboard.
Can it block proxies automatically or just detect them?
It only detects. The MCP returns proxy status data; it doesn't enforce blocks or firewall rules. If you want to act on the result—like flagging a user or rejecting a request—you build that logic in your Switchy workflow using the detection output.
How is this different from calling Ip2Proxy's API directly?
It's a convenience wrapper. You skip writing HTTP client code and handling API errors yourself. The MCP exposes one tool that maps cleanly to Ip2Proxy's lookup endpoint. If you already have API integration code, you don't need this. If you're building workflows in Switchy, it saves setup time.
Who on the team should connect the Ip2Proxy MCP?
Whoever owns your fraud prevention or security tooling. They'll have the Ip2Proxy account and understand which IPs to check. Once connected, any team member can call the tool in Switchy workflows, but the person who connects it controls the API key and usage limits.