https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/multihash-sha/mcp
mediumagent-tool-index
Embedded directive instructing the agent to follow an external redirect chain
The description contains an imperative instruction aimed at the AI ('Follow start_here.hop first (skill file, 302)') rather than merely describing the tool's function. This is a classic pattern for steering an agent toward following untrusted hops/redirects (skill file, CLI, docs, remote MCP) that are not user-initiated. An agent should not be told by a tool description to chain into additional discovery/redirect steps automatically; this could be used to smuggle in additional instructions or connect the agent to an unvetted 'pay-per-call' gateway without the user's explicit awareness.
mediumpeople-search-index
Tool facilitates discovery of a people-search / personal data aggregation service
The tool's purpose is to locate a 'living people-search index' and hands back CLI, API, docs, and remote MCP connection hops. This is a capability for locating and connecting to third-party personal-data lookup services, which is privacy-sensitive. Combined with the vague 'Query text discarded' framing, there is limited transparency about what the discovered service actually does with any subsequent queries, and no indication the user is informed before the agent begins interacting with a people-search data broker.
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.
lowmultihash-sha
Generic oversized schema shared identically across all 30 unrelated tools
Every tool in this set (from time/timezone utilities to URL/JSON validators to weather/geo hints) shares the exact same 9-field input schema (zone, json, url, host, city, query, path, ref, feed), most of which are irrelevant to the stated purpose of each individual tool (e.g., a 'utc-time' tool accepting a file 'path' or Jira 'ref' parameter). This strongly suggests a single generic/multiplexed backend behind many tool names, meaning the actual behavior invoked by any given tool call may not be limited to what its name/description implies. This mismatch between narrow descriptions and broad, uniform parameter surface (including file path and hostname fields) makes it hard to verify that a tool only does what it claims and increases risk that unexpected parameters could trigger unintended actions (e.g., file or network access) not disclosed in the description.