Bricky
Before you use Bricky
- Only 3 part/color lookup tools passed in our test. Render tools have not been tested (they need Playwright Chromium).
Score = points from our five tests (install, handshake, maintenance, docs, license). Not a quality or security rating. Methodology
- Install20/20
- Handshake30/30
- Maintenance25/25
- Docs10/15
- License10/10
New / early find
New / early find: first tested 2026-11-09. Tested PyPI bricky-mcp 0.1.0 (Apache-2.0; depends on bricky 0.1.0; repo maxencefaldor/bricky, 20 GitHub stars when tested, created 2026-10-27; not listed on Glama). Initialize and tools/list over stdio succeeded with no credentials and listed 9 tools (build_model, check_model, explain_rule, export_model, render_model, search_colors, search_parts, show_part, write_instructions). Real calls (no LLM, no credentials): search_parts {query:'plate 2x4',limit:3} returned part 3020 Plate 2 x 4; show_part {part:'3001'} returned the Brick 2 x 4 shape and stud map; search_colors {query:'gray'} returned Light/Dark Bluish Gray. Rendering tools need Playwright Chromium (`playwright install chromium`), which we did not install, so render_model/build_model were not called. Author launch post https://x.com/maxencefaldor/status/2116097299625480327; amplified by https://x.com/RobertTLange/status/2117184357727170688. Not an official LEGO product.
Tool-call test (2026-11-09, direct MCP stdio client, no LLM): pass. 3 of 3 read-only calls passed. Render/build tools not called (need Playwright Chromium). Evidence: local test run, Nov 9, 2026.
Transport (tested 2026-11-09): stdio
Tested version: 0.1.0 · tested 2026-11-09
Token cost (estimate): approx. 2127 tokens, cl100k estimate (9 tools, measured 2026-11-11, version 0.1.0). This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k_base.
Permissions: 4 read, 5 write (state-changing), 0 unclassified · Auth: none · Rate limit: unknown · Pricing unit: unknown
Auth: none. Rate limit: unknown. Pricing unit: unknown.
build_model— write (state-changing)check_model— readexplain_rule— readexport_model— write (state-changing)render_model— write (state-changing)search_colors— readsearch_parts— readshow_part— write (state-changing)write_instructions— write (state-changing)
handshake and tools listed without a recorded key or OAuth
Score 95/100 · Tools 9 · Token cost approx. 2,127 tokens · Compare · Last tested 2026-11-09 · Version tested 0.1.0 · Package bricky-mcp · Repo maxencefaldor/bricky
Summary: Bricky completed an MCP handshake without credentials and exposed 9 tools.
Evidence summary
- Handshake
- pass
- Tools listed
- 9
- Context cost
- approx. 2127 tokens, cl100k estimate (9 tools, measured 2026-11-11, version 0.1.0; an estimate) ranking · add up your servers' context cost
- API key
- No key needed for the tools we called
- Tested
- 2026-11-09
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | uv pip install bricky-mcp (Python venv, Linux) succeeded in 2s. |
| handshake | pass | 30 | MCP initialize + tools/list over stdio succeeded with no credentials; 9 tools listed in 1.5s. |
| maintenance | pass | 25 | Repo pushed 9 days before test; 20 GitHub stars. |
| docs | partial | 10 | install instructions present; mcpServers config example present. Check of the package's own README (PyPI long_description (package README)). |
| license | pass | 10 | Apache-2.0 (OSI-approved). |
Local-model readiness
Token cost (estimate): approx. 2127 tokens, cl100k estimate for 9 tools · about 26% 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-09
- Install from the registry
- We connected with no credentials and asked for its tool list: it listed 9 tools (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
Checked on 2026-11-09 for version 0.1.0 against OSV, GitHub advisories, GitHub repository advisories. Scope: the package itself; dependencies not scanned.
No published advisories found in OSV and GitHub advisories for bricky-mcp 0.1.0 as of 2026-11-09. This is not a security audit.
Monthly roundup: MCP security issues, October 2026.
Tool list changes
Unchanged since the previous snapshot (latest 2026-11-11).
Snapshot hash (fingerprint of the tool list)
86a9f90496fc: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.
Raw test record (JSON)
{
"name": "bricky-mcp",
"version": "0.1.0",
"registry": "pypi",
"status": "working",
"tested": "2026-11-09",
"tools_count": 9,
"deprecated": false,
"archived": false,
"tests": {
"install": [
"pass",
20,
"`uv pip install bricky-mcp` (Python venv, Linux) succeeded in 2s."
],
"handshake": [
"pass",
30,
"MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 9 tools listed in 1.5s."
],
"maintenance": [
"pass",
25,
"Repo pushed 9 days before test; 20 GitHub stars."
],
"docs": [
"partial",
10,
"install instructions present; `mcpServers` config example present. Check of the package's own README (PyPI long_description (package README))."
],
"license": [
"pass",
10,
"Apache-2.0 (OSI-approved)."
]
}
}Install
uvx bricky-mcp
Pin the version we tested
uvx bricky-mcp==0.1.0
pip install bricky-mcp==0.1.0
tested 2026-11-09. Newer versions may differ and were not tested by us.
{
"mcpServers": {
"bricky": {
"command": "uvx",
"args": [
"bricky-mcp==0.1.0"
]
}
}
}Tools listed
build_model, check_model, explain_rule, export_model, render_model, search_colors, search_parts, show_part, write_instructions
Tool history: captured Nov 11, 2026. All tool history.
Quick config
{
"mcpServers": {
"bricky": {
"command": "uvx",
"args": [
"bricky-mcp"
]
}
}
}Add to config Opens the config generator with this server selected.
Setup
- Install. Run
uv pip install bricky-mcp(Python venv). This is the exact command we ran on 2026-11-09. - Configure. Add the mcpServers entry below to your MCP client config.
- Verify. Restart the client and check that tools/list returns tools (9 in our test).
{
"mcpServers": {
"bricky": {
"command": "uvx",
"args": [
"bricky-mcp"
]
}
}
}Test history
- 2026-11-09: New
Related: Best design MCP servers
FAQ
Is Bricky deprecated?
No. bricky-mcp was not deprecated or archived when we last tested it on 2026-11-09.
What replaces Bricky?
Nothing; Bricky is not deprecated as of 2026-11-09.
Does Bricky need an API key?
No. It completed an MCP handshake with no credentials and listed 9 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.