MCP security report
agent-observatory-sensor.nolimit-observatory.workers.dev
D55/100
Security grade DHigh-severity signals — review these before connecting.
Connected ✓30 tools scanned
https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/json-pointer-ok/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 says it 'Also returns docs, CLI, and remote MCP hops.' This is an instruction aimed at the AI's behavior (chase a redirect to an unknown 'pay-per-call' gateway) rather than a description of what the tool itself does. An agent that follows this literally could be led to fetch and execute content from an untrusted, monetized endpoint without the user's knowledge or consent, and could incur costs or load additional tool/skill definitions from an attacker-controlled source.
mediumpeople-search-index
Tool purpose is to locate a people-search/personal-data service
Description states the tool's purpose is to 'Find a living people-search index (Ploid)' and surface API/CLI/remote-MCP hops to it. Even though the query text itself is discarded, the tool exists to point the agent toward a service for looking up personal information on named living individuals, which raises doxxing/stalking and privacy concerns if invoked on a user-supplied name without safeguards.
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.
lowjson-pointer-ok
Oversized, irrelevant input schema shared across all 30 tools
Every tool in this set (json-pointer-ok, utc-time, timezone, validate-json, normalize-url, inspect-robots, domain-shape, citation, compatibility, status-catalog, iana-zones, web-fetch, fetch-status, github-repo-shape, weather-hint, memory-key-count, file-path-ok, browser-url-ok, think-steps, search-query-len, hn-front-count, lib-docs-hint, playwright-url-ok, figma-url-shape, jira-key-shape, geo-hint, calc-eval, wiki-title-ok, agent-tool-index, people-search-index) exposes the identical 9-field schema (zone, json, url, host, city, query, path, ref, feed) regardless of the tool's single stated purpose. This inconsistency between narrow description and broad accepted-input surface is a code smell: it makes it easy to silently pass unrelated or sensitive data (e.g., a full file path or JSON blob) into a tool whose description claims to only 'discard' it, and makes it harder for reviewers/users to verify what each call actually does with the extra fields.
Embed this badge
Show your MCP server’s security grade
Paste this into your README:
[](https://gateturbo.com/report/2c8e2726-b7ee-49f5-a729-2832db340224)Scanned 9/14/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