Petro MCP Server
petro-mcp
PyPI
v1.1.1
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.
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 − 2 = 98. 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:
| Points | Adoption-risk factor |
|---|---|
| −2 | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read |
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 Shell/command execution in packaging/dev tooling (tests/test_server.py)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_server.py:73`): 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: self): result = subprocess.run( [sys.executable, "-m", "petro_mcp.server", "--list-tools"],
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_server.py
Tools 19
Each tool and what it can reach — statically extracted from the published source.
calculate_archie_swno sensitive capabilitycalculate_bubble_pointno sensitive capabilitycalculate_density_porosityno sensitive capabilitycalculate_eurno sensitive capabilitycalculate_gas_zno sensitive capabilitycalculate_net_payno sensitive capabilitycalculate_pvt_propertiesno sensitive capabilitycalculate_vshaleno sensitive capabilitycompare_logsno sensitive capabilityconvert_oilfield_unitsno sensitive capability
Show 9 more tools ↓
fit_declineno sensitive capabilityget_curve_valuesno sensitive capabilitylist_oilfield_unitsno sensitive capabilitypz_analysisno sensitive capabilityquery_productionno sensitive capabilityread_lasno sensitive capabilityrecovery_factorno sensitive capabilityvolumetric_ogipno sensitive capabilityvolumetric_ooipno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (19 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.1.1 latest |
A 98/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.
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 petro-mcp --online --registry pypiMore in Learning & Documentation
Security scan results for the Agentmail MCP server.
Security scan results for the Alfahq MCP server.
Security scan results for the Alpine MCP server.
Search the official Astro framework documentation.
Security scan results for the Atag MCP server.
Security scan results for the Aurais Mcp Research Reader MCP server.