Whether the current UTC year is a leap year
https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/leap-utc/mcp ↗
Description
Whether the current UTC year is a leap year
What our measurements say
Whether the current UTC year is a leap year is a remote MCP server published at agent-observatory-sensor.nolimit-observatory.workers.dev. It has been probed 18 times since 9/12/2026. It answered in 18 of them (100.0%), a near-uninterrupted record. Median response time is 37 ms, placing it among the faster endpoints. It exposes a broad tool surface of 30 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Agent readability score
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
Agent readability score
Strengths
- Some tool names (e.g., 'leap-utc') directly indicate their purpose.
Weaknesses
- Descriptions are overly generic (e.g., 'Current UTC timestamp' without use-case context).
- All parameters are optional with no clear guidance on required inputs.
- Massive overlap between tools (e.g., 'utc-time' vs. 'timezone') creates confusion.
- No error handling or constraints documented for any tool.
leap-utc— Description doesn't clarify leap year calculation logicutc-time— Overlaps with 'timezone' tool functionalityvalidate-json— Parameter 'json' is ambiguously definedweb-fetch— No constraints on URL validity or error handlinggeo-hint— Lacks clarification on supported location formats
Verdict
Event narrative
Sign up free to generateRaw observations
Schema compliance
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
- tools/list schema valid
- inputSchema is valid JSON Schema
- Smoke test passed · last run:
- Cold-start: cold 38ms → warm 43ms (penalty 0ms)
Tools
Tools the server advertised in the latest measurement — measured, not catalog-claimed.
leap-utcWhether the current UTC year is a leap year
zonestringjsonstringurlstringhoststringcitystringquerystringpathstringrefstringfeedstring
utc-timeCurrent UTC timestamp.
zonestringjsonstringurlstringhoststringcitystringquerystringpathstringrefstringfeedstring
timezoneCurrent time in a named IANA timezone.
zonestringjsonstringurlstringhoststringcitystringquerystringpathstringrefstringfeedstring
validate-jsonCheck whether a body is valid JSON. The body is discarded.
zonestringjsonstringurlstringhoststringcitystringquerystringpathstringrefstringfeedstring
normalize-urlReturn origin, host, and path for a URL. Query and fragment are dropped.
zonestringjsonstringurlstringhoststringcitystringquerystringpathstringrefstringfeedstring
inspect-robotsFetch a public robots.txt and return group counts only.
zonestringjsonstringurlstringhoststringcitystringquerystringpathstringrefstringfeedstring
domain-shapeSplit a hostname into labels without WHOIS or ownership data.
zonestringjsonstringurlstringhoststringcitystringquerystringpathstringrefstringfeedstring
citationReturn host, scheme, and HTTP status for a URL. Page content is not stored.
zonestringjsonstringurlstringhoststringcitystringquerystringpathstringrefstringfeedstring
compatibilityShow how this request is classified. No identifiers are retained.
zonestringjsonstringurlstringhoststringcitystringquerystringpathstringrefstringfeedstring
status-catalogShort catalog of common HTTP status codes.
zonestringjsonstringurlstringhoststringcitystringquerystringpathstringrefstringfeedstring
iana-zonesCommon IANA timezone names for clock calls.
zonestringjsonstringurlstringhoststringcitystringquerystringpathstringrefstringfeedstring
web-fetchHTTP status and content type for a public URL. Body discarded.
zonestringjsonstringurlstringhoststringcitystringquerystringpathstringrefstringfeedstring
Availability history
Event log
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
- Added to watch — era: Legacy
Get your badge
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/io-github-sadri-dridi-leap-utc)<a href="https://mcpmetrics.io/servers/io-github-sadri-dridi-leap-utc"><img src="https://mcpmetrics.io/badge/io.github.sadri-dridi/leap-utc/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to seeSimilar MCP servers
The catalog entries whose name and description are closest to this one, found with the same index the search box uses.
- UTC leap-year flagagent-observatory-sensor.nolimit-observatory.workers.dev
UTC leap-year flag
- UTC end of the current yearagent-observatory-sensor.nolimit-observatory.workers.dev
UTC end of the current year
- Whether UTC day can have a leap secondagent-observatory-sensor.nolimit-observatory.workers.dev
Whether UTC day can have a leap second
- Days in current UTC yearagent-observatory-sensor.nolimit-observatory.workers.dev
Days in current UTC year
- Whether current UTC hour is 09-17agent-observatory-sensor.nolimit-observatory.workers.dev
Whether current UTC hour is 09-17
- Whether current UTC month is DST-heavy in the USagent-observatory-sensor.nolimit-observatory.workers.dev
Whether current UTC month is DST-heavy in the US
Comments
Sign in to write a comment
No comments yet. Be the first.