Protowall MCP Server

protowall 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.

Trust grade
A
90/100
Last scanned
Trust
A · 90/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
Moderate
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.
A Why this grade threat 98 − adoption risk = 90/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 − 2.1 = 98. What the published surface and source actually contain:

PointsWhat was foundCategory
−2.1 Package has no source repository MTC-SUP-011 supply-chain

2. Client adoption risk — 98 − 8 = 90. 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
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−5 publisher verification (unlocatable) — no provenance and no public repository to inspect
inspection depth (source) — how much of the target the scan could see

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 1

low Package has no source repositoryMTC-SUP-011

"protowall" declares no repository URL, so its published artifact cannot be compared against reviewable source.

Fix: Prefer packages that link to public, reviewable source.

Location: package protowall

Tools 17

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

  • summarize_reviewer_sessioningests untrusted input
  • approve_access_requestno sensitive capability
  • close_previewno sensitive capability
  • create_previewno sensitive capability
  • create_projectno sensitive capability
  • decline_access_requestno sensitive capability
  • get_audit_logno sensitive capability
  • get_project_usageno sensitive capability
  • get_reviewer_engagementno sensitive capability
  • list_access_requestsno sensitive capability
  • list_previewsno sensitive capability
  • list_projectsno sensitive capability
  • list_reviewer_sessionsno sensitive capability
  • revoke_accessno sensitive capability
  • rotate_secretno sensitive capability
  • send_inviteno sensitive capability
  • update_previewno sensitive capability

What this scan could not see

Versions

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 90/100 1 1.8.0 2026-07-23

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

Use the free API → How scoring works

More in Developer Tools