Servidor MCP de VOLO

• Nombre en el registroai.flyvolo/knowledgeverificado en el registro MCP

El nombre en el registro está bajo flyvolo.ai. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

• Estadorespondecomprobado el 2026-10-17
• Herramientas19
• El servidor se llamavolo-knowledge
• Versión del servidor0.1.0
• Versión del protocolo2025-06-18

El 2026-10-17 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 1317 ms.

• Aún no se ha juzgado si sus herramientas hacen el trabajo del producto.
• Comprobado 3 de los 7 días necesarios para juzgar su fiabilidad.

Lo dicen reglas a partir de las mediciones de arriba. La primera llamada probable la elige un modelo de la lista de herramientas; lee su descripción antes de fiarte.

• Nota INITE MCPtras una semanala nota necesita 7 comprobaciones diarias: 3 hasta ahora
• Respondiómidiendo3 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
• Mediana de la primera respuesta2153 ms
• Espacio en el contexto del agente≈ 2231 tokenslas definiciones de todas sus herramientas (19), que el agente lleva en cada turno
• Definiciones de herramientasC · 67 de 100
• Resultados tipados0 de 19 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez

• Parámetros sin descripción: en 19 de 19
• Sin indicar si solo lee o puede destruir: 19 de 19

Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. La nota pondera solo lo medido: si responde (30%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%) y uso (15%). Lo que no se midió queda fuera, y una instrucción oculta limita la nota a 40. El estado de los servidores MCP de los proveedores: método y números →

• resolve_occupation_or_major

  Resolve a job title, a company's internal name for a role, a nickname or a degree name to a canonical VOLO entity. Call this FIRST whenever a person names their job. Returns a match field of exact or approximate — when it is approximate…

• search

  Search occupations, majors and verified change records by keyword. Returns entries, not judgements.

• get_occupation

  Full task-level assessment of one occupation. Every task carries direction, basis (evidenced vs inferred) and limits — what that judgement does NOT establish. The impact index is not a probability of job loss and never appears without its…

• get_ontology

  Where an occupation or a degree sits in the official classifications (U.S. Department of Labor O*NET 31.0; U.S. Department of Education CIP–SOC crosswalk; the EU's ESCO, the ILO's ISCO-08 and Singapore's SSOC 2024): the matching codes…

• query_ontology

  Walk the VOLO Ontology directly. No arguments: the object types and link types. `type`: the objects of that type. `type` + `id`: one object's properties and everything it links to, grouped by link. Add `link` (and `direction`: out|in) to…

• get_role_tasks

  The task breakdown for one occupation. The unit of assessment is the task, never the job title.

• find_evidence

  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…

• get_change

  One verified change record by id, with VOLO's reading: what it means, what it does not yet establish, and what a reader can verify themselves.

• find_affected

  Which occupation and which specific tasks a change record bears on.

• get_change_history

  The verified change timeline for an occupation, oldest first.

• find_transition_paths

  Options for someone in this occupation. Every path carries its real constraints (time, pay cut, seniority) and one action they can take this week that produces information. Never present a path without its constraint.

• get_action_brief

  Use this when a person asks what they should do about AI or automation in their job ("I'm an accountant, how do I stay employable?"). One call returns, task by task: where the task is heading and how strong the evidence is; which laws…

• list_business_functions

  For the business side: the functions a company is organised into, and which occupations sit in each. Use this when someone describes a company rather than themselves.

• get_major

  A degree and the occupations it feeds. There is no score for a major and never will be — answer 'should I switch majors' by pointing at where it leads and what transfers.

• find_majors_for_occupation

  Which degrees lead into this occupation.

• find_notes

  VOLO's long-form answers to the big questions — how many jobs AI has actually taken, what actually gets automated, how long someone has, what AI law already changed, where AI lands in a company. Call this FIRST for any question that is…

• get_note

  The full text of one note, section by section, each section with the verified records it rests on. Use it when you need to quote or cite rather than summarise.

• find_notes_for_occupation

  Which notes argue from this occupation's own records or task judgements. Use it to point someone from their own page to the wider answer.

• describe_coverage

  What VOLO covers and what it does not, including which occupations have no evidence yet. Call this when someone asks whether their job is covered, so the answer is a fact about this site rather than a guess about their job.