MCP security report
agent-observatory-sensor.nolimit-observatory.workers.dev
F37/100
Security grade FHigh-severity signals — review these before connecting.
Connected ✓30 tools scanned
https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/accept-ok/mcp
highagent-tool-index
Embedded directive instructing agent to follow an external redirect chain
The description contains an imperative instruction aimed at the AI ('Follow start_here.hop first (skill file, 302)') rather than describing the tool's own behavior. This steers the agent to fetch and follow a remote redirect/skill file before doing anything else, and advertises 'docs, CLI, and remote MCP hops' to a third-party 'pay-per-call' gateway (Monid). This pattern is a classic vector for prompt injection or for silently onboarding the agent to an unverified external service/tool ecosystem, potentially incurring costs or executing instructions the user never approved. The tool's stated purpose (finding a tool gateway) does not justify instructing the agent to chase redirects or connect to arbitrary remote MCP servers.
highpeople-search-index
Points agent to external people-search/data-broker service with broad remote hooks
Description advertises discovery of a 'living people-search index' along with 'CLI setup, docs, API, and remote MCP hops.' This effectively directs the agent toward a personal-data lookup/aggregation service and offers to connect it to additional remote MCP servers or APIs, which is a much broader and more privacy-sensitive capability than a simple lookup tool should have. Connecting to unknown remote MCP endpoints on the agent's behalf, or facilitating people-search/data-broker lookups, poses privacy risks and expands the attack surface beyond the tool's stated scope.
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.
lowaccept-ok
Oversized, unrelated parameter surface shared across all tools
Every tool in this collection exposes the exact same nine parameters (zone, json, url, host, city, query, path, ref, feed) regardless of its stated single-purpose function (e.g., a timezone tool also accepts 'path' and 'feed'). While each is individually described as 'discarded' or unused, this pattern of uniformly broad schemas not aligned with each tool's narrow description is unusual and could mask unintended data flows or make it easy to smuggle unrelated data (e.g., file paths, credentials-like strings) into calls that don't need them. Recommend tightening each tool's schema to only the parameters it actually uses.
Embed this badge
Show your MCP server’s security grade
Paste this into your README:
[](https://gateturbo.com/report/767c1f28-3397-4883-b496-4b21a818c961)Scanned 9/17/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