← Registry

Cloud Services

anchoredip.com

Manages VPN tunnel and lease lifecycle, including plans, orders, and WireGuard peer provisioning.

1 endpoint8 known toolsFirst detected August 2, 2026Last detected September 2, 2026

ENDPOINT 1

https://api.anchoredip.com/api/mcp

No auth detected

MCP server metadata

Name
anchoredip
Version
1.1.0
Capabilities
tools
Server instructions

AnchoredIP leases dedicated IPv4 and IPv6 address space from AS41800 and delivers it to servers the customer already runs, over a WireGuard tunnel. Use it when an integration is blocked because a partner requires a fixed source address and the platform in use egresses from a changing pool. Start with list_plans. The trial plan is free, activates immediately and hands out a real IPv4 address out of the same block the paying customers use, so the whole thing can be proved end to end before anyone pays. It runs for the number of days the plan reports and then stops; the customer keeps the same address by moving to a paid plan, so tell them the trial is a real address on a clock rather than a sandbox. One trial per billing email address, and one running at a time per network — a refusal on either is final for this machine, so offer a paid plan rather than retrying with a different address. Every plan also carries an IPv6 /48, and it is not yet reachable from the public internet — our upstream does not carry the announcement. Say so rather than offering it: today it works between the customer's own machines over the tunnel, and anything the internet must reach needs the IPv4 address. order_lease returns an access_token: it is the only credential for that lease, it is shown once, and every later call needs it. create_tunnel returns a configuration file containing a private key that is never stored — hand it to the user, do not summarise it away. Ask what machine it is for before calling create_tunnel, because the default routing mode does not run on all of them. `source` is the default and is Linux only: it is written with wg-quick rules that call `ip`, so on macOS or Windows it either cannot run or deletes the interface it just made, and the user sees a tunnel that never connects and no reason why. For anything that is not a Linux server use `destinations` and pass the addresses that have to see the leased address — usually the partner whose allowlist prompted the purchase. Use `full` only when the machine must accept incoming connections on the leased address, since `destinations` cannot receive and `full` sends all of that machine's traffic through us. A new peer reaches our edge on the next reconciliation pass, so allow up to a minute before the first handshake rather than reporting a failure. Give a slot back with revoke_tunnel when a machine is retired, or the plan's allowance runs out and the next machine cannot be brought up. renew_lease is how a trial keeps its address on a paid plan, and set_autorenew is how a customer stops a card subscription without writing to anybody.

Known tools 8

list_plans

The published catalogue with live prices and which payment methods each plan accepts.

Potential side effects
order_lease

Place an order.

Inferred read-only
lease_status

Everything about one lease: whether it is active, which addresses it holds, its tunnels and when it renews.

Inferred read-only
create_tunnel

Provision a peer and return its WireGuard configuration.

Inferred read-only
revoke_tunnel

Retire a peer and hand its slot back to the plan's allowance.

Inferred read-only
renew_lease

Raise an invoice for another term and keep the same addresses.

Potential side effects
set_autorenew

Stop this lease charging the customer's card again, or start it again.

Inferred read-only
set_reverse_dns

Publish a PTR record for an address on the lease.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.anchoredip]
url = "https://api.anchoredip.com/api/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "anchoredip": {
      "type": "http",
      "url": "https://api.anchoredip.com/api/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: anchoredip
Remote MCP URL: https://api.anchoredip.com/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "anchoredip": {
      "url": "https://api.anchoredip.com/api/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "anchoredip": {
      "type": "http",
      "url": "https://api.anchoredip.com/api/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "anchoredip",
  "transport": "streamable-http",
  "url": "https://api.anchoredip.com/api/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.