ohm-mcp
PyPI
v1.0.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.
Each tool and what it can reach — statically extracted from the published source.
analyze_architectureno sensitive capabilityanalyze_codebaseno sensitive capabilityanalyze_performanceno sensitive capabilityanalyze_tight_couplingno sensitive capabilityanalyze_type_hintsno sensitive capabilityanalyze_wildcard_importsno sensitive capabilityapply_function_refactorno sensitive capabilityapply_refactoringno sensitive capabilitycleanup_old_backupsno sensitive capabilitycreate_refactor_patchno sensitive capabilitydetect_code_duplicatesno sensitive capabilitydetect_dead_codeno sensitive capabilityexplain_refactoringno sensitive capabilityextract_function_codeno sensitive capabilityextract_method_astno sensitive capabilitygenerate_characterization_testsno sensitive capabilitygenerate_quality_reportno sensitive capabilitygenerate_test_for_functionno sensitive capabilitygenerate_type_stubno sensitive capabilityprioritize_by_coverageno sensitive capabilitypropose_function_refactorno sensitive capabilityrefactor_importsno sensitive capabilityrefactor_single_file_importsno sensitive capabilityrename_symbolno sensitive capabilityrollback_refactoringno sensitive capabilityshow_refactoring_historyno sensitive capabilitysuggest_design_patternsno sensitive capabilitysuggest_di_refactorno sensitive capabilitysuggest_extractable_methodsno sensitive capabilitysuggest_testsno sensitive capabilityScan 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.0.1 latest |
A 98/100 | 0 | 1.9.0 | 2026-07-23 |
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.
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 ohm-mcp --online --registry pypi
Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →
Security scan results for the 1stay MCP server.
Security scan results for the Adguard Home MCP server.
Security scan results for the Ado Browser MCP server.
Security scan results for the Adobe Experience Dev MCP server.
Security scan results for the Aemet MCP server.
Security scan results for the Affinity Mcp Bridge MCP server.