Home / MCP registry index / co.lovie/company-formation
Lovie Company Formation
co.lovie/company-formation in the official MCP registry.
Endpoint https://mcp.lovie.co/mcp/mcp. Source: github.com/lovieco/lovie-company-formation-mcp-npx.
The registry describes it as: Form companies, manage bank accounts, cards, invoices and more — directly from your AI coding tools.
We read its 200 tools on 2026-10-22. 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
account_get_account account_get_list_account_details accounting_get_accounting_settings accounting_get_aging_report accounting_get_balance_sheet accounting_get_cash_flow_statement accounting_get_chart_of_accounts accounting_get_close_target accounting_get_funding_summaries accounting_get_general_ledger accounting_get_gl_account_type_catalog accounting_get_journal_entry_by_transaction accounting_get_list_journal_entries accounting_get_list_periods accounting_get_list_review_items accounting_get_list_schedules accounting_get_list_statements accounting_get_period accounting_get_profit_and_loss accounting_get_report_series accounting_get_review_counts accounting_get_schedule accounting_get_similar_review_items accounting_get_statement accounting_get_trial_balance accounting_list_accounting_audit_events accounting_preview_close accounting_preview_schedule accounting_propose_schedules accounting_suggest_statement_matches accounting_suggest_transfer_pairs ads_insight_summarize_ad_spend ads_insight_summarize_campaign_window approval_session_create_approval_session approval_session_get_approval_session_status autonomous_pay banking_confirm_extracted_value banking_confirm_initial_transfer banking_extract_document_fields banking_get_banking_application banking_get_initial_transfer_preview banking_get_issuance_state banking_hydrate_from_cap_table banking_hydrate_from_formation banking_preview_cap_table_hydration banking_preview_formation_hydration banking_refresh_application_provider_status banking_refresh_owner_verification banking_set_application_ein banking_set_owner_identity_document_number banking_set_owner_tax_identifier banking_start_banking_application banking_submit_banking_application banking_suggest_industry_code banking_update_banking_application banking_upsert_beneficial_owner cap_table_clear_cap_table_stakeholders cap_table_close_cap_table_round cap_table_create_cap_table_agreement cap_table_create_cap_table_round and 140 more
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/co-lovie-company-formation)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.