Scry MCP server
ai.tunnelmind/scrytunnelmind.aistreamable-httpv0.5.0Scanned
Free IPv4 lookups against a distributed attacker-observation corpus.
12 tools: 9 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
9 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Scry MCP server can do
The Scry MCP server is published by tunnelmind.ai, a domain the MCP Registry verified. It has 12 tools. It can create or change data (9 tools: scry_check_bulk, scry_top, scry_timeseries, scry_asn and 5 more), but cannot delete data. 3 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 10, 2026, version 0.5.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
12 tools
Changes things 9Claude Code: ask
scry_asnRoll-up of corpus activity for a single ASN — observation count, distinct source IPs, actor count, scanner count, high-confidence actor count, and per-protocol breakdown.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Roll-up of corpus activity for a single ASN — observation count, distinct source IPs, actor count, scanner count, high-confidence actor count, and per-protocol breakdown.
scry_campaignSingle campaign detail by id (format: c[0-9a-f]{15}).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Single campaign detail by id (format: c[0-9a-f]{15}).
scry_campaignsActive threat campaigns — coordinated attacker activity that exceeds the noise floor.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Active threat campaigns — coordinated attacker activity that exceeds the noise floor. ≥5 distinct actors, ≥3 ASNs, ≤5 destination ports, ≥1h history.
scry_check_bulkLook up many IPv4 addresses in one request.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Look up many IPv4 addresses in one request. Up to 100 IPs per call. Same per-IP shape as scry_check, keyed by IP.
scry_countryRoll-up of corpus activity by ISO country code.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Roll-up of corpus activity by ISO country code. Same shape as scry_asn.
scry_recentRecent observations feed — aggregated by source IP within a time window.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Recent observations feed — aggregated by source IP within a time window. Cursor-paginated via since_ms.
scry_timeseriesBucketed observation counts over time.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Bucketed observation counts over time. Detect bursts, plot trends, sanity-check whether attacker activity is rising or falling.
scry_toolSingle tool detail by 16-char hex id from scry_tools.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Single tool detail by 16-char hex id from scry_tools.
scry_topTop-N source dimensions over a time window.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Top-N source dimensions over a time window. Useful for situational awareness — 'where is the noise coming from right now?'
Only reads 3Show 3 read-only tools
scry_checkReturns Scry's corpus knowledge for a single IPv4 address: when it was first/last observed, observation count, protocols and ports targeted, ASN, country, category (actor/scanner/n…No findings
Why it is in this group
- The description's first verb is "return": a word for reading.
Description, as the server wrote it Returns Scry's corpus knowledge for a single IPv4 address: when it was first/last observed, observation count, protocols and ports targeted, ASN, country, category (actor/scanner/not_observed), and confidence_bucket (low/medium/high). Use when an agent needs IP triage, hostility assessment, or risk signaling. Do NOT use for raw payloads (never exposed) or IPv6 (corpus is v4-only at v0.1).
scry_statsReturns aggregate Scry corpus telemetry: total observation count, distinct source IPs, first/last observation timestamps, last-24h activity, and per-protocol breakdowns.No findings
Why it is in this group
- The description's first verb is "return": a word for reading.
Description, as the server wrote it Returns aggregate Scry corpus telemetry: total observation count, distinct source IPs, first/last observation timestamps, last-24h activity, and per-protocol breakdowns. Useful as a liveness/density check before issuing per-IP queries — lets an agent decide whether the corpus has enough data to be authoritative. Use this tool when: - An agent is planning a multi-step investigation and wants to know if Scry has corpus density worth querying. - You want a 'corpus health' signal in a dashboard or report. Do NOT use this tool when: - You want details about a specific IP — use `scry_check`. - You want sensor fleet size or node identities — never exposed at any tier. Inputs: none. Returns: total_observations, distinct_source_ips, first_seen_ms, last_seen_ms, observations_last_24h, distinct_source_ips_last_24h, by_protocol, as_of_ms. Cost: free, anonymous, rate-limited. Latency: <100ms typical.
scry_toolsList detected attack tools — (protocol, payload, path) tuples sent by 3+ distinct source IPs.No findings
Why it is in this group
- The description's first verb is "list": a word for reading.
Description, as the server wrote it List detected attack tools — (protocol, payload, path) tuples sent by 3+ distinct source IPs. Aggregate metadata only; never lists member actors.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:28 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 9
- Protocol version
- 2025-03-26
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 9 tools that change things (9 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.tunnelmind.ai/mcp: tools/list returned 12 tools to an anonymous client, including scry_check_bulk (write), scry_top (write), scry_timeseries (write), scry_asn (write), scry_country (write) and 4 more
Posture changes
- Nov 13, 2026
- HTTP status of an anonymous initialize: 530 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 9
- Protocol version: none to 2025-03-26
- Nov 6, 2026
- HTTP status of an anonymous initialize: 200 to 530
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 9 to 0
- Protocol version: 2025-03-26 to none
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. HTTP status of an anonymous initialize: 530 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 9 (and 1 more).View diff
- HTTP status of an anonymous initialize: 530 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 9
- Protocol version: none to 2025-03-26
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 530; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 9 -> 0 (and 1 more).View diff
- HTTP status of an anonymous initialize: 200 to 530
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 9 to 0
- Protocol version: 2025-03-26 to none
Install
Pinned to version 0.5.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http scry https://mcp.tunnelmind.ai/mcpclaude mcp add --transport http scry https://mcp.tunnelmind.ai/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__scry__scry_stats",
"mcp__scry__scry_check",
"mcp__scry__scry_tools"
],
"ask": [
"mcp__scry__scry_check_bulk",
"mcp__scry__scry_top",
"mcp__scry__scry_timeseries",
"mcp__scry__scry_asn",
"mcp__scry__scry_country",
"mcp__scry__scry_tool",
"mcp__scry__scry_campaigns",
"mcp__scry__scry_campaign",
"mcp__scry__scry_recent"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as scry. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/ai.tunnelmind/scry/verify?hash=d7ef7981b5e1a1910579a93426a75602f2e770e47e976bea6d31e0d586b8b79f" | jq -e '.changed == false'Pinned hash d7ef7981b5e1, from Nov 10, 2026, 04:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/ai.tunnelmind/scry/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/ai.tunnelmind/scry)Source: MCP Registry · repository. Synced Oct 21, 2026, 17:43 UTC.
Scry MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Scry MCP server safe?
- No scan can promise that. What its definitions show: 12 tools, 9 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Scry MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Scry MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Scry MCP server have?
- 12 tools: 9 write, 3 read. scry_check_bulk, scry_top, scry_timeseries, scry_asn, scry_country, scry_tool, scry_campaigns, scry_campaign and 4 more.
Does the Scry MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Scry MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Scry MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.