Capital Company
REMOTE · CAPITALCOMPANY.AI
Launch SPVs and funds, invite investors and send capital calls through Capital Company.
Available components
Last scanned (8 hours ago)
Scores higher than 85% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (capital_company_confirm). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- 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
- All 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
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.
- 5 Nov 26 +1
- Stability: 0.97 → pass security
- 3 Nov 26 +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.
- 1 Nov 26 +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.
- 30 Oct 26 +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.
- 28 Oct 26 +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.
- 26 Oct 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.
- 24 Oct 26 0
- 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 security
- 23 Oct 26 +1
- 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 security
- Tool “capital_company_ask” changed its title: Ask about your funds → Ask Capital Company 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 5 Nov 2026 · Probed https://capitalcompany.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.capitalcompany.ai | CN=Amazon RSA 2048 M01,O=Amazon,C=US | 1 Nov 2026 | 17 May 2027 | RSA 2048 | SHA256-RSA | 2eb156cf38a26e138138d6629eeee97 |
| SANs: *.capitalcompany.ai, capitalcompany.ai | ||||||
| CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 77312380b9d6688a33b1ed9bf9ccda68e0e0f |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of capitalcompany.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| capitalcompany.ai. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | script-src 'self' 'nonce-qgXZonhSisjADYaZZoKAxA=='; style-src 'self' 'unsafe-inline'; connect-src 'self'; img-src 'self' cdn.position.so cdn.alternative.so email.position.so; default-src 'self'; frame-src 'self' https://alternative-webapp-assets-production.s3.us-east-1.amazonaws.com https://alternative-external-static-assets-production.s3.us-east-1.amazonaws.com https://massive-plural-assets-production.s3.us-east-1.amazonaws.com https://massive-edgar-documents-production.s3.us-east-1.amazonaws.com https://massive-public-form-adv-production.s3.us-east-1.amazonaws.com https://massive-browser-sessions.s3.us-east-1.amazonaws.com; frame-ancestors 'self'; object-src 'none'; base-uri 'self'; form-action 'self'; worker-src 'self' data: blob: |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
| permissions-policy | accelerometer=(), camera=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://capitalcompany.ai/mcp | Verified | 200 | |
| http (plaintext) | http://capitalcompany.ai/mcp | HTTPS enforced | 301 | https://capitalcompany.ai/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 →
capital_company_ask Ask Capital Company ~184
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.
| Name | Type | Req | Description |
|---|---|---|---|
| request | string | yes | 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 | yes | The user’s IANA time zone, such as America/New_York |
No output schema declared.
No examples provided.
capital_company_claim Verify your email to finish ~101
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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmationId | string | yes | The Confirmation the user said yes to |
| string | yes | The email address the user will sign in with | |
| timeZone | string | yes | The user’s IANA time zone, such as America/New_York |
No output schema declared.
No examples provided.
capital_company_confirm Confirm or decline what the assistant proposed ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmationId | string | yes | The Confirmation the user was shown, from the link the assistant’s answer carried |
| decision | string | yes | What the user said, in so many words |
| timeZone | string | yes | The user’s IANA time zone, such as America/New_York |
No output schema declared.
No examples provided.
capital_company_conversation Read the Capital Company conversation ~70
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.
| Name | Type | Req | Description |
|---|---|---|---|
| team | string | – | The team whose conversation to read, by name, only when the user belongs to more than one team; leave it out otherwise |
No output schema declared.
No examples provided.
capital_company_create_commitment Record an investor’s commitment ~127
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.
| Name | Type | Req | Description |
|---|---|---|---|
| request | string | yes | 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 | yes | The user’s IANA time zone, such as America/New_York |
No output schema declared.
No examples provided.
capital_company_create_fund Create a fund ~192
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.
| Name | Type | Req | Description |
|---|---|---|---|
| request | string | yes | 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 | yes | The user’s IANA time zone, such as America/New_York |
No output schema declared.
No examples provided.
capital_company_edit_commitment Edit an investor’s commitment ~141
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.
| Name | Type | Req | Description |
|---|---|---|---|
| request | string | yes | 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 | yes | The user’s IANA time zone, such as America/New_York |
No output schema declared.
No examples provided.
capital_company_invite_investors Invite investors to a fund ~132
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.
| Name | Type | Req | Description |
|---|---|---|---|
| request | string | yes | 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 | yes | The user’s IANA time zone, such as America/New_York |
No output schema declared.
No examples provided.
capital_company_reply Answer Capital Company’s question ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | 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 | yes | The user’s IANA time zone, such as America/New_York |
No output schema declared.
No examples provided.
capital_company_send_capital_calls Send capital call notices ~140
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.
| Name | Type | Req | Description |
|---|---|---|---|
| request | string | yes | 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 | yes | The user’s IANA time zone, such as America/New_York |
No output schema declared.
No examples provided.
capital_company_send_subscription_agreements Send subscription agreements ~128
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.
| Name | Type | Req | Description |
|---|---|---|---|
| request | string | yes | 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 | yes | The user’s IANA time zone, such as America/New_York |
No output schema declared.
No examples provided.
capital_company_show_confirmation Show what Capital Company proposes ~47
Shows a Confirmation from Capital Company on its card, where the user can confirm or decline it. Changes nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmationId | string | yes | The Confirmation Capital Company’s reply named |
No output schema declared.
No examples provided.
capital_company_update_fund Update a fund’s settings ~128
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.
| Name | Type | Req | Description |
|---|---|---|---|
| request | string | yes | 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 | yes | The user’s IANA time zone, such as America/New_York |
No output schema declared.
No examples provided.
create_workspace Create a Capital Company workspace ~102
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The email address the person will sign in with | |
| fullName | string | yes | The person’s full name |
| teamName | string | yes | The name of their firm or team, which the workspace is named after |
No output schema declared.
No examples provided.
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.
remote · capitalcompany.ai
claude mcp add --transport http ai-capitalcompany-capital-company 'https://capitalcompany.ai/mcp'
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.