tieline MCP server
Static FE-BE contract-drift checker: finds frontend calls the backend does not expose. CLI + MCP.
0 stars52 downloads/wk
Reviews
Write oneNobody has reviewed tieline yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
tieline tools (5, 1 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
tieline_checkwrite actionRun the static frontend↔backend contract-drift check. Returns totals plus the
tieline_doctorDiff routes parsed from source code (a native server adapter) against the routes
tieline_initAuto-detect nearby repos (frontend + backend stacks) and write a tieline.config.json.
tieline_listReturn the full resolved contract map: every frontend endpoint with its status
tieline_orphansList backend routes that no resolvable frontend call reaches (dead/unused routes).
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- Code scan26 source files scanned25/25
- –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 109 days ago8/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How tieline compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 82/100
- higher than 63% of 48,255 servers
- Tools
- 5
- the typical server has 7
- Tools that change things
- 20%
- typical: 0%. Fewer write tools means less an agent can break
- Downloads a week
- 52
- more than 43% of 12,191 servers with a package
What its tools let an agent do: 4 read · 1 change
Install tieline in Claude Code, Cursor or VS Code
Runs npx -y @nugehs/tieline on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add tieline -- npx -y @nugehs/tieline
What the publisher says
From the tieline repository's README, as published. We do not edit it. Read it on GitHub
tieline
Static frontend↔backend contract-drift checker. Pact without writing a single contract test.
tieline reads the code you already wrote on both sides of an API boundary — the HTTP calls your frontend makes and the routes your backend exposes — and tells you where they disagree. No contract tests to author, no broker to run, no backend to boot. It finishes in well under a second and is built to run in CI as a gate.
Delete the LLM and a developer still installs it. tieline is a deterministic
tool first; an agent reading its output is a bonus.
How it works
frontend code backend code
(axios, rtk-query, …) (express, nestjs, openapi, …)
│ │
client adapter server adapter
│ normalize ${id} :id {id} → {} │
└───────────────► join on (METHOD, path) ◄──────┘
│
✅ matched ❌ drift ⚠️ unverifiable 🟡 deadBoth sides are reduced to a canonical (METHOD, path) and joined. The matcher is adapter-agnostic — any client adapter pairs with any server adapter, so the same engine checks a React app against Express, an Angular app against Spring, or anything against an OpenAPI spec.
tieline vs alternatives
These tools solve neighbouring problems — pick by what you have and what you want guaranteed.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
tieline: common questions
- Is tieline MCP server safe?
- Mostly: it is graded B (82/100). Read the tieline safety report
- How do I install tieline?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does tieline need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is tieline maintained?
- The last commit was 147 days ago (2026-06-10). The latest release is v0.1.4.
- How does tieline compare with other MCP servers?
- safety score 82/100 (higher than 63% of 48,255 servers); tools 5 (the typical server has 7); tools that change things 20% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.