Profunding MCP Server

profunding-mcp PyPI v0.9.6

Published by desperate10 — 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
99/100
Last scanned
Trust
A · 99/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.
A Why this grade threat 100 − adoption risk = 99/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 − 1 = 99. 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
capability blast radius (minimal) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable
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 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 44

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

  • analyze_pairno sensitive capability
  • cancel_orderno sensitive capability
  • check_liquidityno sensitive capability
  • close_delta_neutralno sensitive capability
  • close_tradeno sensitive capability
  • compare_exchangesno sensitive capability
  • convert_stablecoinno sensitive capability
  • find_best_tradeno sensitive capability
  • find_exit_cancelno sensitive capability
  • find_exit_previewno sensitive capability
  • find_exit_startno sensitive capability
  • find_exit_statusno sensitive capability
  • get_alertsno sensitive capability
  • get_balanceno sensitive capability
  • get_exchangesno sensitive capability
  • get_historical_ratesno sensitive capability
  • get_live_alphano sensitive capability
  • get_momentum_moversno sensitive capability
  • get_open_ordersno sensitive capability
  • get_opportunitiesno sensitive capability
  • get_order_fillsno sensitive capability
  • get_pair_intelligenceno sensitive capability
  • get_positionsno sensitive capability
  • get_price_spread_datano sensitive capability
  • get_rate_chart_datano sensitive capability
  • get_record_roino sensitive capability
  • get_smart_opportunitiesno sensitive capability
  • get_still_payingno sensitive capability
  • get_top_holdersno sensitive capability
  • get_unbroken_streaksno sensitive capability
  • get_weekly_recapno sensitive capability
  • list_credentialsno sensitive capability
  • open_delta_neutralno sensitive capability
  • open_tradeno sensitive capability
  • revoke_all_credentialsno sensitive capability
  • revoke_credentialsno sensitive capability
  • run_backtestno sensitive capability
  • store_credentialsno sensitive capability
  • twap_cancelno sensitive capability
  • twap_close_dnno sensitive capability
  • twap_job_statusno sensitive capability
  • twap_jobsno sensitive capability
  • twap_open_dnno sensitive capability
  • watch_positionno 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.9.6 latest A 99/100 0 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 · 99/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/profunding-mcp/badge.svg)](https://mcptrustchecker.com/registry/profunding-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/profunding-mcp"><img src="https://mcptrustchecker.com/registry/profunding-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/profunding-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 profunding-mcp --online --registry pypi

Use the free API → How scoring works

More in Finance & Commerce