Not reviewed
No score, grade or rank. This listing is facts from the official MCP registry and our own checks, and it stays out of the rankings until the panel reviews it.
Give your AI agent a persistent map of your project's structure, dependencies, and bugs.
Facts
- MCP registry
io.umtri/umtri· 1.7.1- Endpoint
https://mcp.umtri.io- Packages
npmumtri-mcp stdio- Website
- docs.umtri.io
- npm / week
- 500
- GitHub stars
- 0
- Registry entry
- updated 6 Nov 2026
From the official MCP registry, the package registries and our own checks. JSON · Markdown
Why it's listed
- It's published in the registry under umtri.io, a namespace the registry only gives to whoever proves they control that domain.
Being indexed says nothing about quality, and nobody can pay for it. Is this yours? Ask for a review.
Tools it lists 32 · about 15,625 tokens of context · checked 18 hours ago
| Tool | What it does | Hint |
|---|---|---|
list_projectsList grounds (projects) | Returns all grounds the authenticated user can access, with latest activity timestamp. Use this first to discover slugs for other tools. By default returns a summary view — each ground carries slug, name, isActive,… | |
get_graphGet the graph of a ground | Returns the tree(nodes), edges, apis, seasons, and bugs for one ground. The tree is the project's information-structure (IA) diagram — each node is a structural element (an object, or an action it performs), not a… | |
get_impactTrace the blast radius of a node or bug | Walks the connection graph (edges + apis) from a start node — or a bug's target — to find which other nodes a problem would reach. This is the tool for "if this breaks / I change this, what else do I need to check?" and… | |
list_bugs | (not repeated here: it reads like a rating or a usage claim) | |
get_bugGet one bug of a ground | Returns a single bug by reference — the cheap path when you already know which bug you mean. `ref` accepts either the human-facing number shown in the UI (seq — "14" or #14) or the internal id (bug-<uuid>), so a human… | |
list_seasonsList seasons of a ground | Returns the seasons (time epochs) of a ground in chronological order. A season is the human's declaration that a chapter closed. You may create one with create_season, but only after the user confirms it — see… | |
export_groundExport a whole ground as JSON | Returns everything in a ground as one JSON document — project, seasons, nodes (removed ones included, with removedAt), edges, apis, bugs and wiki pages with full bodies. For backups, moving off Umtri, or answering "can… | |
list_eventsList change history of a ground | Returns the append-only change history (most recent first) of a ground: node/edge/api/bug create, update (with a field-level diff {from,to}), delete, and plan_commit. Each event carries the actor ("user:<id>" for… | |
create_bugReport a bug on a ground | Creates a new bug (issue eroding the target). target.kind = "node" or "api" requires target.id of an existing node/api in the ground. target.kind = "ground" attaches the bug to the project itself (no id). score = change… | |
create_projectCreate a new ground (project) | Creates a new ground. Slug must match /^[a-z0-9][a-z0-9-]{0,49}$/ and be unique. By default it goes into the authenticated user's personal space; pass org (a team slug, as list_projects shows it) to create it in a team… | |
create_seasonCreate a new season | Creates a new season and makes it the "now" season. This is not an additive act: the ground's current now-season is sealed as past and every node in it is marked grown, which locks that node's… | |
create_nodeCreate a node in a ground | Creates a node. Follows the plant vocabulary protocol — see umtri://rules/vocabulary. type ∈ trunk · limb · twig · leaf · vein. Role is derived (structure / object / action). Build leaf-first: when adding a leaf/vein,… | |
update_nodeUpdate a node | Partial update of a node. Patchable fields: label, type, parent, season, description, tags, metadata, sproutedAt. metadata is merged key by key: only the keys you send change, keys you leave out (commits that… | |
delete_nodeSoft-delete a node | Sets removed_at on the node. By default this tool rejects deletion if the node has any active descendant, so a subtree is never lost silently. To soft-delete the node together with all its active descendants, pass… | |
commit_planCommit a realized plan node | Promotes a plan node (metadata.plan=true) to the real tree by clearing the plan flag. VERIFICATION GATE: the node must already carry metadata.implements (the source path(s) you wrote) — without it the commit is… | |
record_commitRecord a git commit onto the nodes it touched | Configuration record (CI/CD). Given a commit SHA and the files it changed, finds nodes whose metadata.implements include any of those files and appends the commit (sha + timestamp + optional message) to their… | |
create_edgeCreate an edge between two nodes | Creates a directed edge (source → target) for a STRUCTURAL relation: type "dependency" (A is built on / needs B) or "data_flow" (data moves A → B outside a request). Use for module/library deps, a route depending on the… | |
delete_edgeDelete an edge | Removes an edge from the ground. Use to retire dependencies/flows that no longer reflect reality. | |
create_apiCreate an API flow between two nodes | Records an API flow (start → end) for a RUNTIME request / call / data flow: a screen calling an endpoint, an endpoint hitting a table, an external integration (payment, SMS, webhook). Direction is caller → callee. APIs… | |
update_apiUpdate an API entry | Partial update of an API. Patchable fields: label, description, metadata, start, end. | |
delete_apiSoft-delete an API entry | Sets removed_at on the API. History is preserved — the API can still be seen in past season views via the time slider. | |
update_bugUpdate a bug | Partial update of a bug. Most common use: status transition. Send only the fields that actually change. A status transition is patch:{status} alone — do not re-send an unchanged solution, description, or metadata. Those… | |
delete_bugDelete a bug (hard delete) | Permanently removes a bug record. Bugs do not have history — once deleted, the record is gone. For "I resolved this", use update_bug with status="resolved" instead, so the tree remembers what was eroded. | |
send_feedbackSend feedback about Umtri itself | Files a suggestion or a defect report about **Umtri the product** — this MCP server, its tools, the app, the docs. This is NOT for issues in the user's own project: those are bugs on a ground (create_bug). Call this… | |
list_feedbackList feedback filed about Umtri | Lists feedback filed about **Umtri the product** (see send_feedback) — not the bugs of any ground. Umtri operators only: every other account gets 403, so do not call this to check on feedback you filed. Newest first.… | |
update_feedbackUpdate filed feedback | Updates one feedback record about **Umtri the product** — typically closing it: status="done" once it shipped, or "wontfix" when it was declined. Put what was actually done (or why not) in note; that is the part worth… | |
list_wikiList wiki pages of a ground | Lists the ground's wiki — the prose the tree cannot hold: conventions, decisions and why they were made, glossary, onboarding. Reference entries describing how things work, not a log of what happened: the change record… | |
get_wikiRead one wiki page — in full, as an outline, one section, or the lines around a phrase | Returns one wiki page. `ref` takes either the page slug (what a human says) or the internal id (wiki-<uuid>) — renaming a page changes its slug but never its id, so ids stay safe to store. Every response carries rev… | |
list_wiki_revisionsList the revision history of a wiki page | Returns what this page said before, newest first — rev number, who wrote it, when, and the body length. Bodies are not included (a history of twenty full documents is expensive to skim); read one with get_wiki rev=<n>.… | |
write_wikiCreate or update a wiki page | Writes one wiki page. Creates it if the page slug is new, updates it otherwise — you do not need to check first. **The wiki is the project's encyclopedia: one page is one entry, and its body is the current spec and… | |
edit_wikiChange one passage of a wiki page | Replaces one passage of an existing wiki page without resending the body. Pass the exact text to replace (oldString) and what it becomes (newString) — the same contract as a code editor's Edit: oldString must occur… | |
delete_wikiDelete a wiki page | Permanently removes a wiki page **and its whole revision history** — unlike an overwrite, this cannot be undone, and only the history entry (list_events) remains to say it happened. Prefer rewriting a page that went… |
What https://mcp.umtri.io answered to tools/list, asked without credentials over MCP 2025-11-25. The token figure is the size of the list as sent, divided by four; a model sees about that much before it calls anything. Full definitions, input schemas included, are in the listing's JSON under mcpTools.
How its tools read to an agent 0 errors · 49 warnings · 1 note
- warnTC07create_nodethe description is about 597 tokens
- warnTC07get_graphthe description is about 743 tokens
- warnTC07write_wikithe description is about 1,322 tokens
- warnTC11create_api3 parameters without a description: description, label, metadata
- warnTC11create_edge2 parameters without a description: label, metadata
- warnTC11create_node2 parameters without a description: description, tags
- warnTC11create_project1 parameter without a description: description
- warnTC11delete_apinone of its 2 parameters has a description
- warnTC11delete_bugnone of its 2 parameters has a description
- warnTC11list_wiki1 parameter without a description: limit
- warnTC11list_wiki_revisions1 parameter without a description: limit
- warnTC11update_apinone of its 3 parameters has a description
- warnTC11update_bugnone of its 3 parameters has a description
- warnTC11update_feedback4 parameters without a description: body, kind, source, title
- warnTC14create_edgeallowed values are in the description, not an enum: type
- warnTC16commit_planno readOnlyHint or destructiveHint
- warnTC16create_apino readOnlyHint or destructiveHint
- warnTC16create_bugno readOnlyHint or destructiveHint
- warnTC16create_edgeno readOnlyHint or destructiveHint
- warnTC16create_nodeno readOnlyHint or destructiveHint
- warnTC16create_projectno readOnlyHint or destructiveHint
- warnTC16create_seasonno readOnlyHint or destructiveHint
- warnTC16delete_apino readOnlyHint or destructiveHint
- warnTC16delete_bugno readOnlyHint or destructiveHint
The first 24 of 50; every finding is in the listing's JSON under mcpTools.check.
The checks from /check and anchor check, run each day on the list above: about 15,625 tokens of definitions. Not part of the score yet. Check your own server.