Brevet MCP server

Read from the package source without running it. The installed server may list more.

• brevet_acknowledge

  Confirm that this session has stopped applying recalled rules. Call after brevet_active lists them under "recalled", with their recall ids. Each confirmation is recorded on the evidence chain as the MCP serving point's acknowledgement of that recall.

• brevet_active

  Return the governed rules of the latest signed release, checked before they are served: the evidence chain must replay intact and match its anchors, the lock must match the digest the chain recorded for that release, the release signature must verify, and each rule's content and conditions must match what was released. Call at session start and follow every rule returned, within its conditions. To

• brevet_anchorwrite action

  Write the evidence chain's current head to the anchors configured for this workspace (outside it), so a chain later cut short, rewritten or replaced is detected. Anchoring also happens after every governing step; call this to anchor recent evidence as well.

• brevet_chap_ingest

  Import CHAP review verdicts as evidence: overrides (diff, rationale and intent_preserved carried through verbatim), rejections (substituting judgments) and approvals (accepted as they were). CHAP is the capture surface; Brevet remains the learning gate. Importing creates evidence only and grants no authority. ``source`` is an audit JSONL file or folder, a coordinator SQLite ``.db`` file, or a serv

• brevet_dawn_decide

  Apply one dawn-gate decision: promote, hold, reject or re_elicit. The approver must be human:<who> or mission_group:<name>; promotion to the controlled layer needs a mission group. Run only on the user's explicit instruction, with the identity the user gives. When the workspace requires signed approvals, this returns a request for the user to sign.

• brevet_dawn_pending

  List the candidates awaiting a dawn decision: id, kind, recurrence and title. Eval cases appear too, because their labels can be wrong.

• brevet_dreamwrite action

  Run the dream cycle: group recurring overrides into Evidence-layer candidate capabilities and compile eval cases from them. Only what is new is added, and only from the overrides of participants who consented. Candidates have no authority until a human promotes them.

• brevet_harness

  Show the harness the latest release locked (files, agent components and library versions, as digests) and which declared harness files changed since, such as an edited prompt or a new skill. A change that is not released is not under change control: tell the user.

• brevet_recall

  Recall a capability: withdraw it, flag every release whose lockfile contains it, and append the recall notice to the evidence chain. reason_class is one of incorrect, unsafe, consent_withdrawn, superseded, stale, compliance, duplicate or other (duplicate withdraws one byte-identical copy and leaves the content to the copy that stays; every other reason withdraws the content wherever it appears); s

• brevet_record

  Record one completed task as evidence: the agent's draft and the expert's final (the version actually used). An empty final, or one identical to the draft, means the draft was accepted as it was. The participant is the human who made the correction and defaults to the workspace owner named in the manifest. Recording creates evidence only; it grants no authority.

• brevet_release

  Resolve promoted capabilities into capabilities.lock, sign the manifest (Ed25519, covering the lock's digest) and record the release. Trial and production releases need the conservative gate to pass. Give eval_before and eval_after (eval run references) to bind the release to measured runs, whose deltas are then used; otherwise the deltas given here are recorded as attested by the approver, which

• brevet_rollback

  Return the agent to an earlier release as a new signed release: its manifest and harness files come back, and its capabilities minus any recalled or decided against since. Run only on the user's explicit instruction, with the identity the user gives. When the workspace requires signed approvals, this returns a request for the user to sign. Harness files added since that release block the rollback

• brevet_status

  Agent status: version, channel, active capabilities by authority layer, recalled capabilities, the dawn queue and evidence-chain integrity.

• brevet_verify

  Replay the hash-linked evidence chain, check it against the heads anchored outside the workspace (a chain cut short, rewritten or replaced fails), and check every approval signature on it.

• Code scan35 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 6 days ago15/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10

Safety score

94/100

higher than 96% of 48,255 servers

Tools

14

the typical server has 7

Tools that change things

14%

typical: 0%. Fewer write tools means less an agent can break

GitHub stars

1

more than 65% of 28,688 servers

Downloads a week

326

more than 82% of 12,191 servers with a package

Brevet: common questions

Is Brevet MCP server safe?

Yes, by our scan: it is graded A (94/100). Read the Brevet safety report

How do I install Brevet?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Brevet need an API key?

No secret keys are declared. It reads 2 settings from the environment.

Is Brevet maintained?

The last commit was 28 days ago (2026-10-07). The latest release is v0.4.0.

How does Brevet compare with other MCP servers?

safety score 94/100 (higher than 96% of 48,255 servers); tools 14 (the typical server has 7); tools that change things 14% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.