Bricks Builder MCP Server

bricks-builder-mcp npm v3.12.4

Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

Serveur MCP pour piloter Bricks Builder (WordPress) depuis Claude/Codex — édition de pages, gestion d'éléments, audit technique, audit design visuel, upload optimisé WebP. Communauté Discord : https://discord.gg/rX22zHRzH

Trust grade
A
94/100
Last scanned get badge →
Trust
A · 94/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 99 − adoption risk = 94/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 1.2 = 99. What the published surface and source actually contain:

PointsWhat was foundCategory
−1.2 Package runs install-time scripts MTC-SUP-010 supply-chain

2. Client adoption risk — 99 − 5 = 94. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

low Package runs install-time scripts (postinstall)MTC-SUP-010

"bricks-builder-mcp" executes postinstall script(s) at install time. An install hook runs at install time; most are routine build/setup, but review what it does before trusting it.

Evidence: node -e "console.log('\n[bricks-builder-mcp] Pour activer verify_element/audit_page/audit_design_page, lance UNE FOIS :\n npx playwright install chromium\n')"

Fix: Review the scripts; install with --ignore-scripts where possible and vet what they do.

Location: package bricks-builder-mcp

Tools 73

Each tool and what it can reach — statically extracted from the published source.

  • get_page_custom_codeingests untrusted input
  • get_page_jsoningests untrusted input
  • get_page_structureingests untrusted input
  • list_bricks_optionsreads sensitive data
  • update_page_jsoningests untrusted input
  • add_color_to_paletteno sensitive capability
  • add_elementno sensitive capability
  • add_menu_itemno sensitive capability
  • analyze_json_structureno sensitive capability
  • audit_design_pageno sensitive capability
Show 63 more tools ↓
  • audit_pageno sensitive capability
  • batch_addno sensitive capability
  • check_skill_versionno sensitive capability
  • create_global_classno sensitive capability
  • create_pageno sensitive capability
  • create_postno sensitive capability
  • create_taxonomy_termno sensitive capability
  • create_theme_styleno sensitive capability
  • delete_custom_fontno sensitive capability
  • delete_elementno sensitive capability
  • delete_global_classno sensitive capability
  • delete_pageno sensitive capability
  • delete_postno sensitive capability
  • delete_theme_styleno sensitive capability
  • duplicate_pageno sensitive capability
  • find_elementsno sensitive capability
  • get_bricks_optionno sensitive capability
  • get_code_execution_statusno sensitive capability
  • get_custom_codeno sensitive capability
  • get_elementno sensitive capability
  • get_element_schemano sensitive capability
  • get_filter_schemano sensitive capability
  • get_global_stylesno sensitive capability
  • get_postno sensitive capability
  • health_checkno sensitive capability
  • list_all_pagesno sensitive capability
  • list_bricks_pagesno sensitive capability
  • list_color_paletteno sensitive capability
  • list_componentsno sensitive capability
  • list_css_variablesno sensitive capability
  • list_custom_fontsno sensitive capability
  • list_global_classesno sensitive capability
  • list_mediano sensitive capability
  • list_menusno sensitive capability
  • list_missing_featuresno sensitive capability
  • list_post_typesno sensitive capability
  • list_postsno sensitive capability
  • list_spacing_scalesno sensitive capability
  • list_theme_stylesno sensitive capability
  • list_typography_scalesno sensitive capability
  • register_custom_fontno sensitive capability
  • register_google_font_locallyno sensitive capability
  • reorder_sectionsno sensitive capability
  • report_missing_featureno sensitive capability
  • resolve_missing_featureno sensitive capability
  • set_code_executionno sensitive capability
  • set_css_variableno sensitive capability
  • set_custom_codeno sensitive capability
  • set_homepageno sensitive capability
  • set_page_custom_codeno sensitive capability
  • set_spacing_scaleno sensitive capability
  • set_typography_scaleno sensitive capability
  • update_elementno sensitive capability
  • update_global_classno sensitive capability
  • update_global_stylesno sensitive capability
  • update_page_metano sensitive capability
  • update_postno sensitive capability
  • update_theme_styleno sensitive capability
  • upload_local_fileno sensitive capability
  • upload_local_files_batchno sensitive capability
  • upload_mediano sensitive capability
  • upload_media_batchno sensitive capability
  • verify_elementno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v3.12.4 latest A 94/100 1 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 94/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/bricks-builder-mcp/badge.svg)](https://mcptrustchecker.com/registry/bricks-builder-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/bricks-builder-mcp"><img src="https://mcptrustchecker.com/registry/bricks-builder-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/bricks-builder-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan bricks-builder-mcp --online

Use the free API → How scoring works

More in Content Management