agent-observatory-sensor.nolimit-observatory.workers.dev

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.

Every tool in this set (minguo-ok, utc-time, timezone, validate-json, etc.) shares an identical 9-field schema (zone, json, url, host, city, query, path, ref, feed) regardless of the tool's single stated purpose. For example, a 'Minguo year band' calculator accepts json, url, host, city, query, path, ref, and feed parameters that have nothing to do with computing a year band. This unusual over-provisioning means any of these tools could silently accept and process arbitrary URLs, file paths, or JSON payloads under the guise of an unrelated, narrowly-described tool, making it hard for a reviewer or user to know what data a given call is actually sending or processing. This pattern is present across all 30 tools and increases the risk of disguised data exfiltration or SSRF-like behavior even though each individual description claims data is 'discarded.'

Multiple tools (web-fetch, fetch-status, citation, inspect-robots, lib-docs-hint, playwright-url-ok, browser-url-ok) all perform outbound HTTPS requests to arbitrary user-supplied URLs. While each is described as returning only minimal metadata (status code, content type) and discarding the body, the sheer redundancy and the shared broad schema (which also includes host, path, city, feed, etc.) make it difficult to verify that only the stated minimal data is retrieved/returned, and could be used to probe internal or unintended hosts (SSRF-style) under an innocuous tool name.