Acp (PyPI) MCP Server

mcp-acp PyPI v0.4.0

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.

MCP server for Ambient Code Platform (ACP) session management - list, delete, debug, and manage AgenticSession resources via the public API

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.

  • acp_add_repono sensitive capability
  • acp_bulk_delete_sessionsno sensitive capability
  • acp_bulk_delete_sessions_by_labelno sensitive capability
  • acp_bulk_label_resourcesno sensitive capability
  • acp_bulk_restart_sessionsno sensitive capability
  • acp_bulk_restart_sessions_by_labelno sensitive capability
  • acp_bulk_stop_sessionsno sensitive capability
  • acp_bulk_stop_sessions_by_labelno sensitive capability
  • acp_bulk_unlabel_resourcesno sensitive capability
  • acp_clone_sessionno sensitive capability
Show 31 more tools ↓
  • acp_create_scheduled_sessionno sensitive capability
  • acp_create_sessionno sensitive capability
  • acp_create_session_from_templateno sensitive capability
  • acp_delete_scheduled_sessionno sensitive capability
  • acp_delete_sessionno sensitive capability
  • acp_export_sessionno sensitive capability
  • acp_get_repos_statusno sensitive capability
  • acp_get_scheduled_sessionno sensitive capability
  • acp_get_sessionno sensitive capability
  • acp_get_session_logsno sensitive capability
  • acp_get_session_metricsno sensitive capability
  • acp_get_session_transcriptno sensitive capability
  • acp_get_workflow_metadatano sensitive capability
  • acp_label_resourceno sensitive capability
  • acp_list_clustersno sensitive capability
  • acp_list_scheduled_session_runsno sensitive capability
  • acp_list_scheduled_sessionsno sensitive capability
  • acp_list_sessionsno sensitive capability
  • acp_list_sessions_by_labelno sensitive capability
  • acp_loginno sensitive capability
  • acp_remove_repono sensitive capability
  • acp_restart_sessionno sensitive capability
  • acp_resume_scheduled_sessionno sensitive capability
  • acp_set_workflowno sensitive capability
  • acp_suspend_scheduled_sessionno sensitive capability
  • acp_switch_clusterno sensitive capability
  • acp_trigger_scheduled_sessionno sensitive capability
  • acp_unlabel_resourceno sensitive capability
  • acp_update_scheduled_sessionno sensitive capability
  • acp_update_sessionno sensitive capability
  • acp_whoamino 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.4.0 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/mcp-acp/badge.svg)](https://mcptrustchecker.com/registry/mcp-acp)
HTML
<a href="https://mcptrustchecker.com/registry/mcp-acp"><img src="https://mcptrustchecker.com/registry/mcp-acp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mcp-acp/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-acp --online --registry pypi

Use the free API → How scoring works

Other implementations of Acp 3

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

More in Cloud & DevOps