# Capital Company (remote · capitalcompany.ai)

Launch SPVs and funds, invite investors and send capital calls through Capital Company.

- Trust score: 82/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `capitalcompany.ai`: 82/100 (this document), [markdown](https://verifymcp.io/servers/ai-capitalcompany-capital-company/capitalcompany.md), [page](https://verifymcp.io/servers/ai-capitalcompany-capital-company/capitalcompany)

## Channel facts

- Endpoint: `https://capitalcompany.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (capital_company_confirm).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2269 tokens (~151/item across 15 items; 14 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the Capital Company MCP server?

Capital Company is a hosted endpoint at https://capitalcompany.ai/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.

### Claude

```bash
claude mcp add --transport http ai-capitalcompany-capital-company 'https://capitalcompany.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-capitalcompany-capital-company": {
      "url": "https://capitalcompany.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-capitalcompany-capital-company": {
      "type": "http",
      "url": "https://capitalcompany.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-capitalcompany-capital-company]
url = "https://capitalcompany.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-capitalcompany-capital-company": {
      "type": "remote",
      "url": "https://capitalcompany.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-capitalcompany-capital-company --url 'https://capitalcompany.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-capitalcompany-capital-company:
    url: "https://capitalcompany.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-capitalcompany-capital-company": {
      "Transport": "http",
      "Url": "https://capitalcompany.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-capitalcompany-capital-company -t streamable-http -u 'https://capitalcompany.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-capitalcompany-capital-company": {
      "type": "http",
      "url": "https://capitalcompany.ai/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 82, +1)

- [security] Stability: 0.97 → pass

### 2026-11-03 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 77, +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.

### 2026-10-24 (score 76, 0)

- [security] Tool “capital_company_ask” rewrote its description, which is the text the model reads
- [security] Tool “capital_company_create_commitment” rewrote its description, which is the text the model reads
- [security] Tool “capital_company_create_fund” rewrote its description, which is the text the model reads
- [security] Tool “capital_company_edit_commitment” rewrote its description, which is the text the model reads
- [security] Tool “capital_company_invite_investors” rewrote its description, which is the text the model reads
- [security] Tool “capital_company_send_capital_calls” rewrote its description, which is the text the model reads
- [security] Tool “capital_company_send_subscription_agreements” rewrote its description, which is the text the model reads
- [security] Tool “capital_company_update_fund” rewrote its description, which is the text the model reads
- [security] Tool “create_workspace” rewrote its description, which is the text the model reads

### 2026-10-23 (score 76, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “capital_company_ask” rewrote its description, which is the text the model reads
- [cosmetic] Tool “capital_company_ask” changed its title: Ask about your funds → Ask Capital Company

## MCP tools (14)

### `create_workspace` (~102 tokens)

Create a Capital Company workspace

Use this when someone without a Capital Company account wants one for their firm. Opens a Capital Company workspace, an account and the firm’s team. Needs no sign-in. Capital Company emails them a sign-in link.

Input parameters:

- `email` (string, required): The email address the person will sign in with
- `fullName` (string, required): The person’s full name
- `teamName` (string, required): The name of their firm or team, which the workspace is named after

### `capital_company_create_fund` (~192 tokens)

Create a fund

Use this when the user wants to set up an SPV or a fund — to pool investors’ money into one deal, such as buying a startup’s or a pre-IPO company’s shares, or to raise a blind pool — or asks how to start one. Starts setting up the fund in Capital Company: an SPV or a blind pool, with its legal name, expected allocation, strategy, classes and fees, manager and documents. Returns Capital Company’s next question, or a proposed fund for the user to confirm. This call creates nothing.

Input parameters:

- `request` (string, required): What the user asked for, in their own words
- `team` (string): The team to act on, by name, only when the user belongs to more than one team; leave it out otherwise
- `timeZone` (string, required): The user’s IANA time zone, such as America/New_York

### `capital_company_invite_investors` (~132 tokens)

Invite investors to a fund

Use this when the user wants to bring investors into one of their funds. Starts an invitation of investors to the fund by email address. Returns Capital Company’s next question, or the proposed invitations for the user to confirm. This call sends nothing.

Input parameters:

- `request` (string, required): What the user asked for, in their own words
- `team` (string): The team to act on, by name, only when the user belongs to more than one team; leave it out otherwise
- `timeZone` (string, required): The user’s IANA time zone, such as America/New_York

### `capital_company_send_subscription_agreements` (~128 tokens)

Send subscription agreements

Use this when the user wants investors in one of their funds to sign their subscription agreements. Starts the signature requests. Returns Capital Company’s next question, or the proposed signature requests for the user to confirm. This call sends nothing.

Input parameters:

- `request` (string, required): What the user asked for, in their own words
- `team` (string): The team to act on, by name, only when the user belongs to more than one team; leave it out otherwise
- `timeZone` (string, required): The user’s IANA time zone, such as America/New_York

### `capital_company_send_capital_calls` (~140 tokens)

Send capital call notices

Use this when the user wants a fund’s investors to pay in money they committed. Starts capital call notices to the investors of a fund class. Returns Capital Company’s next question, or the proposed notices for the user to confirm. This call sends nothing, and Capital Company never moves money.

Input parameters:

- `request` (string, required): What the user asked for, in their own words
- `team` (string): The team to act on, by name, only when the user belongs to more than one team; leave it out otherwise
- `timeZone` (string, required): The user’s IANA time zone, such as America/New_York

### `capital_company_update_fund` (~128 tokens)

Update a fund’s settings

Use this when the user wants to change a setting on one of their funds. Starts a change to the settings they name. Returns Capital Company’s next question, or the proposed change for the user to confirm. This call changes nothing.

Input parameters:

- `request` (string, required): What the user asked for, in their own words
- `team` (string): The team to act on, by name, only when the user belongs to more than one team; leave it out otherwise
- `timeZone` (string, required): The user’s IANA time zone, such as America/New_York

### `capital_company_edit_commitment` (~141 tokens)

Edit an investor’s commitment

Use this when the user wants to change an investor’s existing commitment in one of their funds. Starts an edit to the fields they name. Returns Capital Company’s next question, or the proposed edit, with its effect on capital calls already sent, for the user to confirm. This call changes nothing.

Input parameters:

- `request` (string, required): What the user asked for, in their own words
- `team` (string): The team to act on, by name, only when the user belongs to more than one team; leave it out otherwise
- `timeZone` (string, required): The user’s IANA time zone, such as America/New_York

### `capital_company_create_commitment` (~127 tokens)

Record an investor’s commitment

Use this when the user wants to record that an investor committed to one of their funds. Starts recording the new commitment. Returns Capital Company’s next question, or the proposed commitment for the user to confirm. This call records nothing.

Input parameters:

- `request` (string, required): What the user asked for, in their own words
- `team` (string): The team to act on, by name, only when the user belongs to more than one team; leave it out otherwise
- `timeZone` (string, required): The user’s IANA time zone, such as America/New_York

### `capital_company_ask` (~184 tokens)

Ask Capital Company

Use this when the user asks about their own funds on Capital Company, or how Capital Company works. Answers a question about the user’s team and funds from Capital Company’s records, or about how Capital Company works — where something is, what a page, a status or an email means, what the product offers, such as its API — from Capital Company’s product guide, with a link to the page when there is one. Answers in Capital Company’s words, only from what the user may see. Changes nothing.

Input parameters:

- `request` (string, required): What the user asked for, in their own words
- `team` (string): The team to act on, by name, only when the user belongs to more than one team; leave it out otherwise
- `timeZone` (string, required): The user’s IANA time zone, such as America/New_York

### `capital_company_reply` (~112 tokens)

Answer Capital Company’s question

Sends the user’s answer to Capital Company’s last question, in their own words. Returns Capital Company’s next question, or a proposal for the user to confirm.

Input parameters:

- `answer` (string, required): The user’s answer, in their own words
- `team` (string): The team the conversation is on, by name, only when the user belongs to more than one team; leave it out otherwise
- `timeZone` (string, required): The user’s IANA time zone, such as America/New_York

### `capital_company_confirm` (~108 tokens)

Confirm or decline what the assistant proposed

Sends the user’s answer, confirm or decline, to a Confirmation from Capital Company. Confirming carries out what it describes; declining carries out nothing, and Capital Company asks what to change.

Input parameters:

- `confirmationId` (string, required): The Confirmation the user was shown, from the link the assistant’s answer carried
- `decision` (string, required): What the user said, in so many words
- `timeZone` (string, required): The user’s IANA time zone, such as America/New_York

### `capital_company_show_confirmation` (~47 tokens)

Show what Capital Company proposes

Shows a Confirmation from Capital Company on its card, where the user can confirm or decline it. Changes nothing.

Input parameters:

- `confirmationId` (string, required): The Confirmation Capital Company’s reply named

### `capital_company_claim` (~101 tokens)

Verify your email to finish

For someone without a Capital Company account who said yes to a proposal: emails a sign-in link to the address they give. Opening the link verifies the address and creates what they said yes to.

Input parameters:

- `confirmationId` (string, required): The Confirmation the user said yes to
- `email` (string, required): The email address the user will sign in with
- `timeZone` (string, required): The user’s IANA time zone, such as America/New_York

### `capital_company_conversation` (~70 tokens)

Read the Capital Company conversation

Reads the user’s current conversation with Capital Company, including the outcome of anything they confirmed and whether it is waiting on them. Changes nothing.

Input parameters:

- `team` (string): The team whose conversation to read, by name, only when the user belongs to more than one team; leave it out otherwise

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-capitalcompany-capital-company/capitalcompany#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 81
- 2026-11-03: 81
- 2026-11-02: 80
- 2026-11-01: 80
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 78
- 2026-10-28: 78
- 2026-10-27: 77
- 2026-10-26: 77
- 2026-10-25: 76
- 2026-10-24: 76
- 2026-10-23: 76
- 2026-10-22: 75
- 2026-10-21: 75
- 2026-10-20: 74
- 2026-10-19: 74
- 2026-10-18: 74
- 2026-10-17: 74
- 2026-10-16: 73
- 2026-10-15: 73
- 2026-10-14: 72
- 2026-10-13: 72
- 2026-10-12: 71
- 2026-10-10: 70
- 2026-10-07: 69

## Common questions

### What is the Capital Company MCP server?

Capital Company is an MCP server listed in the public MCP registry as ai.capitalcompany/capital-company. Launch SPVs and funds, invite investors and send capital calls through Capital Company. This page covers its hosted endpoint (https://capitalcompany.ai/mcp).

### Is the Capital Company MCP server safe to use?

Capital Company scores 82 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 Company MCP server expose?

Capital Company exposes 14 tools: create_workspace, capital_company_create_fund, capital_company_invite_investors, capital_company_send_subscription_agreements, capital_company_send_capital_calls, and 9 more. Their descriptions and schemas cost roughly 1,712 tokens of context every time the server is loaded.

### Does the Capital Company MCP server require authentication?

No. We connected to Capital Company without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Capital Company MCP server still maintained?

Capital Company is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://capitalcompany.ai/mcp
- Website: https://capitalcompany.ai/assistants
- Changelog RSS feed: https://verifymcp.io/servers/ai-capitalcompany-capital-company/capitalcompany.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-capitalcompany-capital-company/capitalcompany.json
- HTML version of this page: https://verifymcp.io/servers/ai-capitalcompany-capital-company/capitalcompany