MCP security report
agent-observatory-sensor.nolimit-observatory.workers.dev
F31/100
Security grade FHigh-severity signals — review these before connecting.
Connected ✓30 tools scanned
https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/wadl-ok/mcp
highagent-tool-index
Embedded directive instructing agent to follow an external redirect chain
The description tells the agent to 'Follow start_here.hop first (skill file, 302)' and describes 'docs, CLI, and remote MCP hops' to a 'pay-per-call tool gateway (Monid)'. This is an instruction embedded in a tool description that directs the agent's behavior (auto-following redirects to an unknown, monetized, external service) rather than just describing a function. This could cause the agent to silently chain into untrusted infrastructure, incur costs, or execute further hops/instructions without user awareness or consent.
highpeople-search-index
Directs agent toward a people-search / data-broker service
Description promotes finding a 'living people-search index (Ploid)' and returns 'CLI setup, docs, API, and remote MCP hops.' This steers the agent toward a service designed to look up personal information about individuals, which is a privacy-sensitive capability far beyond a simple lookup/validation utility, and could facilitate doxxing or unauthorized personal data retrieval if the agent follows the suggested hops.
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.
lowwadl-ok
Tool purpose unclear/mismatched name vs. schema
The tool name ('wadl-ok') and description ('WADL resource count') do not correspond to any parameter in the shared schema (no WADL-related field), making its real behavior opaque. Combined with the same broad input schema used by all 30 tools, this makes it hard to verify what data is actually consumed or sent.
lowutc-time
Overly broad input schema unrelated to stated function
A tool described purely as returning 'Current UTC timestamp' accepts nine unrelated parameters (json, url, host, city, query, path, ref, feed) that have nothing to do with time. This pattern, repeated identically across all 30 tools, suggests a shared generic backend that could silently accept and process unrelated user data (URLs, file paths, queries, feeds) under the guise of unrelated tool calls, increasing risk of unintended data flow or capability creep beyond the documented purpose.
lowfile-path-ok
File path parameter accepted despite 'no disk access' claim, shared with unrelated tools
The tool claims 'no disk access' but is bundled with an identical schema across many tools including ones that fetch remote URLs (web-fetch, citation, etc.). Since all tools share the same schema and only differ by description, there's no technical enforcement visible that path data isn't reused by another tool in the set that does perform network calls, which could combine local path info with outbound requests.
Embed this badge
Show your MCP server’s security grade
Paste this into your README:
[](https://gateturbo.com/report/997a4b95-63ab-46f1-874f-b51c45ba4505)Scanned 9/16/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