Flutter Analysis Engine (MCP) (Saad0149/Flutter_MCP_Knowledge) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 25 tools. No publisher has claimed this listing.

C
Emerging
74/100

Flutter Analysis Engine (MCP)

Local-first MCP server providing deterministic Flutter/Dart static analysis, knowledge search, and project review with structured insights and confidence-based findings over an indexed SQLite store of official repositories.

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

Saad0149

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 →

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.
// tools this server exposes25 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

update_repositories

Start background shallow clones / pulls for all official Flutter/Dart repos. Returns immediately with per-repo status (queued / in_progress). Poll repository_status to observe progress; call reindex separately when clones finish.

repository_status

Report existence, branch, commit, last pull time, and path for supported repositories.

search_source
find_widget
reindex

Build or refresh the local SQLite knowledge index for one or all repositories.

explain_widget
search_docs
find_examples
find_tests
trace_widget
find_best_practice
review_project
find_intended_behavior
analyze_code_quality
analyze_state_management
analyze_architecture
explain_finding
explore_finding
analyze_complexity
analyze_documentation
analyze_testing
analyze_dependencies
analyze_performance
analyze_accessibility
check_environment

Self-diagnostic: reports whether Dart was found (and via which method/path), Node version, whether the SQLite native binding loaded, and knowledge-base repo readiness. Call this whenever analysis looks degraded or heuristic-only.

// 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.
configFLUTTER_KNOWLEDGE_CONFIGThen set in your MCP client config, e.g. for Cursor:
// 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

25/25 tools missing one or more hints — update_repositories (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); repository_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); search_source (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +22 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.

No arbitrary install scripts

Has postinstall/preinstall script — runs arbitrary code on npm install

Remove postinstall/preinstall hooks unless they’re essential.

Dependency freshness

1/7 production deps stale: reflect-metadata@2024-03-29 (2.4y)

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/saad0149/flutter_mcp_knowledge)](https://m8ven.ai/mcp/saad0149/flutter_mcp_knowledge)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 37fc3ab24d8f04cdbfc6c1b782ed0452b5c7fd68
code hash: 1a3034e4cf6c76a946f60cf2dcdfc49d5cd06ca9ad5328d4c7f7f109eff5ca86
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