fusion (yasinyaman/fusion) is an MCP server listed on the M8ven Trust Index. It scores 69 out of 100, grade C. It declares 10 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Limited view
69/100
1 month ago

fusion

Enables LLMs to perform analytical SQL queries on PostgreSQL/MySQL databases via DuckDB, with tools for querying, aggregation, and materialized views.

→ yasinyaman/fusion· listed on glama

Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

Limited view: static analysis for Python is partially covered.

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

yasinyaman

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

Glamanot scored here

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 1 credential: FUSION_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.
configFUSION_ENV
configFUSION_HOST
configFUSION_PORT
configWARP_URL
configWARP_TIMEOUT
configWARP_MAX_RETRIES
configWARP_BACKOFF_FACTOR
configFUSION_DATABASE
configFUSION_MEMORY_LIMIT
configFUSION_THREADS
configFUSION_DUCKDB_EXTERNAL_ACCESS
configFUSION_MAX_TEMP_DIRECTORY_SIZE
configFUSION_MAX_INGEST_ROWS
configFUSION_CACHE_TTL
configFUSION_CACHE_MAX_ENTRIES
🔐 secretFUSION_API_KEY
configFUSION_RATE_LIMIT
configFUSION_RATE_LIMIT_BURST
configFUSION_LOG_LEVEL
configFUSION_LOG_FORMAT
configFUSION_LOG_FILE
configFUSION_CIRCUIT_BREAKER_THRESHOLD
configFUSION_CIRCUIT_BREAKER_TIMEOUT
configFUSION_POOL_SIZE
configFUSION_POOL_MAX_OVERFLOW
configFUSION_BACKUP_ENABLED
configFUSION_BACKUP_INTERVAL
configFUSION_BACKUP_PATH
configFUSION_BACKUP_RETENTION_DAYS
configFUSION_DEBUG_ENDPOINTS
// 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

10/10 tools missing one or more hints — list_sources (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); describe_table (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); query_data (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +7 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

7/10 tool handlers declare input schemas (70%)

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

Tool handlers catch errors

Only 0/10 tool handlers wrap calls in try/catch (0%)

Wrap each tool handler body in try/catch and return a structured error response.

Tests exist

No test files found

Add tests that exercise each declared tool.

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 5 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/yasinyaman/fusion)](https://m8ven.ai/mcp/yasinyaman/fusion)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: ba28e47c7d287bb6767aa303dec282e1ef7a22a8
code hash: 84a6fb8f79a264237046156f4ce3607d7d8e441a123b71c354562d1495c4ab79
verified: 7/21/2026, 8:45:18 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