Koskamo

capital.new MCP

A keyless, stateless MCP server that allows AI agents to verify Capital Authority Mandate drafts via SHA-256 digest replay, read the mandate schema, and locate the human ceremony URL. It stores no data and requires no authentication.

Visit capital.new

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

capital.new MCP logo, by capital.newVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-06Operated by capital.new
MCP endpoint (Streamable HTTP)
https://capital.new/mcp
Vendor documentation

What its tools do

3 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Not annotated (3)

3 of 3 have a description · 0 of 3 declare behavior hints · 1 of 1 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to capital.new ·
  • Passed Endpoint is on the registry namespace domain ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Verify a mandate draft digest
  • Read the mandate schema
  • Find the ceremony location

Source and maintenance

Vendor evidenceRegistry 0.1.0
mcp-registry: new.capital/mandate-tools@0.1.0Project website

Protocol and capabilities

Server
new.capital/mandate-tools 0.2.0
MCP protocol negotiated in check
2025-06-18
Tools
3 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": false
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Tools for Capital Authority Mandate drafts (v1 current; v0 accepted forever). An agent may draft and verify; minting and revocation are human ceremonies performed at https://capital.new. This server stores nothing and accepts no credentials.

Tools

3 advertised

mandate_draft_verify — Verify a mandate draft digest
Advertised by the server during the last successful anonymous check.

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.

mandate_draft_verify input schema
{
  "type": "object",
  "required": [
    "draft"
  ],
  "properties": {
    "draft": {
      "anyOf": [
        {
          "type": "object"
        },
        {
          "type": "string"
        }
      ],
      "description": "The mandate draft file: the wrapped {mandate_draft, digest} object, a bare draft object, or either as a JSON string."
    }
  }
}
mandate_draft_schema — Mandate draft schema (v1)
Advertised by the server during the last successful anonymous check.

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.

mandate_draft_schema input schema
{
  "type": "object",
  "properties": {}
}
ceremony_info — Where the ceremony happens
Advertised by the server during the last successful anonymous check.

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.

ceremony_info input schema
{
  "type": "object",
  "properties": {}
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 1 answered).

  1. 2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
462 ms
95th percentile latency
462 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 462 ms · metadata changed · 3 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http capital-new-mcp https://capital.new/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add capital-new-mcp --url https://capital.new/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable capital-new-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "capital-new-mcp": {
      "url": "https://capital.new/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "capital-new-mcp": {
      "type": "streamableHttp",
      "url": "https://capital.new/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start capital-new-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "capital-new-mcp": {
      "type": "http",
      "url": "https://capital.new/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http capital-new-mcp https://capital.new/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://capital.new/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "capital-new-mcp": {
      "serverUrl": "https://capital.new/mcp"
    }
  }
}

Let your agent find its tools

Find servers like capital.new MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 628

Do you run capital.new MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing