Scry
REMOTE · MCP.TUNNELMIND.AI · SCANNED AUG 3
Free IPv4 lookups against a distributed attacker-observation corpus.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 12 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 874 tokens (~72/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage68
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 4% of tool parameters carry a description.Partial
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.tunnelmind.ai
claude mcp add --transport http ai-tunnelmind-scry https://mcp.tunnelmind.ai/mcp
[mcp_servers.ai-tunnelmind-scry] url = "https://mcp.tunnelmind.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-tunnelmind-scry": {
"type": "remote",
"url": "https://mcp.tunnelmind.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-tunnelmind-scry --url https://mcp.tunnelmind.ai/mcp --transport streamable-http
mcp_servers:
ai-tunnelmind-scry:
url: "https://mcp.tunnelmind.ai/mcp" {
"mcpServers": {
"ai-tunnelmind-scry": {
"type": "http",
"url": "https://mcp.tunnelmind.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 55
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://mcp.tunnelmind.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tunnelmind.ai | CN=YE1,O=Let's Encrypt,C=US | 23 Jun 2026 | 21 Sept 2026 | ECDSA 256 | ECDSA-SHA384 | 52a78d8e6067db0bef4f22f4efdb9e05d12 |
| SANs: *.tunnelmind.ai, tunnelmind.ai | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
DNSSEC insecure
Validation of mcp.tunnelmind.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| tunnelmind.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.tunnelmind.ai/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.tunnelmind.ai/mcp | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
scry_asn ~61
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.
| Name | Type | Req | Description |
|---|---|---|---|
| asn | string | yes | — |
| since_ms | integer | — | — |
No output schema declared.
No examples provided.
scry_campaign ~35
Single campaign detail by id (format: c[0-9a-f]{15}).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | — |
No output schema declared.
No examples provided.
scry_campaigns ~59
Active threat campaigns — coordinated attacker activity that exceeds the noise floor. ≥5 distinct actors, ≥3 ASNs, ≤5 destination ports, ≥1h history.
| Name | Type | Req | Description |
|---|---|---|---|
| include_inactive | boolean | — | — |
| limit | integer | — | — |
No output schema declared.
No examples provided.
scry_check ~127
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).
| Name | Type | Req | Description |
|---|---|---|---|
| ip | string | yes | IPv4 address (e.g. '8.8.8.8') |
No output schema declared.
No examples provided.
scry_check_bulk ~49
Look up many IPv4 addresses in one request. Up to 100 IPs per call. Same per-IP shape as scry_check, keyed by IP.
| Name | Type | Req | Description |
|---|---|---|---|
| ips | array | yes | — |
No output schema declared.
No examples provided.
scry_country ~42
Roll-up of corpus activity by ISO country code. Same shape as scry_asn.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | — |
| since_ms | integer | — | — |
No output schema declared.
No examples provided.
scry_recent ~67
Recent observations feed — aggregated by source IP within a time window. Cursor-paginated via since_ms.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | — | — |
| include_noise | boolean | — | — |
| limit | integer | — | — |
| protocol | string | — | — |
| since_ms | integer | — | — |
No output schema declared.
No examples provided.
scry_stats ~220
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
scry_timeseries ~56
Bucketed observation counts over time. Detect bursts, plot trends, sanity-check whether attacker activity is rising or falling.
| Name | Type | Req | Description |
|---|---|---|---|
| bucket | string | — | — |
| since_ms | integer | — | — |
| until_ms | integer | — | — |
No output schema declared.
No examples provided.
scry_tool ~30
Single tool detail by 16-char hex id from scry_tools.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | — |
No output schema declared.
No examples provided.
scry_tools ~63
List detected attack tools — (protocol, payload, path) tuples sent by 3+ distinct source IPs. Aggregate metadata only; never lists member actors.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | — | — |
| protocol | string | — | — |
| since_ms | integer | — | — |
No output schema declared.
No examples provided.
scry_top ~65
Top-N source dimensions over a time window. Useful for situational awareness — 'where is the noise coming from right now?'
| Name | Type | Req | Description |
|---|---|---|---|
| dimension | string | — | — |
| include_noise | boolean | — | — |
| limit | integer | — | — |
| since_ms | integer | — | — |
No output schema declared.
No examples provided.