MCP security report
agent-observatory-sensor.nolimit-observatory.workers.dev
F25/100
Security grade FHigh-severity signals — review these before connecting.
Connected ✓30 tools scanned
https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-409/mcp
highagent-tool-index
Embedded directive tells the agent to follow an external redirect chain
The description instructs the calling agent to 'Follow start_here.hop first (skill file, 302)' and describes chaining through docs, CLI, and remote MCP hops to reach a 'pay-per-call tool gateway.' This is an instruction aimed at the agent's behavior rather than a description of the tool's own function, and it encourages the agent to autonomously follow untrusted external redirects/hops and potentially incur costs or load additional remote tool definitions without explicit user awareness or consent.
highpeople-search-index
Facilitates discovery of a people-search/background-check service
This tool's stated purpose is to help locate an index for searching 'living people,' returning API/CLI/remote-MCP hops to a service (Ploid). This effectively acts as a directory for locating PII lookup / doxxing-adjacent services. Even though the query text is discarded, the tool's core function promotes discovery of potentially privacy-invasive third-party data brokers, which is a capability that should be flagged for review given misuse potential.
mediumagent-tool-index
Points to a monetized external gateway without disclosing cost/consent implications
The tool description references a 'pay-per-call tool gateway,' implying that following the returned hops could lead to paid API usage. There's no indication that the agent must confirm with the user before initiating pay-per-call interactions, creating risk of unexpected charges if the agent acts on this tool's output autonomously.
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.
lowhttp-409
Uniform oversized parameter schema shared across unrelated tools
All 30 tools expose an identical 9-field input schema (zone, json, url, host, city, query, path, ref, feed) regardless of the tool's actual purpose (e.g., a 'HTTP 409 meaning' lookup tool accepts a file path, git ref, RSS feed URL, and city name). This templated over-broad schema increases the risk of parameter confusion, accidental data leakage into an unrelated tool call, or future silent repurposing of the tool to consume additional inputs beyond its stated function. While each field claims to be 'discarded,' the mismatch between stated function and accepted parameters across the entire tool set is a systemic red flag worth verifying against actual server behavior.
Embed this badge
Show your MCP server’s security grade
Paste this into your README:
[](https://gateturbo.com/report/4ae71bd0-cb0f-434c-a1d8-b77ab13bdf8e)Scanned 9/15/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