Openproject (PyPI) MCP Server

openproject-mcp PyPI v1.0.2

Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

A Model Context Protocol (MCP) server for OpenProject API v3 integration

Trust grade
A
98/100
Last scanned get badge →
Trust
A · 98/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
Minimal
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 = 98/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 − 2 = 98. 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
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

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 41

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

  • check_permissionsno sensitive capability
  • create_membershipno sensitive capability
  • create_projectno sensitive capability
  • create_time_entryno sensitive capability
  • create_versionno sensitive capability
  • create_work_packageno sensitive capability
  • create_work_package_relationno sensitive capability
  • delete_membershipno sensitive capability
  • delete_projectno sensitive capability
  • delete_time_entryno sensitive capability
Show 31 more tools ↓
  • delete_work_packageno sensitive capability
  • delete_work_package_relationno sensitive capability
  • get_membershipno sensitive capability
  • get_projectno sensitive capability
  • get_roleno sensitive capability
  • get_userno sensitive capability
  • get_work_packageno sensitive capability
  • get_work_package_relationno sensitive capability
  • list_membershipsno sensitive capability
  • list_prioritiesno sensitive capability
  • list_project_membersno sensitive capability
  • list_projectsno sensitive capability
  • list_rolesno sensitive capability
  • list_statusesno sensitive capability
  • list_time_entriesno sensitive capability
  • list_time_entry_activitiesno sensitive capability
  • list_typesno sensitive capability
  • list_user_projectsno sensitive capability
  • list_usersno sensitive capability
  • list_versionsno sensitive capability
  • list_work_package_childrenno sensitive capability
  • list_work_package_relationsno sensitive capability
  • list_work_packagesno sensitive capability
  • remove_work_package_parentno sensitive capability
  • set_work_package_parentno sensitive capability
  • test_connectionno sensitive capability
  • update_membershipno sensitive capability
  • update_projectno sensitive capability
  • update_time_entryno sensitive capability
  • update_work_packageno sensitive capability
  • update_work_package_relationno 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
v1.0.2 latest A 98/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 · 98/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/openproject-mcp-2/badge.svg)](https://mcptrustchecker.com/registry/openproject-mcp-2)
HTML
<a href="https://mcptrustchecker.com/registry/openproject-mcp-2"><img src="https://mcptrustchecker.com/registry/openproject-mcp-2/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/openproject-mcp-2/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 openproject-mcp --online --registry pypi

Use the free API → How scoring works

Other implementations of Openproject 4

Independent packages implementing the same tool, scanned with the same engine. Compare all 5 side by side →

More in Business & CRM