# Scry

> Free IPv4 lookups against a distributed attacker-observation corpus.

- name: ai.tunnelmind/scry
- version: 0.5.0
- connection class: R0 (autonomous)
- trust: 92/100
- quality: 79/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/ai.tunnelmind%2Fscry
- tools: https://api.protogrid.dev/v1/servers/ai.tunnelmind%2Fscry/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "scry": {
      "type": "http",
      "url": "https://mcp.tunnelmind.ai/mcp"
    }
  }
}
```


## Trust

- hygiene: 100
- liveness: 96
- freshness: 65
- provenance: 100
- drivers: +repository +namespace-matches-repo +dns-namespace +website +reachable +uptime-91% ~updated-149d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 79/100 (good)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-03-26; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 71 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- fail `tools.annotations`: no tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: scry_country (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); scry_campaign (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); scry_asn (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); …
- pass `tools.token_cost`: about 1,133 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: no tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 12, about 1,133 tokens to load them all
- tool set hash: 0c9a5b5d49d7791f5ca273b054738ee7
- badge: [![protogrid quality](https://protogrid.dev/badge/ai.tunnelmind/scry.svg)](https://protogrid.dev/servers/ai.tunnelmind/scry)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://mcp.tunnelmind.ai/mcp (streamable-http, auth none, reachable true, uptime30d 0.90697676)

## Packages

_none_

## Tools (12)

- `scry_asn`: 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_campaign`: Single campaign detail by id (format: c[0-9a-f]{15}).
- `scry_campaigns`: Active threat campaigns — coordinated attacker activity that exceeds the noise floor. ≥5 distinct actors, ≥3 ASNs, ≤5 destination ports, ≥1h history.
- `scry_check`: 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_bulk`: 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_country`: Roll-up of corpus activity by ISO country code. Same shape as scry_asn.
- `scry_recent`: Recent observations feed — aggregated by source IP within a time window. Cursor-paginated via since_ms.
- `scry_stats`: 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_timeseries`: Bucketed observation counts over time. Detect bursts, plot trends, sanity-check whether attacker activity is rising or falling.
- `scry_tool`: Single tool detail by 16-char hex id from scry_tools.
- `scry_tools`: List detected attack tools — (protocol, payload, path) tuples sent by 3+ distinct source IPs. Aggregate metadata only; never lists member actors.
- `scry_top`: Top-N source dimensions over a time window. Useful for situational awareness — 'where is the noise coming from right now?'