Atrium MCP Server

@lacneu/atrium-mcp npm v0.80.1 Source verified

Published by lacneu — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

Thin MCP server + CLI that proxy the atrium /api/v1 observability surface using an oc_live_ Bearer key. Talks HTTP only — no Convex imports.

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

✓ No adoption-risk deductions — minimal blast radius, verified enough, and fully inspected.

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 31

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

  • bridge_statusno sensitive capability
  • close_feedback_reportno sensitive capability
  • delete_delivery_sessionsno sensitive capability
  • diagnose_chatno sensitive capability
  • get_activityno sensitive capability
  • get_anomaly_attachmentsno sensitive capability
  • get_anomaly_occurrencesno sensitive capability
  • get_chat_stateno sensitive capability
  • get_compaction_historyno sensitive capability
  • get_compatno sensitive capability
Show 21 more tools ↓
  • get_delivery_reportno sensitive capability
  • get_feedback_reportno sensitive capability
  • get_integrationsno sensitive capability
  • get_kpino sensitive capability
  • get_schemano sensitive capability
  • get_trace_enrichmentno sensitive capability
  • healthno sensitive capability
  • list_anomaliesno sensitive capability
  • list_delivery_sessionsno sensitive capability
  • list_feedback_reportsno sensitive capability
  • list_schemasno sensitive capability
  • list_tracesno sensitive capability
  • lossless_doctorno sensitive capability
  • query_openclawno sensitive capability
  • reconcile_chatno sensitive capability
  • reply_feedback_reportno sensitive capability
  • report_anomalyno sensitive capability
  • resolve_anomalyno sensitive capability
  • start_delivery_recordno sensitive capability
  • stop_delivery_recordno sensitive capability
  • sync_instanceno sensitive capability

What this scan could not see

Versions 10

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.80.1 latest A 100/100 0 1.13.0 2026-09-07
v0.77.0 A 100/100 0 1.13.0 2026-09-06
v0.76.0 A 100/100 0 1.13.0 2026-09-05
v0.75.3 A 100/100 0 1.13.0 2026-08-28
v0.75.0 A 100/100 0 1.12.1 2026-08-23
Show 5 more versions ↓
v0.74.4 A 100/100 0 1.12.1 2026-08-22
v0.74.3 A 100/100 0 1.12.1 2026-08-21
v0.74.1 A 100/100 0 1.12.1 2026-08-20
v0.74.0 A 100/100 0 1.12.1 2026-08-19
v0.73.0 A 100/100 0 1.12.1 2026-08-16

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 · 100/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/lacneu-atrium-mcp/badge.svg)](https://mcptrustchecker.com/registry/lacneu-atrium-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/lacneu-atrium-mcp"><img src="https://mcptrustchecker.com/registry/lacneu-atrium-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/lacneu-atrium-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 @lacneu/atrium-mcp --online

Use the free API → How scoring works

More in Lifestyle & Local