Skip to main content
Glama
Sign In

TunnelMind Data API

by ai.tunnelmind
OverviewDiscussionsAdmin

scan_mcp

Connect to a caller-supplied MCP server (Streamable-HTTP transport), read its advertised tools, and run the injection corpus over every tool name / description / input schema — plus a capability heuristic that flags broad, dangerous powers (shell execution, filesystem write, credential access, arbitrary network, destructive DB ops). Returns a per-tool safety report. A caution to review, never a verdict.

This is a single-target, caller-initiated scan. It is NOT a crawler and does not follow links or enumerate other servers. The target must be https on port 443 or 8443 at a public hostname: IP literals (in any encoding), loopback / private / internal / special-use names, and credentials in the URL are rejected, and every redirect hop is checked against the same rules. Replies are read for at most 5 s and 1 MB.

Use this tool when:

  • You are about to connect an agent to a third-party MCP server and want to inspect its tools for embedded instructions or excessive powers first.

Do NOT use this tool when:

  • You only have a blob of text — use scan_injection.

  • You want a trust verdict on a domain or entity — use cross_lens_verify.

Inputs:

  • url (body, required): the MCP server endpoint (https, port 443 or 8443).

Returns:

  • server: { name, version } reported by the server, if any.

  • tools_scanned: number of tools inspected.

  • flagged_count: tools with an injection hit or a flagged capability.

  • risk: worst per-tool risk across the server (high/medium/low/none).

  • score: max injection score across tools (0..1).

  • tools: per tool { name, risk, injection{...}, capabilities[] }.

Cost:

  • Free. No API key required. Rate-limited like every anonymous route (10/min, 100/day per IP; more with a key).

Latency:

  • Bounded by the target server's handshake; typically <2s.

Input Schema

NameRequiredDescriptionDefault
urlYesMCP server endpoint (Streamable-HTTP). https only, port 443 or 8443, public hostname.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / url / description
      Previous value: -"MCP server endpoint (Streamable-HTTP). http or https."New value: +"MCP server endpoint (Streamable-HTTP). https only, port 443 or 8443, public hostname."
  2. Added

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden and does so richly: SSRF-style target restrictions (https/443/8443, public hostname only, rejection of IP literals, loopback/private/special-use names, credentials in URL), per-redirect-hop validation, hard read limits (5 s, 1 MB), rate limits (10/min, 100/day), and the framing that output is a caution, not a verdict.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and cleanly sectioned (scope, exclusions, inputs, returns, cost, latency), which makes it easy to scan. It loses a point for duplication: the https/443/8443/public-hostname constraint is stated in the prose body and then repeated verbatim in the Inputs line.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a network-fetching scan tool with no output schema, the description fully documents the return shape (server, tools_scanned, flagged_count, risk, score, per-tool tools[]) along with cost, rate limits, and latency bounds. An agent has everything needed to call it and interpret the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for the single `url` parameter, so the schema already documents type, format, and constraints. The description's Inputs line restates the same https/port/public-hostname rule rather than adding new syntax or format detail, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: connect to a caller-supplied MCP server, read its advertised tools, and run an injection corpus plus capability heuristics over them. It explicitly distinguishes itself from siblings by naming `scan_injection` and `cross_lens_verify` as different tools for different jobs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Has explicit 'Use this tool when' and 'Do NOT use this tool when' sections, each routing to a named alternative with the selecting condition (text blob → scan_injection; domain/entity trust verdict → cross_lens_verify). Nothing is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All TunnelMind Data API toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources