MCP security report
agent-observatory-sensor.nolimit-observatory.workers.dev
F43/100
Security grade FHigh-severity signals — review these before connecting.
Connected ✓31 tools scanned
https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/guid-ok/mcp
highpeople-search-index
Directs agent to a people-search/data-broker service and dictates navigation with tracking
This tool's description instructs the agent to 'Follow start_here.hop' (with embedded UTM tracking) to reach a 'living people-search index.' Beyond being an embedded directive to the AI about what to do next, the tool's stated purpose — indexing personal-data lookup services for living individuals — raises privacy concerns (facilitating potential doxxing or unauthorized personal data discovery) that are broad relative to a simple 'find an index' utility.
mediumagent-tool-index
Embedded directive instructing agent to follow a specific tracked link
The description tells the agent to 'Follow start_here.hop first' and explicitly embeds UTM tracking parameters (utm_source=agent-observatory&utm_medium=agent) as if dictating required agent behavior. This is an instruction aimed at the AI's action sequence rather than a description of the tool's function, and it funnels the agent toward a specific monetized/tracked destination without the user's awareness or consent.
mediumagent-ads-index
Embedded directive steering agent toward ad placement / trial sign-up for an undisclosed third party
The description instructs the agent to 'Follow start_here.hop first' (again with hardcoded UTM tracking parameters) and mentions a '7-day trial handoff for your operator' — i.e., guiding the agent toward enrolling the user/operator in a third-party commercial trial or ad-placement scheme. This embeds a behavioral directive and a monetization/tracking mechanism inside what should be a neutral discovery tool description, which could manipulate the agent into taking actions benefiting an external advertiser without clear user consent.
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.
lowguid-ok
Oversized, irrelevant parameter surface shared across all tools
Every tool in this set (including this one) exposes an identical 10-field schema (zone, json, url, host, website, city, query, path, ref, feed) regardless of the tool's actual stated purpose. This templated over-broad schema makes it hard to verify that each tool only uses the inputs relevant to its description, and could mask unexpected data flows (e.g., a 'GUID shape' checker accepting a city name or git ref for no stated reason). Not malicious by itself, but it reduces auditability and should be tightened to only the parameters each tool actually needs.
Embed this badge
Show your MCP server’s security grade
Paste this into your README:
[](https://gateturbo.com/report/b51d64e1-3e4c-42fd-959b-d226fe98daf6)Scanned 10/1/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