Wp BlockmarkupSAFE
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
Give your AI assistant a verified block markup database instead of letting it guess Gutenberg HTML.
wp-blockmarkup-mcp is a local MCP server that extracts, validates, and indexes every Gutenberg block from WordPress core, WooCommerce, or any block-based plugin you work with. It gives AI tools like Claude Code a verified database of block schemas, attributes, and validated markup examples to query — instead of relying on training data that hallucinates block structures, invents attributes, and produces markup that triggers "Attempt Block Recovery" in the editor.
Current validation results: 121 core Gutenberg blocks indexed — 100% of static block markup examples pass both structural and save-function validation.
Why This Exists
AI assistants are increasingly used to generate WordPress content programmatically — building pages via the REST API, migrating content between platforms, populating headless frontends. But every AI model shares the same blind spot: block markup comes from training data, not from the actual block source code.
This means:
- Models invent attributes that don't exist —
fontSizeas a number when it expects a string slug like"large" - Class naming patterns are wrong —
has-background-color-vivid-redinstead ofhas-vivid-red-background-color - Block nesting rules are ignored — putting blocks inside containers that don't support
InnerBlocks - Dynamic blocks get static markup — generating HTML for blocks that only accept comment delimiters with attributes
- Third-party blocks are invisible — WooCommerce blocks, Kadence blocks, ACF blocks are all unknown to training data
- Subtle mismatches break silently — the markup looks right but the editor flags it as invalid, requiring manual recove
c16943f39439OBSERVED · 2026-10-08Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add wp-blockmarkup-mcp --env GEMINI_API_KEY=${GEMINI_API_KEY} -- npx -y [email protected]{
"mcpServers": {
"wp-blockmarkup-mcp": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"GEMINI_API_KEY": "${GEMINI_API_KEY}"
}
}
}
}Exposed tools (6)
6 read · 0 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
get_block_markup | read | Get validated markup examples for a Gutenberg block. Optionally filter by features used (color, typography, spacing, align). Every returned example has been extracted from the block\ |
get_block_schema | read | Get the complete schema for a Gutenberg block: all attributes with types/defaults, support configurations, variations, and validation status. Use the full block name (e.g. |
list_block_attributes | read | List all attributes for a Gutenberg block with their types, defaults, allowed values, sources, and selectors. Useful for constructing specific attribute combinations. |
search_blocks | read | Search Gutenberg blocks across all indexed sources using full-text search. Returns BM25-ranked results with block metadata, type classification, and validation status. |
search_variations | read | Search Gutenberg block variations by name or description. Returns matching variations with their pre-configured attributes and parent block information. |
validate_markup | read | Validate raw Gutenberg block markup structurally. |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (1)
@babel/parser, @babel/traverse, @babel/types, @modelcontextprotocol/sdk, @wordpress/block-serialization-default-parser, better-sqlite3, commander, fast-glob
Gates applied: no_behavioural_pass.
c16943f39439full audit observations/trust-audit/mcp-server/pluginslab__wp-blockmarkup.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-08 | c16943f39439 | SAFE | B | 89 | first audit |
Questions
What tools does Wp Blockmarkup expose?
6 in total: 6 read-only, 0 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is Wp Blockmarkup safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does Wp Blockmarkup need?
It reads GEMINI_API_KEY from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How does Wp Blockmarkup run?
It speaks stdio, so it runs as a local process your client starts. It is published on npm as wp-blockmarkup-mcp at 1.1.1.
How current is this page?
The grade is for one exact copy of the source (c16943f39439), read on 2026-10-08. The repository is watched and re-audited when it changes.