MCP Server for ZenTao bug management with CAS SSO login
from $14/mo
Nothing to run from here
Derive 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.
Open Installation—
p95 latency
—
call success
local
runs on your machine
—
calls last 7d
What it does
Derive — MCP server and CLI for autonomous systems engineering. 27 tools: project overview, requirements CRUD, trace links, quality gates, ISO 15289 reports, SysML v2 export, hazard registers, knowledge graph, diagrams, baselines, and verification matrix.
Quickstart
# 1 — run it from where its publisher ships it
npx -y derive-mcp
# 2 — ask your agent something
> Derive — MCP server and CLI for autonomous systems engineering. 27 tools: project overview, requirements CRUD, trace links, quality gates
Derive is free: there is no plan to choose, no cap to set and nothing that can bill you.
Publishernot claimed
AIAll 1 server
airgen-studio1 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 Derive 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. It is scanned, signed and pinned to the version you choose — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add derive-mcp -- npx -y derive-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free to install, and it runs from its publisher’s own package: no account, no key, no card.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
26 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List all architecture diagrams for a project with IDs, names, and views
Takes no parameters.
Example callreturns →
Render an architecture diagram as Mermaid syntax
Takes no parameters.
Example callreturns →
Get current harness operational state: active project, flow state, session count, last session info, live session status, loop status
Takes no parameters.
Example callreturns →
Get the state machine definition: states with labels, transitions with guards, flows, and priorities
Takes no parameters.
Example callreturns →
List recent autonomous session journal entries with date, title, session number, task class, and excerpt
Takes no parameters.
Example callreturns →
Get the full markdown content of a journal entry
Takes no parameters.
Example callreturns →
List classified entities in a project
Takes no parameters.
Example callreturns →
Query the knowledge graph. Predicates: PART_OF, CONNECTS, PRODUCES, HAS_STAKEHOLDER, HAS_CONSTRAINT, INTERFACES_WITH, HAS_HAZARD, HAS_MISSION, HAS_MODE, HAS_SCENARIO, SPEC_TREE, RED_TEAM_FINDING
Takes no parameters.
Example callreturns →
Get the hazard register with linked requirements for each hazard. Shows which requirements mitigate each hazard based on SIL tags and rationale references.
Takes no parameters.
Example callreturns →
List all systems engineering projects with slug, name, requirement count, and status
Takes no parameters.
Example callreturns →
Compare all SE projects: requirement counts, trace coverage, orphan counts, and quality gate status across the entire portfolio. Use this to find the best/worst projects or identify patterns.
Takes no parameters.
Example callreturns →
Get project summary: requirement counts by document type, decomposition tree, subsystems, standards, diagrams with IDs, quality gate status. Does NOT return full requirement text.
Takes no parameters.
Example callreturns →
Comprehensive single-call project review: overview + quality gates + all high-severity lint findings + orphan requirements with document type + hazard register + diagrams + recent journal entries. Best starting point for reviewing a project.
Takes no parameters.
Example callreturns →
Import a local document (PDF, DOCX, MD, TXT) into a project. Extracts text, runs Claude to identify requirements/stakeholders/hazards, and stores as Substrate facts for the concept flow to consume. Creates the project if it doesn
Takes no parameters.
Example callreturns →
Run semantic requirements lint. Returns findings with severity, affected requirement ref, finding type, and description. Supports filtering by severity and document type.
Takes no parameters.
Example callreturns →
Evaluate quality gates (isFirstPassComplete, isQCPassed, isValidated) for a specific project. Shows each metric vs its threshold.
Takes no parameters.
Example callreturns →
Generate SysML v2 textual notation (.sysml) for a Derive project. Maps requirements, trace links, PART_OF hierarchy, connections, modes, hazards, and constraints to valid SysML v2 constructs. Returns the full .sysml text and line/construct counts.
Takes no parameters.
Example callreturns →
Get paginated requirements for a project, optionally filtered by document type (stakeholder-requirements, system-requirements, subsystem-requirements, interface-requirements, architecture-decisions, verification-requirements)
Takes no parameters.
Example callreturns →
Get full detail of a single requirement including all trace links to/from it
Takes no parameters.
Example callreturns →
Full-text search across requirement text and rationale. Returns up to 30 matches.
Takes no parameters.
Example callreturns →
Get trace link summary and first 100 links. Shows coverage statistics and structural gaps (groups of requirements missing derivation/verification links).
Takes no parameters.
Example callreturns →
Find requirements with no trace links. Includes document type for severity assessment (STK orphans are critical, SUB orphans less so).
Takes no parameters.
Example callreturns →
Compare two baselines to see what changed between them — added, removed, and modified requirements. Uses airgen diff (v0.21.0+).
Takes no parameters.
Example callreturns →
List all baselines (snapshots) for a project with refs and dates.
Takes no parameters.
Example callreturns →
Get the verification cross-reference matrix — shows which requirements are verified, by what method, and coverage gaps.
Takes no parameters.
Example callreturns →
Get project activity timeline — recent changes to requirements, trace links, and baselines.
Takes no parameters.
Example callreturns →
Freeyour plan
$0 forever
- Every tool, no call limit
- No card, no account needed
- Source published under a licence you can read
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because nothing bills
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable. Derive costs nothing to install and nothing to call, 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: $8.42
$16.58 left
BTrust score 87 / 100
Release 0.3.0 · scanned 26 Aug 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 score94
Client score87
Findings1 threat · 5 capability
Capabilityhigh
Coveragesource
Verificationrepo
Surface digestf350fcc576f804b60dcf5ad5f97ba52810ff492648c424898139789013a8e05a
Score vectorthreat 94 → client 87
| Term | Level | What it prices | Points |
|---|---|---|---|
| −6.3 | |||
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| 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 surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (2 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, 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. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| SE Projects | no tags | |
| Harness State | no tags |
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 digestf350fcc576f804b6
Scanned2026-08-26
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
Pinned to 0.3.0 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
0.3.0
undated
installedNo release note was published with this version.
—
no reviews yet
Reviews are earned
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Reviews are earned
Writing one takes an account with at least 50 real tool calls against Derive in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
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 an account with 50 real tool calls against it.