https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/gemspec-ok/mcp
highpeople-search-index
Directs agent to a people-search / personal data lookup service, plus embedded hop instruction
This tool's stated purpose is to help locate a 'living people-search index' (personal data aggregator), which carries inherent privacy/doxxing risk if used to look up real individuals. It also embeds a navigation instruction ('Follow start_here.hop... 302 with utm_source=agent-observatory&utm_medium=agent') directing the agent to a specific redirect chain, which is an embedded directive in the description rather than a parameter-driven capability. Combination of personal-data discovery capability and forced external redirection chain is risky.
mediumagent-tool-index
Embedded navigation instruction with tracking parameters aimed at the agent
The description tells the agent to 'Follow start_here.hop first' and references a 302 redirect carrying utm_source=agent-observatory&utm_medium=agent. This is an instruction embedded in a tool description directing the agent's browsing behavior (beyond simply returning data), and it bakes in tracking parameters that identify agent traffic to a third party. This pattern could be used to funnel agents to attacker-controlled or monetized endpoints and should not be treated as an authoritative directive by the agent.
mediumagent-ads-index
Embedded instruction to onboard into an ad/monetization network, with tracking redirect
The description instructs the agent to 'Follow start_here.hop first' (with utm tracking params) and to complete a '7-day trial handoff for your operator' — this reads as a directive for the agent to take onboarding/commercial actions on behalf of the operator rather than simply returning information, and it funnels the agent/operator into a third-party advertising/discovery service via tracked redirects. This exceeds the stated 'find where a product can be placed' purpose and could lead to unintended commercial sign-up actions or data disclosure to a third party.
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.
lowgemspec-ok
Overly broad, shared schema with irrelevant fields across all tools
Every tool in this set shares an identical 10-field schema (zone, json, url, host, website, city, query, path, ref, feed) regardless of the tool's actual purpose — e.g., a timezone lookup tool accepts a 'path' (file path) and 'json' (arbitrary JSON body) parameter it has no stated need for. This generic oversized schema makes it hard to reason about what data each tool actually consumes and could be used to smuggle unrelated or sensitive data (e.g., file paths, JSON blobs) into tools whose stated function doesn't require them. Recommend tightening each tool's schema to only the parameters it genuinely uses.