mcp-registry/com.apished/apished · v1.0.0
As of 2026-10-27 00:26 UTC, the Apished MCP server is up with a Glimind reliability score of 84/100 (grade B). Over the last 30 days it answered 99.4% of Glimind's liveness checks.
Validates PESEL/NIP/REGON/IBAN/Luhn/ISBN/EAN/BIC/VAT; RPN, dates, hash, tokens, random, encode, time
Point your MCP client at this streamable-http endpoint: https://apished.com/mcp
52 of 52 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 →
52 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
41 parameter(s) across 24 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) 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 →
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 →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 24 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.apished%2Fapished/fixes
{
"name": "color_convert",
"description": "Converts a color between hex, rgb, hsl, and hsv. value's shape depends on from/to: a string for hex, an object ({r,g,b,a?} etc.) otherwise.",
"inputSchema": {
"type": "object",
"required": [
"from",
"to",
"value"
],
"properties": {
"to": {
"type": "string",
"description": "hex, rgb, hsl, or hsv"
},
"from": {
"type": "string",
"description": "hex, rgb, hsl, or hsv"
},
"value": {
"description": "a hex string, or an {r,g,b,a?}/{h,s,l,a?}/{h,s,v,a?} object per from",
"type": "string"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "csv_stats",
"description": "Parses CSV text (header row required) and reports per-column non-empty/empty value counts across the data rows. No numeric aggregation.",
"inputSchema": {
"type": "object",
"required": [
"text"
],
"properties": {
"text": {
"type": "string"
},
"delimiter": {
"type": "string"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "csv_validate",
"description": "Reports whether CSV text is structurally well-formed: every row has the same field count as the first.",
"inputSchema": {
"type": "object",
"required": [
"text"
],
"properties": {
"text": {
"type": "string"
},
"delimiter": {
"type": "string"
}
},
"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/com.apished/apished"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.apished/apished"}) over MCP.
pipe_run ~277 tokenshash_hmac ~203 tokensrpncalc_eval ~178 tokensregon_validate ~174 tokensdatemath_businessdays ~170 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%2Fcom.apished%2Fapished?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.apished%2Fapished?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.apished%2Fapished.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.apished%2Fapished.svg :target: https://glimind.com/server/mcp-registry%2Fcom.apished%2Fapished?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:bd3911775f686886…, first seen 2026-10-24, included at leaf 61680 of 76,334. Version history · verify what your client received.
Compare: most reliable other servers · most reliable data servers · most reliable security servers · most reliable network 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-27 00:26 UTC, the Apished MCP server is up with a Glimind reliability score of 84/100 (grade B). Over the last 30 days it answered 99.4% of Glimind's liveness checks.
Apished MCP server advertises 52 tools, including color_contrast, color_convert, csv_from_json, csv_parse, csv_stats.
Point your MCP client at this streamable-http endpoint: https://apished.com/mcp
Glimind scanned all 52 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.