MCP/Risk

Scan report

co.lovie/company-formation

npm, scanned 2026-09-11, tool surface via remote-tools-list

This page reports an automated security scan of co.lovie/company-formation (npm), scanned 2026-09-11. It rates trust (provenance, transport, known vulnerabilities, instruction integrity) as grade F and capability risk (what the tools can do) separately at high. It does not certify the server is safe to connect; it reports what could be checked from outside.

Automated checks

StatusCheckPolicyResult
PASS Listed on the official MCP registry §1.1
Listed on registry.modelcontextprotocol.io as co.lovie/company-formation. 1 finding
  • Registry entry: co.lovie/company-formation ↗
WARN Source repository is public and maintained §1.2
Repository health issues: no license. 5 findings
  • Repository ↗
  • Last push: 86 days ago
  • Stars: 0
  • License: none detected
  • Security policy (SECURITY.md): absent
FAIL Published package is consistent and attested §1.3
Integrity concerns: package repository field does not match the claimed source repo; no npm provenance attestation. 6 findings
  • Package: lovie@1.0.10 ↗
  • Ecosystem: npm
  • Age: 192 days
  • Weekly downloads: 41
  • Repo field matches source repo: false
  • Build-provenance attestation: absent
PASS Tool surface is inspectable and proportionate §2.1–§2.4
332 tool(s) enumerated. Capabilities detected: network-egress. Reported as capability risk (§2.4); whether each is essential to the server's stated purpose is §2.3 and remains a manual judgement. 4 findings
  • Tools exposed: 332
  • banking_refresh_application_provider_status: network-egress
  • formation_confirm_payment: network-egress
  • Detected capabilities: network-egress
PASS HTTPS-only endpoint §3.1
Endpoint uses HTTPS. 1 finding
  • Endpoint: https://mcp.lovie.co/mcp/mcp
FAIL Authentication required §3.2

Server answers anonymous requests (HTTP 200) while exposing non-trivial or unverifiable capabilities - fail per §3.2.
PASS OAuth protected-resource metadata published §3.3
Publishes /.well-known/oauth-protected-resource per the June 2025 authorization spec. 1 finding
  • Authorization server: https://mcp.lovie.co
PASS No known vulnerabilities (OSV.dev) §4.1

No advisories on record for lovie @1.0.10 (npm).
FAIL Server-supplied instructions free of poisoning indicators §5.1–§5.4
3 suspicious indicator(s) found in server-supplied instructions, tool descriptions, or schemas. 3 findings
  • cap_table_record_cap_table_investment description: oversized: 2125 chars (limit 2048)
  • banking_set_owner_identity_document_number: cross-tool shadowing: instead of the tax-identifier tool
  • formation_confirm_payment: concealment directive: do not tell the user

Verify manually - the scoring model can’t judge these for you

  • §2.3 - Is the tool surface no broader than the server’s stated purpose requires?
  • §3.4 - For stdio servers: which environment credentials does it read, and are they scoped rather than org-wide tokens?
  • §6.1 - Cross this server’s capabilities with your already-connected servers: any read-capability × send-capability pairs need explicit sign-off.
  • §6.2 - Run the connecting agent with sandboxing and egress controls sized to the combined tool surface, not just this server’s.

Methodology: MCP Server Security Policy. Checks and scoring weights are open source. Unfamiliar term? See the glossary.