mcp-registry/io.github.dimabalony/whentofly · v1.0.3
Also listed as glama/dimabalony/whentofly, mcp-registry/io.github.dimabalony/flights · primary listing: mcp-registry/io.github.dimabalony/flights
As of 2026-10-19 12:24 UTC, the Dimabalony Whentofly MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 70.3% of Glimind's liveness checks. It had 420 outages in 90 days, with a median recovery of 8 minutes.
whentofly: flexible-date economy/business flight search + price-level context for AI agents
Point your MCP client at this streamable-http endpoint: https://whentofly.io/mcp?ch=mcp-registry
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 →
Reachable 70.3% of the time over the last 30 days; median recovery 8 min.
Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.
1 tool definition(s) exceed ~1,200 tokens each (largest: search_flights, ~1,967).
Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~1,367 tokens every session. How to fix →
1 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 →
Handshake + tools/list takes ~2,391 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 →
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.dimabalony/whentofly"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.dimabalony/whentofly"}) over MCP.
search_flights ~1,967 tokenssearch_locations ~189 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.dimabalony%2Fwhentofly?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.dimabalony%2Fwhentofly?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.dimabalony%2Fwhentofly.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.dimabalony%2Fwhentofly.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.dimabalony%2Fwhentofly?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:a8a3f13155406166…, first seen 2026-10-17, included at leaf 506 of 51,641. Version history · verify what your client received.
Compare: most reliable search 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 12:24 UTC, the Dimabalony Whentofly MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 70.3% of Glimind's liveness checks. It had 420 outages in 90 days, with a median recovery of 8 minutes.
Dimabalony Whentofly MCP server advertises 2 tools, including search_flights, search_locations.
Point your MCP client at this streamable-http endpoint: https://whentofly.io/mcp?ch=mcp-registry
Glimind scanned all 2 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.