Skip to content
VOLO logo

VOLO MCP server

Which servers in the official MCP registry are VOLO's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-17

← Back to VOLO

Whose server it is
  • Registry nameai.flyvolo/knowledgeverified in the MCP registry

The registry name sits under flyvolo.ai. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-17
  • Stateanswerschecked 2026-10-17
  • Tools19
  • Server calls itselfvolo-knowledge
  • Server version0.1.0
  • Protocol version2025-06-18

On 2026-10-17 the server answered initialize and tools/list without a sign-in. First answer in 1317 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 3 of the 7 days it takes to judge reliability.

Once connected

  • Parameters are untyped or undescribed in 19 of 19 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 3, the first on 2026-10-19
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
  • Answeredmeasuring3 of the 7 daily checks it takes to print a share
  • Median first answer2153 ms
  • Space in an agent's context≈ 2,231 tokensthe definitions of all its tools (19), which an agent carries on every turn
  • Tool definitionsC · 67 of 100
  • Typed results0 of 19 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 19 of 19
  • Not saying whether it only reads or can destroy: 19 of 19

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers19 tools · read 2026-10-17
  • 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.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "knowledge": {
      "type": "http",
      "url": "https://mcp.flyvolo.ai/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http flyvolo https://mcp.flyvolo.ai/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://mcp.flyvolo.ai/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.