C
Emerging
74/100
1 day ago

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

the-basilisk-ai

Source: modelscope · also listed on Official

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 →

Install from

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.
🔐
You'll be asked for 3 credentials: POSTHOG_API_KEY, PROPELAUTH_API_KEY, PROPELAUTH_CLIENT_SECRET
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.
configBASE_URIPORT / MCP_URL / Server port and externally-advertised base URL
configLOG_LEVELLogger verbosity
configMCP_URLPORT / / BASE_URI Server port and externally-advertised base URL
🔐 secretPOSTHOG_API_KEY/ POSTHOG_HOST Enable tool-call telemetry
configPOSTHOG_HOSTPOSTHOG_API_KEY / Enable tool-call telemetry
🔐 secretPROPELAUTH_API_KEY✅ Backend integration key for minting service JWTs
configPROPELAUTH_CLIENT_ID/ PROPELAUTH_CLIENT_SECRET ✅ OAuth 2.1 client credentials for token introspection
🔐 secretPROPELAUTH_CLIENT_SECRETPROPELAUTH_CLIENT_ID / ✅ OAuth 2.1 client credentials for token introspection
configSQUAD_ENVEdit .env with your PropelAuth credentials (and =dev to target the dev platform)
configSQUAD_GRAPHQL_URLOverride the Squad GraphQL endpoint (also used by codegen)
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
deployREDIS_URL
// 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

30/30 tools missing one or more hints — list_actions (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_action_context (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); update_action_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +27 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.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

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/the-basilisk-ai-squad-mcp-0j89lw)](https://m8ven.ai/mcp/the-basilisk-ai-squad-mcp-0j89lw)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 78c7b6708a3f9988f7385a956e5b01c74b442fb5
code hash: 65a1e2862c9efe60c74cdd6e4812b1570d074bf2e7ea76bf7c681b3831228d67
verified: 8/21/2026, 1:03:48 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