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

Back to MCP Trust IndexM8ven
C
Emerging
74/100
10 days ago

sift-mcp

Valhuntir SIFT platform — MCP servers, gateway, Examiner Portal

→ AppliedIR/sift-mcp· listed on github_code

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

AppliedIR

Source: github_code

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

GitHub

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Secret credentials may flow to a network call
2 flows detected: GITHUB_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 2 credentials: OPENCTI_TOKEN, GITHUB_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.
configVHIR_CASES_DIRRoot directory containing all cases
configVHIR_CASE_DIRActive case directory — enables audit trail. Falls back to ~/.vhir/active_case if unset.
configRAG_INDEX_DIR
configOPENCTI_URL
🔐 secretOPENCTI_TOKEN
configXDG_CONFIG_HOME
🔐 secretGITHUB_TOKEN
configVHIR_EXAMINERExaminer identity for evidence IDs and audit
configFK_DATA_DIR
configRAG_KNOWLEDGE_DIR
configRAG_MODEL_NAME
configRAG_MAX_TOP_K
configRAG_MAX_QUERY_LENGTH
configRAG_MAX_DOWNLOAD_BYTES
configRAG_FETCH_MAX_RETRIES
configRAG_ALLOW_HTTP
configRAG_UNSAFE_PATHS
configRAG_FETCH_RETRY_DELAY
configOPENCTI_STARTUP_TIMEOUT
configOPENCTI_SSL_VERIFY
configVHIR_SHARE_ROOT
configVHIR_ANALYST
configVHIR_AUDIT_DIR
configVHIR_ACTIVE_CASE
configVHIR_LOG_FORMAT
configVHIR_LOG_FILE
configSIFT_CATALOG_DIR
configSIFT_TOOL_PATHSExtra binary search paths (colon-separated)
configSIFT_TIMEOUTDefault command timeout in seconds
configSIFT_HAYABUSA_DIRHayabusa install location
configSIFT_RESPONSE_BUDGET
configSIFT_MAX_OUTPUT
configWT_DATA_DIR
configWT_KNOWN_GOOD_DB
configWT_CONTEXT_DB
configWT_REGISTRY_DB
configWT_LOG_LEVEL
configWT_SKIP_DB_VALIDATION
configANONYMIZED_TELEMETRY
// 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

78/78 tools missing one or more hints — case_init (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); case_activate (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); case_list (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +75 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.

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 2 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/appliedir/sift-mcp)](https://m8ven.ai/mcp/appliedir/sift-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: c67a860ea70c38dc3c5243193a76f0bcbd6db18f
code hash: 4932296ff030217b675b47c49df9a131275bd4db5418519f9f58a94f0859d1ba
verified: 9/3/2026, 7:39:13 PM
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