Jamfmcp MCP Server
jamfmcp
PyPI
v1.0.2
Published by liquidz00 — 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.
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 − 7 = 93. 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 |
|---|---|
| −6 | capability blast radius (high) — 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
high Shell/command execution in server code (src/jamfmcp/cli.py)MTC-SRC-002
In the server's implementation (`src/jamfmcp/cli.py:68`): 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: try: result = subprocess.run(["uv", "--version"], capture_output=True, text=True) return result.return
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 src/jamfmcp/cli.py
Tools 49
Each tool and what it can reach — statically extracted from the published source.
get_advanced_computer_search_detailsno sensitive capabilityget_advanced_computer_searchesno sensitive capabilityget_basic_diagnosticsno sensitive capabilityget_building_detailsno sensitive capabilityget_buildingsno sensitive capabilityget_categoriesno sensitive capabilityget_category_detailsno sensitive capabilityget_compliance_statusno sensitive capabilityget_computer_historyno sensitive capabilityget_computer_inventoryno sensitive capability
Show 39 more tools ↓
get_configuration_profilesno sensitive capabilityget_cvesno sensitive capabilityget_department_detailsno sensitive capabilityget_departmentsno sensitive capabilityget_device_lock_pinno sensitive capabilityget_directory_binding_detailsno sensitive capabilityget_directory_bindingsno sensitive capabilityget_extension_attributesno sensitive capabilityget_group_detailsno sensitive capabilityget_health_scorecardno sensitive capabilityget_jcds_filesno sensitive capabilityget_ldap_server_detailsno sensitive capabilityget_ldap_serversno sensitive capabilityget_licensed_softwareno sensitive capabilityget_licensed_software_detailsno sensitive capabilityget_network_segment_detailsno sensitive capabilityget_network_segmentsno sensitive capabilityget_package_detailsno sensitive capabilityget_packagesno sensitive capabilityget_patch_policiesno sensitive capabilityget_patch_software_title_detailsno sensitive capabilityget_patch_software_titlesno sensitive capabilityget_policiesno sensitive capabilityget_policy_detailsno sensitive capabilityget_profile_detailsno sensitive capabilityget_restricted_softwareno sensitive capabilityget_restricted_software_detailsno sensitive capabilityget_script_detailsno sensitive capabilityget_scriptsno sensitive capabilityget_site_detailsno sensitive capabilityget_sitesno sensitive capabilityget_smart_groupsno sensitive capabilityget_user_detailsno sensitive capabilityget_user_group_detailsno sensitive capabilityget_usersno sensitive capabilityget_webhook_detailsno sensitive capabilityget_webhooksno sensitive capabilitypingno sensitive capabilitysearch_computersno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (49 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.0.2 latest |
A 93/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.
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 jamfmcp --online --registry pypiMore in Developer Tools
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.