Mantis (shirelshitrit) MCP Server
@shirelshitrit/mantis-mcp
npm
v0.1.2
Published by @shirelshitrit — 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 − 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:
| Points | Adoption-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 0
Tools 49
Each tool and what it can reach — statically extracted from the published source.
mantis_create_issuenetwork egressmantis_create_issue_notenetwork egressmantis_add_issue_attachmentsno sensitive capabilitymantis_add_issue_relationshipno sensitive capabilitymantis_add_issue_tagsno sensitive capabilitymantis_add_subprojectno sensitive capabilitymantis_create_my_tokenno sensitive capabilitymantis_create_projectno sensitive capabilitymantis_create_project_versionno sensitive capabilitymantis_create_userno sensitive capability
Show 39 more tools ↓
mantis_create_user_tokenno sensitive capabilitymantis_delete_filterno sensitive capabilitymantis_delete_issueno sensitive capabilitymantis_delete_issue_noteno sensitive capabilitymantis_delete_issue_relationshipno sensitive capabilitymantis_delete_my_tokenno sensitive capabilitymantis_delete_projectno sensitive capabilitymantis_delete_project_versionno sensitive capabilitymantis_delete_userno sensitive capabilitymantis_delete_user_tokenno sensitive capabilitymantis_get_configno sensitive capabilitymantis_get_filterno sensitive capabilitymantis_get_issueno sensitive capabilitymantis_get_issue_fileno sensitive capabilitymantis_get_issue_filesno sensitive capabilitymantis_get_issue_view_pageno sensitive capabilitymantis_get_langno sensitive capabilitymantis_get_my_userno sensitive capabilitymantis_get_projectno sensitive capabilitymantis_get_project_versionno sensitive capabilitymantis_get_userno sensitive capabilitymantis_get_user_by_usernameno sensitive capabilitymantis_list_filtersno sensitive capabilitymantis_list_issuesno sensitive capabilitymantis_list_project_handlersno sensitive capabilitymantis_list_project_usersno sensitive capabilitymantis_list_project_versionsno sensitive capabilitymantis_list_projectsno sensitive capabilitymantis_monitor_issueno sensitive capabilitymantis_remove_issue_tagno sensitive capabilitymantis_remove_project_userno sensitive capabilitymantis_reset_user_passwordno sensitive capabilitymantis_set_configno sensitive capabilitymantis_set_project_userno sensitive capabilitymantis_update_issueno sensitive capabilitymantis_update_projectno sensitive capabilitymantis_update_project_versionno sensitive capabilitymantis_update_subprojectno sensitive capabilitymantis_update_userno 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 |
|---|---|---|---|---|
v0.1.2 latest |
A 96/100 | 0 | 1.10.0 | 2026-07-25 |
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 @shirelshitrit/mantis-mcp --onlineOther implementations of Mantis 2
Independent packages implementing the same tool, scanned with the same engine. Compare all 3 side by side →
Security scan results for the Mantis (kfnzero) MCP server.
Security scan results for the Mantis (grec0) MCP server.
More 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.