Tor Exit Node

What it grounds

Ground agents in a daily-updated Tor exit-node list so access and risk decisions rest on verifiable network intel, not assumptions.

Ways to ground with it

Verify hosts and IPs

Give an agent Tor Exit Node so it resolves and checks hosts against real data before acting, rather than assuming — grounding network reasoning in fact.

Ground an ops assistant

Wire tordetect into an operations agent so its answers about connectivity and infrastructure rest on live lookups it can cite.

Traceable checks

Each result the agent relies on carries Tor Exit Node as its source, keeping the reasoning auditable.

Connect over MCP

Point your agent framework at the VerveContext endpoint. Every enabled source — this one included — becomes a tool the model can call. No per-source plumbing.

context.json

{
  "mcpServers": {
    "vervecontext": {
      "url": "https://api.vervecontext.com/v1/mcp",
      "headers": { "x-api-key": "vc_live_••••" }
    }
  }
}

# “tordetect” is now a tool your agent can call

Facts your agent can cite

Each call returns structured fields your agent can read — and trace back to this source.

ipAddress
isTor
ipDetails
parsed

Tor Exit Node, answered

How to ground an agent in it over MCP.

How do I give my agent Tor Exit Node?

Enable it on VerveContext and point your agent framework at the VerveContext MCP endpoint. Tor Exit Node then appears to the model as a tool named tordetect, which it calls when a task needs it — no per-source plumbing.

Which agents and frameworks can use it?

Any MCP client — Claude, Cursor, LangChain, and custom agents all speak the Model Context Protocol. Tor Exit Node is exposed as a standard tool, so nothing source-specific is required.

Can the agent cite Tor Exit Node?

Yes. Tor Exit Node is verifiable factual grounding — every value the agent pulls can carry Tor Exit Node as its source, so a person (or another system) can trace where the fact came from.

How many credits does a Tor Exit Node call cost?

Each call costs 1 credit. Scoped keys let you grant an agent only the sources it should reach, and usage logs show exactly what was pulled to ground each answer.

How current is the data?

Tor Exit Node is served live from APIVerve's production data engine and pulled at the moment the agent calls it, so answers reflect the world now rather than the model's training cutoff.

Where does the data come from, and what shows on my bill?

VerveContext runs on APIVerve, our production data engine; Tor Exit Node is one of 300+ sources on the same key. Invoices and card statements show APIVERVE.

Ground alongside

Browse all sources

Verify hosts and IPs

Ground an ops assistant

Traceable checks

Tor Exit Node, answered

Ground your agents in Tor Exit Node. Connect over MCP, enable the source, and every answer carries its receipts.

Scaling up?