mcp-registry/io.github.br0ski777/timezone-converter · v1.0.0
Also listed as glama/br0ski777/timezone-converter
As of 2026-10-20 19:58 UTC, the Br0ski777 Timezone Converter MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 0% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 5 minutes.
Convert datetime between timezones. List all IANA zones. x402 micropayment.
Point your MCP client at this streamable-http endpoint: https://timezone-converter.api.klymax402.com/mcp
The endpoint did not complete an MCP handshake.
Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST. How to fix →
1 of 1 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.br0ski777%2Ftimezone-converter/fixes
{
"name": "utility_convert_timezone",
"description": "Use this when you need to convert a date/time from one timezone to another. Returns the converted datetime with offset data in JSON.\n\nReturns: 1. convertedDatetime (ISO 8601) 2. fromTimezone and toTimezone 3. utcOffset (e.g. \"+01:00\") 4. abbreviation (e.g. \"CET\", \"EST\") 5. isDST (boolean) 6. originalDatetime.\n\nExample output: {\"originalDatetime\":\"2026-04-13T14:30:00\",\"fromTimezone\":\"America/New_York\",\"toTimezone\":\"Europe/Paris\",\"convertedDatetime\":\"2026-04-13T20:30:00\",\"utcOffset\":\"+02:00\",\"abbr",
"inputSchema": {
"type": "object",
"required": [
"datetime",
"from",
"to"
],
"properties": {
"to": {
"type": "string",
"description": "Target IANA timezone (e.g. Europe/Paris)"
},
"from": {
"type": "string",
"description": "Source IANA timezone (e.g. America/New_York)"
},
"datetime": {
"type": "string",
"description": "Date/time string (ISO 8601 or human-readable, e.g. '2024-01-15T14:30:00')"
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.br0ski777/timezone-converter"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.br0ski777/timezone-converter"}) over MCP.
utility_convert_timezone ~265 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.br0ski777%2Ftimezone-converter?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.br0ski777%2Ftimezone-converter?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.br0ski777%2Ftimezone-converter.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.br0ski777%2Ftimezone-converter.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.br0ski777%2Ftimezone-converter?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:7727e54ab9f18157…, first seen 2026-10-17, included at leaf 6683 of 75,126. Version history · verify what your client received.
Compare: most reliable productivity servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-20 19:58 UTC, the Br0ski777 Timezone Converter MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 0% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 5 minutes.
Br0ski777 Timezone Converter MCP server advertises 1 tool, including utility_convert_timezone.
Point your MCP client at this streamable-http endpoint: https://timezone-converter.api.klymax402.com/mcp
Glimind scanned all 1 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.