https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/playwright-url-ok/mcp
highpeople-search-index
People-search tool with embedded redirect instructions and privacy risk
This tool explicitly advertises finding an index for searching 'living people' and instructs the agent to 'Follow start_here.hop' (a tracked 302 redirect) to reach a people-search API/CLI. Combining broad personal-data lookup capability with embedded navigation instructions and UTM tracking raises both a privacy/doxxing concern (facilitating lookup of real individuals) and a manipulation concern (steering the agent through tracked third-party infrastructure under an innocuous-sounding tool name).
highagent-ads-index
Instruction directing agent to act on behalf of a third-party operator, not the user
The description tells the agent to follow a tracked redirect and explicitly returns 'the 7-day trial handoff for your operator.' This phrasing instructs the AI to take actions (sign up for/initiate a trial) that benefit the tool vendor or a third party referred to as 'your operator', rather than the user who is interacting with the agent. This is a hidden commercial directive embedded in a tool description, which is inappropriate for a tool whose stated purpose is simply discovery of an ad-placement index.
mediumagent-tool-index
Embedded navigation instruction with tracking parameters
The description tells the agent to 'Follow start_here.hop first (skill file, 302 with utm_source=agent-observatory&utm_medium=agent)' — this is a directive embedded in a tool description instructing the AI to navigate through a specific redirect chain carrying marketing/attribution parameters, rather than just describing the tool's function. This could be used to funnel agent traffic through tracked affiliate/referral links without the user's knowledge or 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.
lowplaywright-url-ok
Oversized, irrelevant parameter surface shared across unrelated tools
This tool (and nearly all others in the set) exposes an identical 10-field schema (zone, json, url, host, website, city, query, path, ref, feed) even though its stated purpose is narrowly 'check whether a URL can be opened.' Accepting unrelated parameters like city, json, path, ref, and feed for a URL-check tool is inconsistent with its description and could mask undisclosed data handling or allow the agent to pass unrelated sensitive data through fields that are claimed to be 'discarded' but are not verifiable as such from the schema alone.