Fluttersdk MCP
Score = points from our five tests (install, handshake, maintenance, docs, license). Not a quality or security rating. Methodology
- Install20/20
- Handshake30/30
- Maintenance0/25
- Docs10/15
- License10/10
Tested npm @fluttersdk/mcp 1.1.3 (MIT; repo anilcancakir/ai). Installed pinned with scripts off (npm --ignore-scripts) and launched: initialize and tools/list over stdio succeeded with no credentials and listed 1 tools (no tool annotations). Real calls: 0 of 1 real function calls passed. Core tools not tested: 70 cap.
Tool-call test (2026-11-19 UTC, direct MCP stdio client, no LLM): fail. 0 of 1 real function calls passed. Evidence: local test run, Nov 19, 2026 UTC.
Transport (tested 2026-11-19 UTC): stdio
Token cost (estimate): approx. 226 tokens, cl100k estimate (1 tool, measured 2026-11-19 UTC, version 1.1.3). This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k_base.
Permissions: 1 read, 0 write (state-changing), 0 unclassified · Auth: none · Rate limit: unknown · Pricing unit: unknown
Auth: none. Rate limit: unknown. Pricing unit: unknown.
search-docs— read
handshake and tools listed without a recorded key or OAuth
Score 70/100 · Tools 1 · Token cost approx. 226 tokens · Compare · Last tested 2026-11-19 UTC · Version tested 1.1.3 · Package @fluttersdk/mcp · Repo anilcancakir/ai
Summary: Fluttersdk MCP completed an MCP handshake without credentials and exposed 1 tools; it is deprecated or archived, so prefer a maintained alternative.
Evidence summary
- Handshake
- pass
- Tools listed
- 1
- Context cost
- approx. 226 tokens, cl100k estimate (1 tools, measured 2026-11-19 UTC, version 1.1.3; an estimate) ranking · add up your servers' context cost
- API key
- No key to connect (handshake passed)
- Tested
- 2026-11-19 UTC
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | npm install @fluttersdk/mcp --ignore-scripts (Node v24.22.1, Linux) succeeded in 1s. |
| handshake | pass | 30 | MCP initialize + tools/list over stdio succeeded with no credentials; 1 tools listed in 7.5s. |
| maintenance | fail | 0 | Deprecated on npm: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. |
| docs | partial | 10 | install instructions present; mcpServers config example present. Check of the package's own README (README shipped in npm package). |
| license | pass | 10 | MIT (OSI-approved). |
Local-model readiness
Token cost (estimate): approx. 226 tokens, cl100k estimate for 1 tools · about 3% of an 8k context. This is an estimate from our testing (counted with cl100k_base).
Small-model friendly (schema heuristic, not a model result): unknown.
Not tested
Small-model task runs: Not yet tested.
What we tested and what we didn't
Tested on 2026-11-19 UTC
- Install from the registry
- We connected with no credentials and asked for its tool list: it listed 1 tool (Method details: MCP
initializethentools/list) - Maintenance signals (last push, archived/deprecated status)
- Docs (README length, install and config example)
- License (OSI-approved or not)
- Token cost (estimate)
Not tested
- Security: not audited (no code review, no permission or data-flow analysis)
- Real tasks (no functional task runs yet)
- Behaviour with real credentials or a real account
- Performance, rate limits or load
- Correctness of results beyond the listed tasks
Methodology: how we test. A high score means it installs and responds, not that giving it access to your data carries no risk.
Known security issues
Not yet checked.
Monthly roundup: MCP security issues, October 2026.
Tool list changes
Baseline recorded from the 2026-11-19 UTC test run; changes appear after the next test.
Snapshot hash (fingerprint of the tool list)
f8911af4fb84: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.
Raw test record (JSON)
{
"name": "@fluttersdk/mcp",
"version": "1.1.3",
"registry": "npm",
"status": "working",
"tested": "2026-11-19",
"tools_count": 1,
"deprecated": true,
"archived": false,
"tests": {
"install": [
"pass",
20,
"`npm install @fluttersdk/mcp --ignore-scripts` (Node v24.22.1, Linux) succeeded in 1s."
],
"handshake": [
"pass",
30,
"MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 1 tools listed in 7.5s."
],
"maintenance": [
"fail",
0,
"Deprecated on npm: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info."
],
"docs": [
"partial",
10,
"install instructions present; `mcpServers` config example present. Check of the package's own README (README shipped in npm package)."
],
"license": [
"pass",
10,
"MIT (OSI-approved)."
]
},
"testedAt": "2026-11-19T06:08:58.537Z"
}Install
npx -y @fluttersdk/mcp
Pin the version we tested
npx -y --ignore-scripts @fluttersdk/mcp@1.1.3
tested 2026-11-19 UTC. Newer versions may differ and were not tested by us.
{
"mcpServers": {
"fluttersdk-mcp": {
"command": "npx",
"args": [
"-y",
"@fluttersdk/mcp@1.1.3"
]
}
}
}Tools listed
search-docs
Quick config
{
"mcpServers": {
"fluttersdk-mcp": {
"command": "npx",
"args": [
"-y",
"@fluttersdk/mcp"
]
}
}
}Setup
- Install. Run
npm install @fluttersdk/mcp --ignore-scripts(Node v24.22.1). This is the exact command we ran on 2026-11-19 UTC. - Configure. Add the mcpServers entry below to your MCP client config.
- Verify. Restart the client and check that tools/list returns tools (1 in our test).
{
"mcpServers": {
"fluttersdk-mcp": {
"command": "npx",
"args": [
"-y",
"@fluttersdk/mcp"
]
}
}
}Test history
- 2026-11-19 UTC: New
- 2026-11-19 UTC: Deprecated
Related: Best dev MCP servers
FAQ
Is Fluttersdk MCP deprecated?
Yes. Fluttersdk MCP is deprecated on npm (as of 2026-11-19 UTC). npm says: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info."
What replaces Fluttersdk MCP?
None identified. We have no evidence of a maintained replacement yet.
Does Fluttersdk MCP need an API key?
No. It completed an MCP handshake with no credentials and listed 1 tools.
Embed the badge
Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.