Tor Exit Node Skill

Overview

Tor Detect uses up-to-date exit node lists from the Tor network to verify if the specified IP address is actively being used as a Tor exit node. This is essential for services that wish to restrict access from anonymous sources or monitor traffic.

Live Test Tor Exit Node Skill Skill →

The tool

Once your client is connected to the VerveKit server, this appears in its tool list as TorExitNodeSkill. It is read-only and open-world — it fetches and never mutates anything on your side — so most clients call it without asking you to confirm.

Tool call

{
  "name": "TorExitNodeSkill",
  "arguments": {
    "ip": "185.189.183.143"
  }
}

You do not name the tool yourself; the model picks it. Asking about 185.189.183.143 in the terms this skill covers is enough for it to reach for TorExitNodeSkill on its own — naming it explicitly also works, and is the way to force the call.

Connecting

One server URL covers every skill in the catalog, including this one. Authorization is OAuth: the client opens a browser once, and there is no key to paste into a config file.

{
  "mcpServers": {
    "vervekit": {
      "url": "https://api.vervekit.com/v1/mcp"
    }
  }
}

Per-client setup — Claude, Cursor, VS Code, ChatGPT — is on the MCP setup page.

Arguments

These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made. Premium arguments are accepted on every plan but only take effect on plans that include them.

Argument	Type	Description
`ip`Required	string	The IP address to check against the Tor exit node list ip

What the model gets back

The result carries a structuredContent object matching the tool's declared outputSchema, so a client reads fields without parsing prose. status is "ok" and error is null on success; a null field means the value was not available for that input, not that the call failed.

Result

{
  "status": "ok",
  "error": null,
  "data": {
    "ipAddress": "185.189.183.143",
    "isTor": true,
    "ipDetails": {
      "country": "NL",
      "region": "ZH",
      "timezone": "Europe/Amsterdam"
    },
    "parsed": true,
    "asn": "AS215747",
    "asnName": "NUBACLOUD"
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Field	Type	Example	Description
`ipAddress`	string	`185.189.183.143`	The IP address being checked for Tor exit node status
`isTor`	boolean	`true`	Whether the IP is a known Tor exit node
`ipDetails`Premium	object	`{…}`	Detailed information about the IP geolocation and network
`ipDetails.country`Premium	string	`NL`	Two-letter ISO country code of IP location
`ipDetails.region`Premium	string	`ZH`	Region or state code of IP location within country
`ipDetails.timezone`Premium	string	`Europe/Amsterdam`	IANA timezone identifier for IP location
`parsed`	boolean	`true`	Whether the IP address was successfully parsed and validated
`asn`Premium	string	`AS215747`	Autonomous System Number announcing the IP (e.g., AS60729); null if unrouted
`asnName`Premium	string	`NUBACLOUD`	Registered name of that AS (e.g., TORSERVERS-NET), not always the company name

Failure modes

Errors come back as tool errors carrying a sentence the model can act on, not a bare status code. Error handling covers the full list.

Status	What it means
`400` / `422`	The arguments did not validate. The message names the offending one.
`401`	The OAuth session is invalid or expired — reconnect the server.
`403`	Blocked by a key restriction or an IP allow-list. Never a bad identity.
`404`	This skill is not part of VerveKit. Check the catalog.
`429`	Out of credits, or a brief rate limit. The message tells them apart.

A call costs 10 credits each time the tool actually runs; a model that reasons about the tool without calling it costs nothing.

Use cases

Account Registration Screening: To stop automated credential creation, signup workflows check visitor IPs and require extra verification for sessions originating from exit nodes.
Payment Fraud Prevention: Flag suspicious orders before credit card processing by reviewing whether checkout traffic routes through anonymized exit addresses.
Digital Rights Enforcement: Streaming services prevent geographic licensing evasion during media playback by blocking access requests sent from confirmed exit relays.
Session Anomaly Detection: When an established user logs in from a Tor exit node, identity systems trigger multi-factor authentication to prevent session hijacking.

Other ways to use Tor Exit Node Skill

Set up Tor Exit Node Skill on VerveKit, or reach the same source a different way. Your VerveKit account and credits work on all of them — one key, one balance.

Call it as a REST APIOne HTTPS endpoint and an x-api-key header, with SDKs for Node, Python and .NET.APIVerve →Reference →

Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheets →Reference →

Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.VerveContext →Reference →

Pages that use this skill:

Block fake signupsGuides