Home / MCP registry index / ai.flyvolo/knowledge
ai.flyvolo/knowledge
ai.flyvolo/knowledge in the official MCP registry.
Endpoint https://mcp.flyvolo.ai/mcp. Source: github.com/weihermans/VOLO.
The registry describes it as: Sourced, task-level facts on how AI changes jobs, for agents answering 'what should I do?'
We read its 19 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
resolve_occupation_or_major search get_occupation get_ontology query_ontology get_role_tasks find_evidence get_change find_affected get_change_history find_transition_paths get_action_brief list_business_functions get_major find_majors_for_occupation find_notes get_note find_notes_for_occupation describe_coverage
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/ai-flyvolo-knowledge)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.