MCP server for dossier automation standard - enables LLMs to discover, verify, and execute dossiers
Nothing to run from here
Tirith is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
99/100
trust score
22
tools declared
local
runs on your machine
182
downloads
What it does
Coordination server for parallel coding agents: claims, contracts, notices, and memory notes.
Quickstart
This one is not published to a package registry, so there is no one-line install: it is built and started the way its own source says.
Publishernot claimed
EAAll 1 server
eabz1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Tirith as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This one is not published to a package registry, so there is no one-line install: it is built and started the way its own source says.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Claim paths (a directory covers its contents) before editing, atomically; ok briefs notices, contracts, decisions, memory. ttl_secs 600, max 3600. wait_secs max 120: waits out conflicts.
No parameter schema on file.
Release paths, or everything you hold when paths is omitted.
No parameter schema on file.
Extend every lease you hold.
No parameter schema on file.
Your live claims plus any overlapping path; all=true for every claim. Newest first, paged.
No parameter schema on file.
Add a todo task; depends_on ids must be done before it can be pulled; higher priority pulls first.
No parameter schema on file.
Take the highest-priority unblocked todo task as in_progress. wait_secs max 120: waits out claims and dependencies.
No parameter schema on file.
Set status (todo|in_progress|blocked|done) with an optional note; another agent's in_progress task is a conflict unless force.
No parameter schema on file.
List tasks by status and owner, most recently updated first, paged.
No parameter schema on file.
Publish an interface shape (kind: http|function|type|event|cli|other). Republish: new version, consumers kept unless given, conflict on stale expected_version.
No parameter schema on file.
Fetch a contract by name or id, with its versions.
No parameter schema on file.
List contracts by consumer path or kind, newest first, paged.
No parameter schema on file.
Announce a change (kind: rename|signature|removed|moved|behavior) and the affected_paths that must react.
No parameter schema on file.
List change notices by path, since (RFC 3339), or unread only, newest first, paged. Unread without a path covers the paths you hold unless all=true.
No parameter schema on file.
Record a settled choice with its rationale, alternatives, and the paths it affects.
No parameter schema on file.
List decisions by path or text query, newest first, paged.
No parameter schema on file.
Counts, persistence and load problems; verbose=true adds who holds what.
No parameter schema on file.
Write a durable note (kind: fact|lesson|gotcha|handoff|research|note); an existing title updates it.
No parameter schema on file.
Read a note by permalink, id, or title; depth (0 to 3) adds related notes.
No parameter schema on file.
Search notes, best first; no query lists the newest. limit: default 10, max 50.
No parameter schema on file.
Delete a memory note by permalink, id, or exact title. Its file is removed.
No parameter schema on file.
Message an agent (to: name, * for all active, human for the human queue); delivered on their next call. text: max 1000 chars.
No parameter schema on file.
List your messages, newest first; filter by with, since, unread.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Tirith or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 99 / 100
Release 1.2.0 · scanned 15 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score99
Findings2 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digest2dc22d3bf39daa3966da07121ef3ae7218597d0cc75600bd6ac9471b4c82a657
Score vectorthreat 100 → client 99
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
No tool surface was enumerated, so there is nothing to attribute a capability to.
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest2dc22d3bf39daa39
Scanned2026-10-15
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
It installs from its repository rather than from a versioned package, so the command cannot be pinned to a release. The history below is for reading; the current release on file is 1.2.0.
1.2.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Tirith can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.