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

Back to MCP Trust IndexM8ven
C
Emerging
74/100

Vex-Skillgit

Headless Skill Hub and GitOps for Agentic Memory. Turn complex codebases and documents into version-controlled, immutable cognitive skills. Featuring AST chunking, cryptographic Delta Updates, and native MCP support for multi-tenant swarms.

→ Shuuida/Vex-Skillgit· listed on github_repo_search

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

⚡ 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

Shuuida

Source: github_repo_search

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
✅
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 3 credentials: VEX_GITHUB_WEBHOOK_SECRET, VEX_QDRANT_API_KEY, VEX_API_KEY
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.
🔐 secretVEX_GITHUB_WEBHOOK_SECRETHMAC secret for GitHub webhook verification
configVEX_CORS_ORIGINSComma-separated CORS allowed origins
configVEX_QDRANT_URL
🔐 secretVEX_QDRANT_API_KEY
configVEX_EMBEDDING_MODELOllama embedding model name
configVEX_VECTOR_DIMENSIONVector dimension (must match model)
configVEX_COLLECTION_NAMEQdrant collection name
configVEX_SCORE_THRESHOLDMinimum similarity score for search results
configVEX_DEFAULT_SEARCH_LIMIT
configVEX_REQUIRE_AUTHEnable API key authentication
🔐 secretVEX_API_KEYAPI key (required when auth is enabled)
configVEX_LOG_LEVELLogging level (DEBUG, INFO, WARNING, ERROR)
configVEX_EMBEDDING_MAX_RETRIES
configVEX_EMBEDDING_RETRY_DELAY
// 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

6/6 tools missing one or more hints — search_vex_skill (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); compare_skill_versions (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_skills (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +3 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 test coverage

Only 1/6 tools referenced in tests (17%)

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 3 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/shuuida/vex-skillgit)](https://m8ven.ai/mcp/shuuida/vex-skillgit)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 5076015064fb23f9b08f039dd58a2b25e1d77ae7
code hash: e96e6464b2e270bdfa4d74dc24001c09d62f51183edccad83d93a85e748f5bc8
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