MCP.Market

Scry MCP server

online · 100% uptime
by tunnelmind.ai·ai.tunnelmind/scry·v0.5.0
No reviews yet

Free IPv4 lookups against a distributed attacker-observation corpus.

B72/100grade B
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
B72/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Scry yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Scry tools (12)

write = sends, deletes, buys or posts
  • scry_asnFree

    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_campaignFree

    Single campaign detail by id (format: c[0-9a-f]{15}).

  • scry_campaignsFree

    Active threat campaigns — coordinated attacker activity that exceeds the noise floor. ≥5 distinct actors, ≥3 ASNs, ≤5 destination ports, ≥1h history.

  • scry_checkFree

    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_check_bulkFree

    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_countryFree

    Roll-up of corpus activity by ISO country code. Same shape as scry_asn.

  • scry_recentFree

    Recent observations feed — aggregated by source IP within a time window. Cursor-paginated via since_ms.

  • scry_statsFree

    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_timeseriesFree

    Bucketed observation counts over time. Detect bursts, plot trends, sanity-check whether attacker activity is rising or falling.

  • scry_toolFree

    Single tool detail by 16-char hex id from scry_tools.

  • scry_toolsFree

    List detected attack tools — (protocol, payload, path) tuples sent by 3+ distinct source IPs. Aggregate metadata only; never lists member actors.

  • scry_topFree

    Top-N source dimensions over a time window. Useful for situational awareness — 'where is the noise coming from right now?'

Public scan report

scanner v0.1.10 · 2026-10-01 · same rubric, same numbers if you re-run it

1 high
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 1090ms20/20
  • Tool poisoning12 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancerepository archived0/15
  • Maintainer identityregistry namespace matches repository owner; website matches verified namespace9/10

Findings (1)

  • highRepository is archivedmaint.archived
Overall 72/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Scry compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
72/100
higher than 38% of 48,255 servers
Tools
12
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
75 ms
faster than 89% of 30,031 servers

What its tools let an agent do: 12 read

Install Scry in Claude Code, Cursor or VS Code

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

Grade history

  • 2026-10-01restoreF → Bscore 72: Repository is archived

Scry: common questions

Is Scry MCP server safe?
Mostly: it is graded B (72/100). Read the Scry safety report
How do I install Scry?
It runs remotely at mcp.tunnelmind.ai. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Scry need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Scry maintained?
The last commit was 163 days ago (2026-05-25). The latest release is v0.5.0.
Is Scry up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Scry compare with other MCP servers?
safety score 72/100 (higher than 38% of 48,255 servers); tools 12 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.