Coroot MCP Server

mcp-coroot PyPI v0.1.1

Published by jamesbrink — 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.

MCP server for Coroot observability platform

Trust grade
A
99/100
Last scanned get badge →
Trust
A · 99/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 = 99/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 − 1 = 99. 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
−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 61

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

  • configure_integrationno sensitive capability
  • configure_logsno sensitive capability
  • configure_profilingno sensitive capability
  • configure_tracingno sensitive capability
  • create_api_keyno sensitive capability
  • create_application_categoryno sensitive capability
  • create_dashboardno sensitive capability
  • create_or_update_roleno sensitive capability
  • create_projectno sensitive capability
  • create_userno sensitive capability
Show 51 more tools ↓
  • delete_api_keyno sensitive capability
  • delete_application_categoryno sensitive capability
  • delete_custom_cloud_pricingno sensitive capability
  • delete_dashboardno sensitive capability
  • delete_integrationno sensitive capability
  • delete_projectno sensitive capability
  • get_ai_configno sensitive capability
  • get_applicationno sensitive capability
  • get_application_categoriesno sensitive capability
  • get_application_logsno sensitive capability
  • get_application_profilingno sensitive capability
  • get_application_rcano sensitive capability
  • get_application_tracesno sensitive capability
  • get_applications_overviewno sensitive capability
  • get_current_userno sensitive capability
  • get_custom_applicationsno sensitive capability
  • get_custom_cloud_pricingno sensitive capability
  • get_dashboardno sensitive capability
  • get_db_instrumentationno sensitive capability
  • get_deployments_overviewno sensitive capability
  • get_incidentno sensitive capability
  • get_inspection_configno sensitive capability
  • get_integrationno sensitive capability
  • get_nodeno sensitive capability
  • get_nodes_overviewno sensitive capability
  • get_panel_datano sensitive capability
  • get_projectno sensitive capability
  • get_project_statusno sensitive capability
  • get_risks_overviewno sensitive capability
  • get_rolesno sensitive capability
  • get_sso_configno sensitive capability
  • get_traces_overviewno sensitive capability
  • health_checkno sensitive capability
  • list_api_keysno sensitive capability
  • list_dashboardsno sensitive capability
  • list_inspectionsno sensitive capability
  • list_integrationsno sensitive capability
  • list_projectsno sensitive capability
  • list_usersno sensitive capability
  • test_integrationno sensitive capability
  • update_ai_configno sensitive capability
  • update_application_categoryno sensitive capability
  • update_application_risksno sensitive capability
  • update_current_userno sensitive capability
  • update_custom_applicationsno sensitive capability
  • update_custom_cloud_pricingno sensitive capability
  • update_dashboardno sensitive capability
  • update_db_instrumentationno sensitive capability
  • update_inspection_configno sensitive capability
  • update_project_settingsno sensitive capability
  • update_sso_configno 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
v0.1.1 latest A 99/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 · 99/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mcp-coroot/badge.svg)](https://mcptrustchecker.com/registry/mcp-coroot)
HTML
<a href="https://mcptrustchecker.com/registry/mcp-coroot"><img src="https://mcptrustchecker.com/registry/mcp-coroot/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mcp-coroot/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 mcp-coroot --online --registry pypi

Use the free API → How scoring works

More in Productivity & Workflow