Flocks MCP
MCPB · FLOCKS-MCP.MCPB
Servidor MCP que serve o catálogo de 131 componentes do Flocks (props, uso, a11y) a agentes.
Available components
Last scanned (2 hours ago)
Scores higher than 82% of MCPB servers
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 84 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 680 tokens (~226/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 −3
- Stability: pass → 0.77 functional
- 30 Oct 26 +1
- Stability: 0.97 → pass security
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed mcpb/https://github.com/jotapeconsultoria/flocks/releases/download/v0.1.2/flocks-mcp.mcpb
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_component ~202
Return the full record of one Flocks component: every prop with its type, whether it is required and its default; when to use it and when not to; do and don't; accessibility behaviour; runnable code examples; and related component ids. This is the source of truth for props and usage — prefer it over inferring an API from the component name, because Flocks is not Material and its widgets do not share Material's parameter names. Needs a component id such as "app_badge"; call list_components or search_components if you do not have one.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The component id, snake_case, as returned by list_components or search_components — for example "app_badge". |
| lang | string | – | Language of the returned prose: "en" or "pt". The catalog is written in both at the source, field by field, so neither is a translation of the other and neither is more complete. Defaults to "en". |
No output schema declared.
No examples provided.
list_components ~189
List the components of Flocks, the Flutter design system this server documents — a widgets-only system that uses no Material and no Cupertino. Returns the id, name and one-line summary of every component, optionally narrowed to one category. Use it to discover what exists before writing UI code, or to check whether Flocks already covers a need. It returns summaries on purpose, not full specs: once you have picked an id, call get_component for the props and the usage rules.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Narrow the list to one category: "atom", "molecule" or "organism". Omit it to list every component. |
| lang | string | – | Language of the returned prose: "en" or "pt". The catalog is written in both at the source, field by field, so neither is a translation of the other and neither is more complete. Defaults to "en". |
No output schema declared.
No examples provided.
search_components ~170
Search the Flocks component catalog by free text, matching component names, one-line summaries and full descriptions. Use it when you know the need but not the name — "status pill", "empty state", "date field". Matching ignores case and accents, so Portuguese prose is reachable from an unaccented query. Returns id, name and summary of every match, name matches first; call get_component on a result for the props and the usage rules.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language of the returned prose: "en" or "pt". The catalog is written in both at the source, field by field, so neither is a translation of the other and neither is more complete. Defaults to "en". |
| query | string | yes | Free text to look for. Case- and accent-insensitive. |
No output schema declared.
No examples provided.
How do I install the Flocks MCP server?
Flocks MCP ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. The MCP registry declares no SHA-256 for this bundle, so there is no published digest to check the download against.
mcpb · flocks-mcp.mcpb
Download bundleThe MCP registry declares no SHA-256 for this bundle, so there is no published digest to check it against. Open it with an MCPB-capable host such as Claude Desktop.
What is the Flocks MCP server?
Flocks MCP is listed in the public MCP registry as io.github.jotapeconsultoria/flocks-mcp. Servidor MCP que serve o catálogo de 131 componentes do Flocks (props, uso, a11y) a agentes. This page covers its MCPB bundle (https://github.com/jotapeconsultoria/flocks/releases/download/v0.1.2/flocks-mcp.mcpb).
Is the Flocks MCP server safe to use?
Flocks MCP scores 51 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Flocks MCP server expose?
Flocks MCP exposes 3 tools: list_components, get_component, search_components. Their descriptions and schemas cost roughly 561 tokens of context every time the server is loaded.
What licence is the Flocks MCP server under?
Flocks MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.