MCP.Market

Flocks MCP server

by jotapeconsultoria·io.github.jotapeconsultoria/flocks-mcp·v0.1.2

Servidor MCP que serve o catálogo de 131 componentes do Flocks (props, uso, a11y) a agentes.

B78/100grade B
What users say
No reviews yet
Be the first
Safety scan
B78/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Flocks MCP yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Flocks MCP tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.10 · 2026-11-03 · same rubric, same numbers if you re-run it

no findings
  • –Code scanpackage could not be scannedn/a
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 80 days ago12/15
  • Maintainer identityregistry namespace matches repository owner7/10
Overall 78/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Flocks MCP compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
78/100
higher than 57% of 48,255 servers

Install Flocks MCP in Claude Code, Cursor or VS Code

The registry entry has no remote endpoint or installable package.

What the publisher says

From the Flocks MCP repository's README, as published. We do not edit it. Read it on GitHub

Flocks

A Flutter design system built on widgets.dart — no Material, no Cupertino.

flocks.live

Six of the seven packages are published on pub.dev under the jotapeconsultoria.com.br verified publisher. The seventh is the demo, which is a showcase and not a library.

No version numbers in that table on purpose: nothing here gates a hand-written one, and pub.dev already shows the current version of each.

Start at packages/flocks/README.md. The components are browsable at widgetbook.flocks.live.

Working on it

This repo is a pub workspace. Resolve from the root, always:

flutter pub get

That is what makes the adapters and the MCP server resolve flocks against the local package instead of the published one, so a change to the core is felt by them in the same checkout. Each package carries resolution: workspace, so pub get run inside one of them will fail — it is not a broken checkout.

dart format --output=none --set-exit-if-changed .   # formatação
dart analyze                                        # os três pacotes
cd packages/flocks && flutter test --exclude-tags golden
cd packages/flocks && dart run tool/validate_components.dart

Goldens compare pixels and their baselines were generated on macOS arm64, so they run apart, and only there:

cd packages/flocks && flutter test --tags golden

License

MIT — see LICENSE. Bundled third-party assets keep their own licenses: the fonts are SIL Open Font License 1.1, Phosphor Icons is MIT, Lucide is ISC (with the part derived from Feather under its own MIT), and cupertinoicons — a dependency, not a vendored asset — is MIT. Each license text ships beside the files it covers (OFL.txt, assets/icons/LICENSE, assets/fonts/LICENSE-phosphor-, packages/flocks_lucide/assets/fonts/LICENSE-lucide), and each package's README says which apply to it.

Nothing above is checked by us. What we check is on the safety report.

Flocks MCP: common questions

Is Flocks MCP server safe?
Mostly: it is graded B (78/100). Read the Flocks MCP safety report
Does Flocks MCP need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Flocks MCP maintained?
The last commit was 81 days ago (2026-08-15). The latest release is v0.1.2.