mcp-registry/ai.flyvolo/knowledge · v0.1.0
As of 2026-10-25 17:04 UTC, the Flyvolo Knowledge MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Sourced, task-level facts on how AI changes jobs, for agents answering 'what should I do?'
Claude Code
claude mcp add --transport http flyvolo-knowledge-mcp-server https://mcp.flyvolo.ai/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"flyvolo-knowledge-mcp-server": {
"type": "http",
"url": "https://mcp.flyvolo.ai/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
41 parameter(s) across 19 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 →
19 of 19 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 →
Handshake + tools/list takes ~1,804 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. 19 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fai.flyvolo%2Fknowledge/fixes
{
"name": "describe_coverage",
"description": "What VOLO covers and what it does not: the full list of covered occupations and degrees (slug and name), which occupations have no evidence yet, and the counts. Call this when someone asks whether their job is covered, and whenever resolve_occupation_or_major returns null — then decide from the list which entry, if any, the person means. The answer is a fact about this site rather than a guess about their job.",
"inputSchema": {
"type": "object",
"properties": {
"locale": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "find_affected",
"description": "Which occupation and which specific tasks a change record bears on.",
"inputSchema": {
"type": "object",
"required": [
"id"
],
"properties": {
"id": {
"type": "string"
},
"locale": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "find_evidence",
"description": "Verified evidence records for an occupation, optionally for one task. Each record carries its scope (where it applies), its stage, whether that stage can move a task judgement at all, and its source tier. Repeat the scope rather than smoothing it away.",
"inputSchema": {
"type": "object",
"required": [
"slug"
],
"properties": {
"slug": {
"type": "string"
},
"locale": {
"type": "string"
},
"taskId": {
"type": "string"
}
}
},
"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/ai.flyvolo/knowledge"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/ai.flyvolo/knowledge"}) over MCP.
get_action_brief ~223 tokensquery_ontology ~203 tokensresolve_occupation_or_major ~189 tokensget_ontology ~184 tokensfind_notes ~160 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%2Fai.flyvolo%2Fknowledge?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fai.flyvolo%2Fknowledge?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.flyvolo%2Fknowledge.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.flyvolo%2Fknowledge.svg :target: https://glimind.com/server/mcp-registry%2Fai.flyvolo%2Fknowledge?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:949a0b36760310e0…, first seen 2026-10-18, included at leaf 22596 of 67,386. Version history · verify what your client received.
Compare: most reliable knowledge servers · 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-25 17:04 UTC, the Flyvolo Knowledge MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Flyvolo Knowledge MCP server advertises 19 tools, including describe_coverage, find_affected, find_evidence, find_majors_for_occupation, find_notes.
Point your MCP client at this streamable-http endpoint: https://mcp.flyvolo.ai/mcp
Glimind scanned all 19 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.