mcp-server-snipe-it (borgels/mcp-server-snipe-it) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 13 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100
1 month ago

mcp-server-snipe-it

MCP server for the Snipe-IT asset management REST API, enabling read and write operations on assets, licenses, accessories, and more.

→ borgels/mcp-server-snipe-it· listed on glama

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

borgels

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glama

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 2 credentials: MCP_HTTP_TOKEN, SNIPEIT_API_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configHOST
configMCP_ALLOWED_ORIGINS
configMCP_ALLOW_ANY_ORIGIN
configMCP_HTTP_HOST
🔐 secretMCP_HTTP_TOKEN
configMCP_MAX_BODY_BYTES
🔐 secretSNIPEIT_API_TOKENSee .env.example. Required: SNIPEIT_BASE_URL, (personal access token, tied to the creating user's permissions).
configSNIPEIT_AUDIT_LOG
configSNIPEIT_BASE_URLSee .env.example. Required: , SNIPEIT_API_TOKEN (personal access token, tied to the creating user's permissions).
configSNIPEIT_ENABLE_WRITES
configSNIPEIT_TIMEOUT_MS
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

13/13 tools missing one or more hints — snipeit_search_capabilities (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); snipeit_list_assets (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); snipeit_get_asset (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +10 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool inputs are validated

11/13 tool handlers declare input schemas (85%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool test coverage

Only 2/13 tools referenced in tests (15%)

Write tests that reference each tool by name so every tool has at least one test.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 4 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/borgels/mcp-server-snipe-it)](https://m8ven.ai/mcp/borgels/mcp-server-snipe-it)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: efc5a00d22d80b54c740e7a2bb5f1340fc07abd5
code hash: a2a59a350bda7937930865a41cf705f2f1f76a957b974b16aabdce72f680c638
verified: 7/16/2026, 8:45:15 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client