Amicus MCP Server

amicus PyPI v0.8.0

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

One MCP server for every second-opinion model: consult, review, and delegate with the backend as a parameter

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/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
High
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 = 93/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 − 7 = 93. 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
−6 capability blast radius (high) — 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 15

high Reads a sensitive credential path or dumps the environment (src/amicus/sdk/core/redaction.py)MTC-SRC-006

In the server's implementation (`src/amicus/sdk/core/redaction.py:15`): Reading private keys / cloud credentials, or serializing the whole environment, is a sensitive-data source that becomes exfiltration when combined with any egress. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: .env$|.*\.pem$|.*\.key$|id_rsa|id_ed25519|.*\.p12$)", re.IGNORECASE, ) # Inline secret-value shapes redacted within

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server src/amicus/sdk/core/redaction.py

high Dynamic code execution in server code (src/amicus/obs.py)MTC-SRC-001

In the server's implementation (`src/amicus/obs.py:133`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: 's free-form filename (`exec(compile(src, "<anything>", ...))`) but does not prove the code was READ from that file.

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server src/amicus/obs.py

high Shell/command execution in server code (src/amicus/backends/claude/cli.py)MTC-SRC-002

In the server's implementation (`src/amicus/backends/claude/cli.py:192`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: try: proc = subprocess.run( [binary, *contract.AUTH_STATUS_ARGS], capture_output=Tru

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server src/amicus/backends/claude/cli.py

high Shell/command execution in server code (src/amicus/jobs/store.py)MTC-SRC-002

In the server's implementation (`src/amicus/jobs/store.py:657`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: proc = subprocess.Popen( cmd, cwd=str(jd),

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server src/amicus/jobs/store.py

high Shell/command execution in server code (src/amicus/manifest.py)MTC-SRC-002

In the server's implementation (`src/amicus/manifest.py:246`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: rement_env() proc = subprocess.Popen( _SERVER_ARGV, stdin=subprocess.PIPE, stdout=subprocess

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server src/amicus/manifest.py

low Reads a sensitive credential path or dumps the environment in packaging/dev tooling (tests/sdk/test_gitdiff.py)MTC-SRC-006

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/sdk/test_gitdiff.py:1227`): Reading private keys / cloud credentials, or serializing the whole environment, is a sensitive-data source that becomes exfiltration when combined with any egress. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: , "diff --git a/id_rsa b/config.py", ] probe = DiffRedactor() retained_out: list[str] = [] for l

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/sdk/test_gitdiff.py

low Reads a sensitive credential path or dumps the environment in packaging/dev tooling (tests/sdk/test_redaction.py)MTC-SRC-006

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/sdk/test_redaction.py:2208`): Reading private keys / cloud credentials, or serializing the whole environment, is a sensitive-data source that becomes exfiltration when combined with any egress. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: ( "diff --git a/id_rsa b/config.py\n" "diff --git a/config.py b/config.py\n" "--- a/config.py\n+

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/sdk/test_redaction.py

low Dynamic code execution in packaging/dev tooling (tests/test_log_redaction.py)MTC-SRC-001

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_log_redaction.py:322`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: amespace: dict = {} exec(compile("def boom():\n raise RuntimeError('x')\n", f"<{MARKER}>", "exec"), namespace)

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/test_log_redaction.py

low Shell/command execution in packaging/dev tooling (scripts/capture_claude_differentials.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/capture_claude_differentials.py:308`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: () -> int: commit = subprocess.run( ["git", "log", "-1", "--format=%h"], capture_output=True, text=True, che

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server scripts/capture_claude_differentials.py

low Shell/command execution in packaging/dev tooling (scripts/capture_codex_differentials.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/capture_codex_differentials.py:239`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: () -> int: commit = subprocess.run( ["git", "log", "-1", "--format=%h"], capture_output=True, text=True, che

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server scripts/capture_codex_differentials.py

low Shell/command execution in packaging/dev tooling (scripts/capture_kimi_differentials.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/capture_kimi_differentials.py:241`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: () -> int: commit = subprocess.run( ["git", "log", "-1", "--format=%h"], capture_output=True, text=True, che

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server scripts/capture_kimi_differentials.py

low Shell/command execution in packaging/dev tooling (scripts/check_backend_compat.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/check_backend_compat.py:146`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: try: done = subprocess.run( ["npm", "view", package, "version"], capture_output=True

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server scripts/check_backend_compat.py

low Shell/command execution in packaging/dev tooling (scripts/check_release_state.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/check_release_state.py:833`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: OOT) -> str: return subprocess.run( ["git", *args], cwd=repo_root, capture_output=True, text=True, check=Tru

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server scripts/check_release_state.py

low Shell/command execution in packaging/dev tooling (scripts/probe_review_surface.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/probe_review_surface.py:165`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: ver. """ proc = subprocess.Popen( [sys.executable, "-c", "from amicus.server import main; main()"],

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server scripts/probe_review_surface.py

low Shell/command execution in packaging/dev tooling (scripts/record_live_gate_evidence.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/record_live_gate_evidence.py:121`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: rocess[str]: return subprocess.run(["git", *args], cwd=REPO_ROOT, capture_output=True, text=True, check=True) def

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server scripts/record_live_gate_evidence.py

What this scan could not see

Versions 8

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.8.0 latest A 93/100 15 1.14.0 2026-09-28
v0.7.0 A 93/100 15 1.14.0 2026-09-26
v0.6.0 A 93/100 15 1.14.0 2026-09-25
v0.5.0 A 93/100 15 1.14.0 2026-09-20
v0.4.0 A 93/100 15 1.13.0 2026-09-19
Show 3 more versions ↓
v0.3.0 A 93/100 12 1.13.0 2026-09-16
v0.2.0 A 93/100 12 1.13.0 2026-09-11
v0.1.0 A 93/100 10 1.13.0 2026-09-10

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

Use the free API → How scoring works

More in Developer Tools

1stay Source verified npm
A
1stay-mcp

Hotel booking MCP server — 300K+ properties, real confirmation numbers, loyalty programs. Builders monetize every booking via Stripe Connect. The first MCP server that completes real hotel reservations inside AI conversations.

Developer Tools Score 100/100 0 findings 31/wk Cap. Minimal
21st.dev Magic Source verified npm
A
@21st-dev/magic

Generates production-ready UI components from natural language, inspired by v0.

Developer Tools Score 100/100 0 findings 16k/wk Cap. Minimal
A11y Context Source verified npm
A
@a11y-context/mcp-server

Model Context Protocol server that serves the A11y Context accessibility-pattern corpus (WCAG 2.2 AA patterns, Foundations rules) to AI coding agents.

Developer Tools Score 100/100 0 findings 484/wk Cap. Minimal
Adguard Home Source verified npm
A
@samik081/mcp-adguard-home

Manage AdGuard Home through AI assistants

Developer Tools Score 100/100 0 findings 641/wk Cap. Minimal
Ado Browser Source verified npm
A
mcp-ado-browser

Read-only Azure DevOps for MCP clients using only your existing browser session — no PAT, no Azure CLI. Browse work items, pull requests, comments, attachments and Artifacts feeds across every project, repo and feed you can access.

Developer Tools Score 100/100 0 findings 19/wk Cap. Minimal
Adobe Experience Dev Source verified npm
A
@stubbedev/adobe-experience-dev-mcp

MCP server for Adobe Experience Manager Assets integration development

Developer Tools Score 100/100 0 findings 200/wk Cap. Minimal