Prowpt MCP Server

prowpt-mcp-server PyPI v0.3.1

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

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/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.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/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 − 4 = 96. 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
−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 1

medium Untrusted input can drive an external actionMTC-FLOW-005

Untrusted-input tools ([create_workflow]) co-exist with external-action tools ([create_workflow]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.

Evidence: untrusted [create_workflow] → sinks [create_workflow]

Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.

Location: flow create_workflow → create_workflow

Tools 59

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

  • create_workflowingests untrusted inputnetwork egress
  • accept_previewno sensitive capability
  • add_packageno sensitive capability
  • clone_projectno sensitive capability
  • connect_stripeno sensitive capability
  • create_projectno sensitive capability
  • create_recordno sensitive capability
  • create_record_typeno sensitive capability
  • delete_assetno sensitive capability
  • delete_email_templateno sensitive capability
Show 49 more tools ↓
  • delete_projectno sensitive capability
  • delete_recordno sensitive capability
  • delete_workflowno sensitive capability
  • deploy_projectno sensitive capability
  • discard_draft_changesno sensitive capability
  • disconnect_stripeno sensitive capability
  • execute_workflowno sensitive capability
  • export_projectno sensitive capability
  • get_account_infono sensitive capability
  • get_assistant_statusno sensitive capability
  • get_creditsno sensitive capability
  • get_deploymentsno sensitive capability
  • get_email_templateno sensitive capability
  • get_preview_urlno sensitive capability
  • get_projectno sensitive capability
  • get_project_contextno sensitive capability
  • get_publish_statusno sensitive capability
  • get_source_versionsno sensitive capability
  • get_stripe_statusno sensitive capability
  • get_translationsno sensitive capability
  • get_usageno sensitive capability
  • get_workflow_executionsno sensitive capability
  • list_assetsno sensitive capability
  • list_catalogno sensitive capability
  • list_email_templatesno sensitive capability
  • list_project_packagesno sensitive capability
  • list_projectsno sensitive capability
  • list_record_typesno sensitive capability
  • list_recordsno sensitive capability
  • list_source_filesno sensitive capability
  • list_workflowsno sensitive capability
  • preview_email_templateno sensitive capability
  • publish_projectno sensitive capability
  • purchase_credit_packno sensitive capability
  • read_source_fileno sensitive capability
  • remove_packageno sensitive capability
  • reset_system_templatesno sensitive capability
  • restore_source_versionno sensitive capability
  • seed_email_templatesno sensitive capability
  • send_promptno sensitive capability
  • send_test_emailno sensitive capability
  • update_projectno sensitive capability
  • update_recordno sensitive capability
  • update_record_typeno sensitive capability
  • update_translationsno sensitive capability
  • update_workflowno sensitive capability
  • upload_assetno sensitive capability
  • upsert_email_templateno sensitive capability
  • write_source_filesno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

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

Use the free API → How scoring works

More in Developer Tools