Home / MCP registry index / ai.capitalcompany/capital-company
Capital Company
ai.capitalcompany/capital-company in the official MCP registry.
Endpoint https://capitalcompany.ai/mcp.
The registry describes it as: Launch SPVs and funds, invite investors and send capital calls through Capital Company.
We read its 17 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
create_workspace capital_company_create_fund capital_company_process_fund_migration capital_company_control_fund_migration_document capital_company_review_fund_migration_statements capital_company_invite_investors capital_company_send_subscription_agreements capital_company_send_capital_calls capital_company_update_fund capital_company_edit_commitment capital_company_create_commitment capital_company_ask capital_company_reply capital_company_confirm capital_company_show_confirmation capital_company_claim capital_company_conversation
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/ai-capitalcompany-capital-company)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.