Knowledge is answering right now. Last checked 2 min ago. It exposes 16 tools.
Evidence-graded, task-level record of how AI and automation change 70 occupations. Read-only.
The linked repository no longer exists on GitHub — it was deleted or made private.
Uptime history
5 days of history
5 days agonow
100.0%
Uptime 24h
92 of 92 checks
16
Tools
read from the server
397 ms
Response time
average over 24h
open, no key
Access
streamable-http
This one has been quiet for a while
Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.
run in your terminal
claude mcp add knowledge --transport http https://mcp.flyvolo.ai/mcp~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"knowledge": {
"url": "https://mcp.flyvolo.ai/mcp"
}
}
}~/.codex/config.toml
[mcp_servers.knowledge]
url = "https://mcp.flyvolo.ai/mcp".cursor/mcp.json
{
"mcpServers": {
"knowledge": {
"url": "https://mcp.flyvolo.ai/mcp"
}
}
}.vscode/mcp.json
{
"mcpServers": {
"knowledge": {
"url": "https://mcp.flyvolo.ai/mcp"
}
}
}Available tools 16
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
change
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.
get_change_history
The verified change timeline for an occupation, oldest first.
notes
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 about the whole picture rather than one occupation: those are exactly the questions you can answer fluently without evidence, and these notes are the evidence. Each result carries the note's own limits.
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.
affected
find_affected
Which occupation and which specific tasks a change record bears on.
business
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.
describe
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.
evidence
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 smoothing it away.
major
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.
majors
find_majors_for_occupation
Which degrees lead into this occupation.
note
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.
occupation
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 confidence and assessment date.
resolve
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, say which entity you read the question as. Returns null when VOLO does not cover it, which is a gap in this site and not a statement about the job.
role
get_role_tasks
The task breakdown for one occupation. The unit of assessment is the task, never the job title.
search
search
Search occupations, majors and verified change records by keyword. Returns entries, not judgements.
transition
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.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://mcp.flyvolo.ai/mcp | streamable-http | answering | 434 ms | 2 min ago |
Alternatives to Knowledge
same job, measured the same wayOswright
by ask-812
Windows desktop automation that re-reads only what changed: 7x fewer tokens per task.
Bitsbound Contract Automation
by taytrom
AI contract automation with partner-level redlines, OOXML Track Changes, and risk analysis.
Contract Automation
by bitsbound
AI contract automation with partner-level redlines, OOXML Track Changes, and risk analysis.
Mindwtr
by dongdongbh
Task and project automation for local and self-hosted Mindwtr Cloud data; read-only by default.
Charles Local MCP
by eason0in
Guarded local Charles Proxy automation and bounded XML session evidence
BLEA
by nitmi
Safe BLE diagnostics, evidence workflows, and guarded automation for AI agents.
Raza SOR
by razarizwan
Raza Rizwan's record: ask how much of your workflow AI can automate; governed, cited answers.
TextMine MCP
by textmine
Search, read, and automate TextMine documents, records, workflows, integrations, and agent tasks.
Knowledge — questions
Answers built from our own checks of this server.
What can Knowledge do?
It exposes 16 tools, read directly from the server on our last check. Among them: describe_coverage, find_affected, find_evidence, find_majors_for_occupation, find_notes, find_notes_for_occupation and 10 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
What is Knowledge mostly used for?
Its tools cluster around change and notes. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Knowledge working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 397 ms. The bar chart above shows every period we have measured.
Is Knowledge still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect Knowledge?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Knowledge need an API key?
No. Knowledge completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 16 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Knowledge?
It answers our handshake in 397 ms on average, which is faster than 38% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.