Vectree
io.vectree/diagrams · 1.0.0
Search and read ~95,000 interactive concept diagrams that explain how things work — visually.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 45 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://vectree.io/mcpstreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 6 tools.
- Protocol
- 2025-03-26
- Calls itself
- vectree 1.0.0
- Handshake time
- 326 ms
- HTTP status
- 200
The tools it lists (6, as of 8 hours ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
get_collectionFetch one Vectree collection: its description and the diagrams it contains, in curated order. A collection is an editor-assembled group of Vectree's labelled schematics around one theme — a book shelf, a system map, a skill tree or a set of deep lore. This tool returns the whole group, so you do not need to fetch the page. Use it after `list_collections`, or whenever you already know a collection slug. Each entry gives a diagram slug you can pass to `get_diagram` to read it in full; an entry marked "still generating" has no readable diagram yet, so skip it. Only published collections can be
get_diagramFetch the full content of one Vectree diagram: every labelled node with its explanation, a step-by-step walkthrough when the diagram is animated, plus image URLs and links to the diagrams its nodes lead to. Vectree explains how things work as zoomable, labelled schematics; this tool returns the complete text of one of them, so you do not need to fetch the page. Use it after `search_diagrams` to read a result in depth, or whenever you already know a Vectree slug. The `Linked diagrams` and `Related diagrams` sections carry slugs you can pass straight back to this tool to walk the graph. Only
get_learning_pathFetch one Vectree learning path: its ordered steps, each naming the diagram that step teaches. A learning path is a curated sequence of Vectree's labelled schematics that works through a subject from the fundamentals upward. This tool returns the whole sequence in order, so you do not need to fetch the page. Use it after `search_learning_paths`, or whenever you already know a path slug. Every step gives a diagram slug you can pass to `get_diagram` to read that step in full; a step marked "still generating" has no readable diagram yet, so skip it. Only published paths can be fetched. Nothing
list_collectionsList Vectree's curated collections — hand-assembled groups of diagrams: book shelves, system maps, skill trees and deep lore. Vectree explains how things work as zoomable, labelled schematics. A collection is an editor-curated set of them around one theme, so it is the best way to see what Vectree covers when you have no specific query yet. Use this to browse, to answer "what is on Vectree?", or to find a themed set of diagrams. When the user already has a topic in mind, use `search_diagrams` instead; when they want an ordered syllabus, use `search_learning_paths`. Every entry carries a slu
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
io.vectree/diagrams, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 40 days ago. The registry entry · vectree.io