How do I install Scry?

Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Scry need an API key?

No required environment variable is listed on this record.

Scry

by ai.tunnelmind

Free IPv4 lookups against a distributed attacker-observation corpus.

Power your agent

Add this server

The publisher's own URL. Not a PlugMCP endpoint.

Server URL

https://mcp.tunnelmind.ai/mcp

Provider

Add in Claude

Claude opens with the name and URL filled in. You still confirm it there.

Claude Code

claude mcp add --transport http ai.tunnelmind-scry https://mcp.tunnelmind.ai/mcp

Run in a terminal.

Claude Desktop

{
  "mcpServers": {
    "ai.tunnelmind-scry": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.tunnelmind.ai/mcp"
      ]
    }
  }
}

claude_desktop_config.json

Step-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Related MCP

Related skills

View all

A
agent-walletGive the AI agent its own EVM wallet with admin-controlled policies the agent CANNOT bypass even under prompt injection. Encrypted keystore (AES-256-GCM, scrypt KDF), policy file the agent has no tool

Questions

How do I install Scry?: Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
Does Scry need an API key?: No required environment variable is listed on this record.
What transport does Scry use?: Scry is reached over HTTP.
When was Scry last checked?: Last checked 2026-10-16. Free IPv4 lookups against a distributed attacker-observation corpus.

scry-mcp

MCP (Model Context Protocol) server for the Scry corpus. Wraps the scry-api public endpoints as agent-callable tools.

Hosted at mcp.tunnelmind.ai. MCP spec version 2025-03-26. Streamable HTTP transport.

Tools (v0.1)

Tool	Wraps	Tier
`scry_check`	`GET /v1/check/{ip}`	Free

Future tools (deferred to defender tier; need ATAP attestation):

scry_watch — subscribe to state changes for an IP/domain
scry_actor — full actor profile
scry_campaign — campaign detail

Wire protocol

POST https://mcp.tunnelmind.ai/mcp
Content-Type: application/json

{"jsonrpc":"2.0","id":1,"method":"initialize"}

Methods:

initialize — handshake, returns { protocolVersion, capabilities, serverInfo }
notifications/initialized — client → server notification (returns 204)
tools/list — returns { tools: [...] }
tools/call — { name, arguments } → { content: [{ type: "text", text }] }
ping — returns {}

Discovery:

GET https://mcp.tunnelmind.ai/
→ { service, version, protocol, transport, endpoint, tools }

Layout

src/
  worker.js   transport (JSON-RPC 2.0 over POST /mcp)
  tools.js    tool definitions + handlers
test/
  tools.test.js   unit tests for tool registry

Setup

npm test
npx wrangler deploy

No bindings, no secrets — this Worker is a thin proxy with no state.