Skip to content

capital.new mandate draft tools MCP server

new.capital/mandate-toolscapital.newstreamable-httpv0.1.0Scanned

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

3 tools: 1 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 1 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the capital.new mandate draft tools MCP server can do

The capital.new mandate draft tools MCP server is published by capital.new, a domain the MCP Registry verified. It has 3 tools. It can create or change data (1 tool: mandate_draft_verify), but cannot delete data. 2 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

The fixed checks matched 1 finding (credentials-mention). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 18, 2026, version 0.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

3 tools

Changes things 1Claude Code: ask
  • mandate_draft_verifyRecomputes 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.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
Only reads 2Show 2 read-only tools
  • ceremony_infoReturns where and how a mandate draft becomes an instrument.1 finding

    Why it is in this group

    • The description's first verb is "return": a word for reading.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...rail: signing arrives with the portable credential in a later version."

      What this check looks for
    Description, as the server wrote it
    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.
  • mandate_draft_schemaReturns 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 co…No findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:16 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://capital.new/mcp: tools/list returned 3 tools to an anonymous client, including mandate_draft_verify (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 info

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http mandate-tools https://capital.new/mcp
claude mcp add --transport http mandate-tools https://capital.new/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__mandate-tools__mandate_draft_schema",
      "mcp__mandate-tools__ceremony_info"
    ],
    "ask": [
      "mcp__mandate-tools__mandate_draft_verify"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as mandate-tools. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/new.capital/mandate-tools/verify?hash=14663e48464c000d384c1ae36ef3da3ee4c6d984f5023bb2ad7f97451655f67a" | jq -e '.changed == false'

Pinned hash 14663e48464c, from Nov 18, 2026, 21:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/new.capital/mandate-tools/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for new.capital/mandate-tools
[![Anlyon Radar](https://radar.anlyon.com/badge/new.capital/mandate-tools.svg)](https://radar.anlyon.com/servers/new.capital/mandate-tools)

Source: MCP Registry. Synced Oct 21, 2026, 18:53 UTC.

capital.new mandate draft tools MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the capital.new mandate draft tools MCP server safe?

No scan can promise that. What its definitions show: 3 tools, 1 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the capital.new mandate draft tools MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the capital.new mandate draft tools MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the capital.new mandate draft tools MCP server have?

3 tools: 1 write, 2 read. mandate_draft_verify, mandate_draft_schema and ceremony_info.

Does the capital.new mandate draft tools MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the capital.new mandate draft tools MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the capital.new mandate draft tools MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.