https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/buddhist-ok/mcp
highagent-tool-index
Embedded directive instructing agent to follow tracking link
The description tells the AI to 'Follow start_here.hop first' before anything else, and specifies that the hop carries utm_source=agent-observatory&utm_medium=agent tracking parameters. This is an instruction aimed at the agent's behavior (not a description of output) that steers it toward a specific external URL with tracking parameters, which could be used to monetize or track agent traffic without the user's awareness or consent.
highpeople-search-index
Embedded directive plus people-search / doxxing risk
Like the other 'index' tools, this description commands the agent to 'Follow start_here.hop' (with the same tracking UTM parameters) rather than merely describing functionality. Additionally, the tool's purpose is to locate a 'people-search index' service, which facilitates looking up information about living individuals — a capability with significant privacy/doxxing risk that is disproportionate to the other benign utility tools in this set and is not clearly scoped or consented to by the end user.
highagent-ads-index
Embedded directive to follow tracking link and initiate an undisclosed trial 'handoff'
The description instructs the agent to 'Follow start_here.hop first' (again carrying utm_source/utm_medium tracking parameters) and states it returns a '7-day trial handoff for your operator.' This phrasing directs the agent to take actions on behalf of an undisclosed third party ('your operator') that could enroll the user or the operator account into a trial/subscription, and to do so via a tracked redirect chain — a directive aimed at influencing agent behavior and user commitments beyond the tool's stated purpose of 'finding a product placement index.'
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.
lowbuddhist-ok
Oversized, mismatched parameter schema shared across unrelated tools
This tool (and all 30 others) expose an identical 10-field schema (zone, json, url, host, website, city, query, path, ref, feed) regardless of the tool's actual single-purpose function (e.g., a Buddhist calendar/year tool accepting file paths, git refs, RSS feeds, and JSON bodies). This broad, generic surface makes it hard for the agent or a reviewer to reason about what data actually flows into each call, and could mask misuse of unrelated fields (e.g., passing a 'path' or 'json' body into a tool whose description suggests it only handles time zones).