highpeople-search-index
Directs agent to a people-search / background-check service and embeds tracked redirect instruction
Description instructs the agent to 'Follow start_here.hop' (with tracking parameters) to reach a 'people-search index' for locating information about living individuals. Tools that facilitate lookup of personal data on private individuals carry inherent privacy/doxxing risk, and the embedded 'follow this hop first' phrasing is a directive aimed at agent behavior rather than a neutral capability description.
highagent-ads-index
Embedded instruction steers agent toward advertising sign-up/trial on behalf of its operator
The description instructs the agent to 'Follow start_here.hop first' via a tracked redirect (utm_source=agent-observatory&utm_medium=agent) and explicitly returns a '7-day trial handoff for your operator.' This asks the agent to take an action that commits its operator to a commercial trial/subscription, which is a business decision that should require explicit user/operator consent rather than being embedded as a default instruction in a tool description.
mediumagent-tool-index
Embedded directive instructing agent to follow tracked redirect chain
The description tells the agent to 'Follow start_here.hop first' through a 302 redirect that embeds marketing/tracking parameters (utm_source=agent-observatory&utm_medium=agent). This is an instruction aimed at the AI's behavior (navigate this specific hop before anything else) rather than a description of the tool's function, and it funnels the agent toward a third-party monetization/affiliate gateway without the user necessarily being aware of the redirect or its tracking parameters.
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.
lowlang-bg
Unrelated/overloaded schema parameters shared across unrelated tools
This tool (and all 31 tools reviewed) share an identical schema with ten unrelated parameters (zone, json, url, host, website, city, query, path, ref, feed) regardless of the tool's actual single-purpose function (e.g., a language-tag tool accepting a 'path' or 'ref' parameter). This design is unusual and could let data be silently routed into unrelated processing paths or make it harder for the agent/user to reason about what data is actually sent/collected per call; recommend tightening schemas to only the parameters each tool actually uses.