Ai Vpn Mcp

Created By
Alexjef9 months ago
Allow your agent to access multiple geolocation, API and catalogs by changing its IP.
Overview

What is Ai Vpn Mcp?

Ai Vpn Mcp is an AI-powered VPN orchestration layer that allows agents to access multiple geolocations, APIs, and catalogs by changing their IP addresses seamlessly.

How to use Ai Vpn Mcp?

To use Ai Vpn Mcp, install the software on your system, configure the mcp.json file with your directory path, and launch the AI agent CLI to discover the MCP automatically.

Key features of Ai Vpn Mcp?

  • On-demand provisioning of VPN tunnels
  • Control over tunnel lifecycle (start/stop/status)
  • Traffic routing through global endpoints
  • Real-time connection health monitoring

Use cases of Ai Vpn Mcp?

  1. Accessing region-restricted content
  2. Scraping data from websites with geolocation restrictions
  3. Enhancing privacy and security for AI agents

FAQ from Ai Vpn Mcp?

  • Is Ai Vpn Mcp easy to install?

Yes! Installation is straightforward with provided packages for various operating systems.

  • Can I use Ai Vpn Mcp for multiple users?

Yes! It can be configured to support multiple agents accessing different geolocations.

  • What are the prerequisites for installation?

You need Python 3.9+, UV package manager, and WireGuard installed on your system.

Server Config

{
  "mcpServers": {
    "AI VPN": {
      "command": "uv",
      "args": [
        "--directory",
        "/opt/ai-vpn-mcp",
        "run",
        "--with",
        "fastmcp",
        "fastmcp",
        "run",
        "server.py"
      ],
      "env": {},
      "transport": "stdio"
    }
  }
}
Project Info
Created At
9 months ago
Updated At
9 months ago
Author Name
Alexjef
Star
-
Language
-
License
-

Recommend Servers

View All
Payai X402 Tools

6 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago