capital.new mandate draft tools
REMOTE · CAPITAL.NEW · SCANNED SEP 24
Verify Capital Authority Mandate drafts (SHA-256 replay) + v0 schema. Ceremonies stay human.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 373 tokens (~124/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the capital.new mandate draft tools MCP server?
capital.new mandate draft tools is a hosted endpoint at https://capital.new/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · capital.new
claude mcp add --transport http new-capital-mandate-tools 'https://capital.new/mcp'
{
"mcpServers": {
"new-capital-mandate-tools": {
"url": "https://capital.new/mcp"
}
}
} {
"servers": {
"new-capital-mandate-tools": {
"type": "http",
"url": "https://capital.new/mcp"
}
}
} [mcp_servers.new-capital-mandate-tools] url = "https://capital.new/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"new-capital-mandate-tools": {
"type": "remote",
"url": "https://capital.new/mcp",
"enabled": true
}
}
} openclaw mcp add new-capital-mandate-tools --url 'https://capital.new/mcp' --transport streamable-http
mcp_servers:
new-capital-mandate-tools:
url: "https://capital.new/mcp" {
"McpServers": {
"new-capital-mandate-tools": {
"Transport": "http",
"Url": "https://capital.new/mcp"
}
}
} assistant mcp add new-capital-mandate-tools -t streamable-http -u 'https://capital.new/mcp'
{
"mcpServers": {
"new-capital-mandate-tools": {
"type": "http",
"url": "https://capital.new/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 7 Sept 26 0
- Stability: 0.97 → pass security
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 73
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 15 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “ceremony_info” rewrote its description, which is the text the model reads security
- Tool “mandate_draft_schema” rewrote its description, which is the text the model reads security
- Tool “mandate_draft_verify” rewrote its description, which is the text the model reads security
- Schema quality: 86 → 124 ▼ functional
- MCP protocol: pass → fail ▼ functional
- MCP protocol version: 2025-11-25 → 2025-06-18 functional
- Server version: 0.1.0 → 0.2.0 functional
- Tool “mandate_draft_schema” changed its title: Mandate draft schema (v0) → Mandate draft schema (v1) cosmetic
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Probed https://capital.new/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=capital.new | CN=WE1,O=Google Trust Services,C=US | 7 Aug 2026 | 5 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 2f1d97edb3049c620e6f89201d619535 |
| SANs: capital.new | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of capital.new. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| new. | present | 25687 | 8 | Verified |
| capital.new. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://capital.new/mcp | Verified | 200 | |
| http (plaintext) | http://capital.new/mcp | HTTPS enforced | 301 | https://capital.new/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ceremony_info Where the ceremony happens ~59
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mandate_draft_schema Mandate draft schema (v1) ~95
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mandate_draft_verify Verify a mandate draft digest ~168
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.
| Name | Type | Req | Description |
|---|---|---|---|
| draft | – | yes | The mandate draft file: the wrapped {mandate_draft, digest} object, a bare draft object, or either as a JSON string. |
No output schema declared.
No examples provided.
What is the capital.new mandate draft tools MCP server?
capital.new mandate draft tools is an MCP server listed in the public MCP registry as new.capital/mandate-tools. Verify Capital Authority Mandate drafts (SHA-256 replay) + v0 schema. Ceremonies stay human. This page covers its hosted endpoint (https://capital.new/mcp).
Is the capital.new mandate draft tools MCP server safe to use?
capital.new mandate draft tools scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the capital.new mandate draft tools MCP server expose?
capital.new mandate draft tools exposes 3 tools: mandate_draft_verify, mandate_draft_schema, ceremony_info. Their descriptions and schemas cost roughly 322 tokens of context every time the server is loaded.
Does the capital.new mandate draft tools MCP server require authentication?
No. We connected to capital.new mandate draft tools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the capital.new mandate draft tools MCP server still maintained?
capital.new mandate draft tools is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.