sidq (NexuChat/sidq) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 3 tools. No publisher has claimed this listing.

C
Emerging
74/100

sidq

DataHub-native verification layer: is the catalog telling the truth before an agent trusts it?

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

NexuChat

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 →

Install from

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 2 credentials: GITHUB_TOKEN, DATAHUB_GMS_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.
configSIDQ_REPO_ROOT
configSIDQ_SQL_PATH
configSIDQ_VENV_DIR
configSIDQ_RUNTIME_DIR
configDATAHUB_GMS_URL
configSIDQ_ALLOWED_ORIGINS
configSIDQ_TRUSTED_PROXIES
configSIDQ_RELEASE_SHA
configSIDQ_LANDING_PORT
🔐 secretGITHUB_TOKEN
configSIDQ_DATAHUB_UI_URL
configCLAIMS_SOURCE
configSIDQ_DATAHUB_MCP_COMMAND
configSIDQ_ACTION_PATH
configSIDQ_MODE
configSIDQ_POLICY
configSIDQ_FIXTURE_DIR
configGITHUB_API_URL
configSIDQ_PUBLISH_RESULTS
configOLLAMA_HOST
🔐 secretDATAHUB_GMS_TOKEN~90s
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deploySIDQ_POSTGRES_DSN
// 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

3/3 tools missing one or more hints — check_change (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); verify_context (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); search_verified (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint). 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/nexuchat/sidq)](https://m8ven.ai/mcp/nexuchat/sidq)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 9fa3ea0debca1c3e280636f0ef9476f99e16f9a0
code hash: b048668b80f901e204cfdced9446c2aded269a8fe4ad05341908b83723e1fbd7
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