Fcop MCP Server

fcop-mcp PyPI v3.2.5

Published by joinwell52-ai — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

stdio MCP server for the FCoP Python library: exposes the fcop package's Project, task, report, issue, GAL alert, and audit APIs to MCP clients (Cursor, Claude Desktop, …). Optional bridge, not a second protocol; depends on fcop 3.x, FastMCP, websockets.

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 45

Each tool and what it can reach — statically extracted from the published source.

  • inspect_taskreads sensitive data
  • read_reportreads sensitive data
  • approve_taskno sensitive capability
  • archive_taskno sensitive capability
  • archive_to_historyno sensitive capability
  • bulk_archive_to_historyno sensitive capability
  • check_updateno sensitive capability
  • claim_taskno sensitive capability
  • create_custom_teamno sensitive capability
  • create_taskno sensitive capability
Show 35 more tools ↓
  • deploy_role_templatesno sensitive capability
  • drop_suggestionno sensitive capability
  • fcop_auditno sensitive capability
  • fcop_checkno sensitive capability
  • fcop_create_alertno sensitive capability
  • fcop_list_alertsno sensitive capability
  • fcop_reportno sensitive capability
  • finish_taskno sensitive capability
  • get_available_teamsno sensitive capability
  • get_governance_summaryno sensitive capability
  • get_team_statusno sensitive capability
  • init_projectno sensitive capability
  • init_solono sensitive capability
  • list_governance_eventsno sensitive capability
  • list_historyno sensitive capability
  • list_issuesno sensitive capability
  • list_reportsno sensitive capability
  • list_reviewsno sensitive capability
  • list_tasksno sensitive capability
  • list_workspacesno sensitive capability
  • mark_human_approvedno sensitive capability
  • new_workspaceno sensitive capability
  • read_history_taskno sensitive capability
  • read_reviewno sensitive capability
  • read_taskno sensitive capability
  • redeploy_rulesno sensitive capability
  • reject_taskno sensitive capability
  • set_project_dirno sensitive capability
  • submit_taskno sensitive capability
  • upgrade_fcopno sensitive capability
  • validate_team_configno sensitive capability
  • write_issueno sensitive capability
  • write_reportno sensitive capability
  • write_reviewno sensitive capability
  • write_taskno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v3.2.5 latest A 96/100 0 1.13.0 2026-08-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/fcop-mcp/badge.svg)](https://mcptrustchecker.com/registry/fcop-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/fcop-mcp"><img src="https://mcptrustchecker.com/registry/fcop-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/fcop-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan fcop-mcp --online --registry pypi

Use the free API → How scoring works

More in Developer Tools