MCP Risk

Directory / server

co.lovie/company-formation

This directory entry reports an automated security scan of co.lovie/company-formation, scanned 2026-07-28. Trust grade B rates provenance, transport, known vulnerabilities and instruction integrity; capability risk is reported separately, not folded into the grade.

registry.modelcontextprotocol.io, scanned 2026-07-28, tool surface via package-source

B 80/100 permalink

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: 41 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: 148 days
  • Weekly downloads: 51
  • Repo field matches source repo: false
  • Build-provenance attestation: absent
PASS Tool surface is inspectable and proportionate §2.1–§2.4
Package source scanned. Capabilities detected: process-execution, filesystem, 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. 7 findings
  • process-execution (child process execution): dist/index.js
  • process-execution (child process module import): dist/index.js
  • filesystem (filesystem write/delete): dist/index.js
  • filesystem (fs module import): dist/index.js
  • network-egress (outbound network calls): dist/index.js
  • network-egress (http module import): dist/index.js
  • Detected capabilities: process-execution, filesystem, network-egress
PASS HTTPS-only endpoint §3.1
Endpoint uses HTTPS. 1 finding
  • Endpoint: https://mcp.lovie.co/mcp/mcp
PASS Authentication required §3.2
Server rejects anonymous requests and advertises its auth scheme. 1 finding
  • WWW-Authenticate: Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://mcp.lovie.co/.well-known/oauth-protected-resource/mcp/mcp"
WARN OAuth protected-resource metadata published §3.3
No protected-resource metadata found - clients cannot discover the authorization server per spec. 1 finding
  • Checked: https://mcp.lovie.co/.well-known/oauth-protected-resource
PASS No known vulnerabilities (OSV.dev) §4.1

No advisories on record for lovie @1.0.10 (npm).
PASS Server-supplied instructions free of poisoning indicators §5.1–§5.4

No poisoning indicators found across 1 server-supplied text item(s).
What this grade covers
  • Provenance & supply-chain integrity (§1)
  • Tool surface & capability risk (§2)
  • Transport & authentication (§3)
  • Known CVEs via OSV.dev (§4)
  • Instruction/tool poisoning patterns (§5)

Limitations: pattern-based only (no semantic injection detection), static npm analysis (live server instructions not retrieved for package-only scans), single-server scope (no cross-server toxic flow analysis). See the full policy.

Methodology: MCP Server Security Policy. Unfamiliar term? See the glossary.