capital.new mandate draft tools

new.capitalPublished by capital.newOfficial publisherv0.1.0Updated Oct 27, 2026

Verify Capital Authority Mandate drafts (SHA-256 replay) + v0 schema. Ceremonies stay human.

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Lets an assistant build and verify Capital Authority Mandate draft files by replaying their SHA-256 digest, while minting stays a human ceremony.

What you can do
  • Verify a mandate draft by recomputing its SHA-256 digest and comparing it to the digest embedded in the file.
  • Retrieve the v1 (and v0) draft template, the never-delegable act list and the digest convention so a draft can be constructed.
  • Look up where and how a draft becomes an instrument, including that minting and revocation are human ceremonies.
When to use it
Use it when an assistant needs to prepare a Capital Authority Mandate draft for a principal to mint, or to check that an existing draft file is internally consistent before it is handed to a counterparty.
Requirements
A remote streamable HTTP endpoint at capital.new; no packages, environment variables or headers are declared. No authentication is declared.
Before you install
Verification only proves the file is unaltered since its own digest was taken; it does not prove the mandate was minted or that its caps are valid. Minting and revocation happen only through human ceremonies at capital.new, and v1 has no signing rail, so drafts are not signed credentials.

Installation

In SourceWeft

  1. Open capital.new mandate draft tools in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/new.capital%2Fmandate-tools/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "capital-new-mandate-draft-tools": {
      "type": "http",
      "url": "https://capital.new/mcp"
    }
  }
}

Tools

3

mandate_draft_verify

Verify a mandate draft digest

Recomputes the SHA-256 digest of a Capital Authority Mandate draft and compares it to the digest embedded in the file — the same replay any counterparty would run. Establishes that the file is internally consistent (unaltered since its own digest was taken), NOT that it was minted, and not that capital.new has ever seen it: both the bytes and the digest come from the file under test. The digest is computed over the mandate_draft object serialized as pretty-printed JSON (2-space indent, key order preserved). Accepts the wrapped {mandate_draft, digest} file or a bare draft.

Parametersdraftrequired

mandate_draft_schema

Mandate draft schema (v1)

Returns the v1 Capital Authority Mandate draft template (v0 accepted too, and its template is included), the never-delegable act list, and the digest convention, so an agent can construct a draft its principal will mint at capital.new. A draft file wraps the draft as {mandate_draft, digest:{alg:'sha-256', hex}}; key order in the draft is part of the document.

Takes no parameters.

ceremony_info

Where the ceremony happens

Returns where and how a mandate draft becomes an instrument. Minting and revocation are human ceremonies at https://capital.new — agents draft and verify; humans authorize. v1 has no signing rail: signing arrives with the portable credential in a later version.

Takes no parameters.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Capital integrations