MCP.Market

Tirith MCP server

by eabz·io.github.eabz/tirith·v1.2.0·3 stars

Coordination server for parallel coding agents: claims, contracts, notices, and memory notes.

A88/100grade A
What users say
No reviews yet
Be the first
Safety scan
A88/100

full report

Adoption
Growing

3 stars

Reviews

Write one

Nobody has reviewed Tirith yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Tirith tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.10 · 2026-10-02 · same rubric, same numbers if you re-run it

no findings
  • –Code scanpackage could not be scannedn/a
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 8 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Tirith compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
88/100
higher than 75% of 48,255 servers
GitHub stars
3
more than 80% of 28,688 servers

Release history: 2 versions in the registry since 2026-09-18, latest 2026-09-18, typically one every 1 day.

Install Tirith in Claude Code, Cursor or VS Code

The registry entry has no remote endpoint or installable package.

What the publisher says

From the Tirith repository's README, as published. We do not edit it. Read it on GitHub

Tirith

Coordination server for parallel coding agents. Claims, a task board, interface contracts, change notices, a decisions log, path-scoped memory notes, and agent messages, over MCP.

Run five or ten coding agents on one repository and they edit the same files, rename things others depend on, and build both sides of an interface to different shapes. Tirith is a small daemon they all talk to: an agent claims files before editing, gets the notices, contracts, decisions, and notes for those files back with the claim, and publishes the shape of an interface before either side implements it.

It works with anything that speaks MCP, over stdio or HTTP: Claude Code, Cursor, Codex, LangGraph, CrewAI, or a plain script.

It also remembers. Agents leave notes scoped to repository paths, so what one agent learned about a file reaches the next agent that claims it. Tirith stores no conversation history and no embeddings.

Status: v1 shipped. Every primitive, the CLI, persistence, and the

dashboard are built and tested, against the definition in

ADR-0013; tool schemas follow

semantic versioning.

Install

macOS and Linux:

curl -LsSf https://eabz.github.io/tirith/install.sh | sh

Windows (PowerShell):

irm https://eabz.github.io/tirith/install.ps1 | iex

With cargo (the package is tirith-mcp, the binary is tirith):

cargo install tirith-mcp

Already installed? tirith update replaces the binary in place with the latest release. Prebuilt binaries for macOS, Linux, and Windows on x86_64 and ARM64 are on the releases page; every option is in docs/1-about/05-installation.md.

Listed in the MCP Registry: mcp-name: io.github.eabz/tirith.

Quick start

Register tirith stdio with your client, the same way as any other stdio MCP server. It starts the repository's daemon the first time a session needs it, replaces a daemon of another version, and proxies to it after that; nothing has to be started by hand.

The daemon serves MCP at http://127.0.0.1:7477/mcp and a live dashboard at http://127.0.0.1:7477/. State is written to .tirith/ in your repository: contracts, notices, decisions, and memory notes are meant to be committed; .tirith/runtime/ (claims, tasks, messages) is gitignored by a .gitignore Tirith writes itself.

Every agent passes a stable agent name with each call. That is the only convention it has to follow.

What it does

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Tirith: common questions

Is Tirith MCP server safe?
Yes, by our scan: it is graded A (88/100). Read the Tirith safety report
Does Tirith need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Tirith maintained?
The last commit was 41 days ago (2026-09-24). The latest release is v1.2.0.
What can I use instead of Tirith?
Servers from other publishers that do the same job: Deja Vu MCP server.
How does Tirith compare with other MCP servers?
safety score 88/100 (higher than 75% of 48,255 servers); github stars 3 (more than 80% of 28,688 servers). Full comparison.

Alternatives to Tirith

Same job from other publishers: the closest match first, then the best rated.

  • Deja Vu
    deja-vu: local memory over the session histories of forty-three coding agents.
    A