mcp-registry/io.github.zvmzaretsky/utility-belt · v1.0.0
Also listed as glama/zvmzaretsky/fabtally-utility-belt
As of 2026-10-26 20:36 UTC, the Zvmzaretsky Utility Belt MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 10 outages in 90 days, with a median recovery of 11 minutes.
13 deterministic agent utilities: timezone, cron, RRULE, currency, regex, diff, hashing & more.
Point your MCP client at this streamable-http endpoint: https://belt.fabtally.com/mcp
13 of 13 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 →
1 tool(s) have parameters with no type (no type/enum/anyOf/$ref).
Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →
2 parameter(s) across 1 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. 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. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.zvmzaretsky%2Futility-belt/fixes
{
"name": "convert",
"description": "FREE. Convert a value between units in the same dimension: length, mass, temperature, volume, data, time, area, speed, angle, pressure, energy. Deterministic. Args: value (number), from (unit), to (unit). e.g. {value:100, from:'c', to:'f'} or {value:1, from:'GiB', to:'MB'}. Different-dimension conversions 400.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"value",
"from",
"to"
],
"properties": {
"to": {
"type": "string",
"description": "Target unit in the same dimension."
},
"from": {
"type": "string",
"description": "Source unit, e.g. c, km, GiB, gal, kg."
},
"value": {
"type": "number",
"description": "Numeric value to convert."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Unit conversion"
}{
"name": "cron",
"description": "PAID $0.001. Parse a 5- or 6-field cron expression and return the next N run times plus a plain-English description. Args: expression, timezone (IANA, default UTC), count (default 5), from (ISO, optional). Without payment returns the x402 challenge; pass x_payment to settle.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"expression"
],
"properties": {
"from": {
"type": "string",
"description": "Compute runs after this ISO datetime (default now)."
},
"count": {
"type": "integer",
"description": "How many upcoming runs (1-100, default 5)."
},
"timezone": {
"type": "string",
"description": "IANA timezone (default UTC)."
},
"x_payment": {
"type": "string",
"description": "x402 payment payload (base64) for this PAID tool. If supplied it is forwarded as the X-PAYMENT header to settle the $0.001 call and return the real result instead of a 402 challenge. Omit to get the price challenge first."
},
"expression": {
"type": "string",
"description": "Cron expression, e.g. '0 9 * * 1-5'."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "Cron -> next N runs + description (paid $0.001)"
}{
"name": "currency",
"description": "PAID $0.001. Convert an amount between currencies at reference/mid-market rates from a keyless public central-bank feed (ECB), cached. Informational, not a dealable quote. Args: amount, from, to (ISO-4217, e.g. USD, EUR, JPY). Without payment returns the x402 challenge; pass x_payment to settle.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"amount",
"from",
"to"
],
"properties": {
"to": {
"type": "string",
"description": "Target ISO-4217 code, e.g. EUR."
},
"from": {
"type": "string",
"description": "Source ISO-4217 code, e.g. USD."
},
"amount": {
"type": "number",
"description": "Amount in the source currency."
},
"x_payment": {
"type": "string",
"description": "x402 payment payload (base64) for this PAID tool. If supplied it is forwarded as the X-PAYMENT header to settle the $0.001 call and return the real result instead of a 402 challenge. Omit to get the price challenge first."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Live currency convert (paid $0.001)"
}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.zvmzaretsky/utility-belt"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.zvmzaretsky/utility-belt"}) over MCP.
datemath ~504 tokenstimezone ~330 tokensrrule ~306 tokenscron ~297 tokensdiff ~290 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.zvmzaretsky%2Futility-belt?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.zvmzaretsky%2Futility-belt?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.zvmzaretsky%2Futility-belt.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.zvmzaretsky%2Futility-belt.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.zvmzaretsky%2Futility-belt?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:ab45e81f1aa79990…, first seen 2026-10-17, included at leaf 3280 of 75,321. Version history · verify what your client received.
Compare: most reliable data servers · most reliable other servers · most reliable finance servers · most reliable security 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-26 20:36 UTC, the Zvmzaretsky Utility Belt MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 10 outages in 90 days, with a median recovery of 11 minutes.
Zvmzaretsky Utility Belt MCP server advertises 13 tools, including convert, cron, currency, datemath, diff.
Point your MCP client at this streamable-http endpoint: https://belt.fabtally.com/mcp
Glimind scanned all 13 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.