mcp-registry/io.github.kaitzyy-dev/readout · v1.0.0
As of 2026-10-19 15:58 UTC, the Kaitzyy Dev Readout MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Measured readings on open-source dependencies: health, end-of-life, model prices, incidents.
Claude Code
claude mcp add --transport http kaitzyy-dev-readout-mcp-server https://readout-7pt.pages.dev/api/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"kaitzyy-dev-readout-mcp-server": {
"type": "http",
"url": "https://readout-7pt.pages.dev/api/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
31 of 31 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 →
30 parameter(s) across 27 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 →
2 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 →
Handshake + tools/list takes ~1,792 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
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. 27 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.kaitzyy-dev%2Freadout/fixes
{
"name": "base_image_check",
"description": "For a container base image: its size, when it was last rebuilt, and whether the OS underneath it is still supported. Requires a key; see https://sighttrue.com/pricing.",
"inputSchema": {
"type": "object",
"required": [
"image"
],
"properties": {
"image": {
"type": "string"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "check_before_install",
"description": "Call this before adding a dependency. Returns only the facts a reviewer would be annoyed to discover afterwards: whether the publisher has withdrawn the package, whether it runs scripts on the installing machine, whether its repository is archived, how many advisories are on record, whether the licence is source-available, and how long since it was actually published. Each fact carries the address of the body that published it. It does not say whether to install; it says what is on record.",
"inputSchema": {
"type": "object",
"required": [
"registry",
"name"
],
"properties": {
"name": {
"type": "string",
"description": "Package name as the registry spells it."
},
"registry": {
"type": "string"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "check_eol",
"description": "Check whether a runtime, database or framework release is still receiving security fixes, and what to move to. Covers about two dozen products read daily from endoflife.date.",
"inputSchema": {
"type": "object",
"required": [
"product"
],
"properties": {
"cycle": {
"type": "string",
"description": "Release line, e.g. 3.9 or 20. Omit for every cycle."
},
"product": {
"type": "string",
"description": "Product as endoflife.date spells it, e.g. python, nodejs, postgresql."
}
},
"additionalProperties": false
},
"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.kaitzyy-dev/readout"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.kaitzyy-dev/readout"}) over MCP.
check_before_install ~211 tokensfind_model ~152 tokenscheck_eol ~144 tokenscheck_stack ~136 tokenswho_can_publish ~134 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.kaitzyy-dev%2Freadout?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.kaitzyy-dev%2Freadout?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.kaitzyy-dev%2Freadout.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.kaitzyy-dev%2Freadout.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.kaitzyy-dev%2Freadout?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:a7bf52526d65785f…, first seen 2026-10-17, included at leaf 4290 of 27,511. Version history · verify what your client received.
Compare: most reliable security servers · most reliable devops servers · most reliable other servers · most reliable data servers · most reliable knowledge 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-19 15:58 UTC, the Kaitzyy Dev Readout MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Kaitzyy Dev Readout MCP server advertises 31 tools, including advisory_severity, audit_manifest, base_image_check, check_before_install, check_eol.
Point your MCP client at this streamable-http endpoint: https://readout-7pt.pages.dev/api/mcp
Glimind scanned all 31 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.