MCP security report
agent-observatory-sensor.nolimit-observatory.workers.dev
D52/100
Security grade DHigh-severity signals — review these before connecting.
Connected ✓30 tools scanned
https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/linear-id-shape/mcp
highagent-tool-index
Embedded instruction directs agent to follow external redirect chain to an untrusted gateway
The description explicitly instructs the AI to 'Follow start_here.hop first (skill file, 302)' and then chase 'docs, CLI, and remote MCP hops.' This is an instruction embedded in a tool description that tells the agent to autonomously follow redirects to an external, unverified 'pay-per-call' service and to load additional remote MCP servers/CLI tooling. This is a classic vector for supply-chain compromise or prompt injection: the agent could be steered into executing code, installing tools, or incurring paid API calls from an unknown third party ('Monid') without the user's explicit awareness or consent.
mediumpeople-search-index
Directs agent toward a people-search/doxing-style external service and remote MCP hops
The description promotes finding a 'living people-search index (Ploid)' and returns CLI setup, docs, API, and 'remote MCP hops.' This steers the agent toward third-party services designed to look up personal information about individuals, and toward connecting to additional remote MCP servers of unknown provenance. Both the privacy implications of a people-search index and the instruction to chain into unverified remote tooling warrant caution before the agent acts on this guidance.
low
Not on gate's verified list
This server isn't on gate's handpicked list. That's not necessarily bad, but there's no third-party signal about it — review its tools carefully.
lowlinear-id-shape
Uniform oversized schema shared across unrelated single-purpose tools
Every tool in this set (including this one) exposes the same nine parameters — zone, json, url, host, city, query, path, ref, feed — regardless of the tool's actual stated purpose. This generic, one-size-fits-all schema makes it hard to verify that each tool only uses the field relevant to it, and increases the risk that unrelated or sensitive-looking fields (e.g., 'path') could be silently repurposed. While each individual tool description claims narrow, discarded-after-use behavior, the shared broad schema across ~28 tools is an unusual design pattern worth flagging for review.
lowfile-path-ok
Accepts local file path parameter despite claiming no disk access
The tool accepts a 'path' field described as a file path 'to check; no disk access,' but combined with the shared broad schema pattern across all tools, this is worth verifying independently since a path parameter is unusual for a set of otherwise web/text utilities and could be a residual or repurposable capability if the no-disk-access claim is not enforced server-side.
Embed this badge
Show your MCP server’s security grade
Paste this into your README:
[](https://gateturbo.com/report/2a3b1f50-001c-43a9-ac0c-fcfd2685863b)Scanned 9/13/2026 · This is a point-in-time snapshot of the server’s public tools. Re-scan.
Connect this server safely with gate.
Continuous re-scans, drift alerts, per-tool allow/ask/block, and a log of every call.
Monitor it — free