io.github.Wordpressistic/bridgistic
NPM · BRIDGISTIC-MCP-SERVER
Connect Claude to WordPress safely: signed requests, scoped keys, approvals, logs, snapshots.
Available components
Last scanned (20 hours ago)
Scores higher than 72% of npm servers
Category E-commerce
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Wordpressistic/bridgistic-claude-marketplace). View diagnostics → Pass
- Clear OSI-approved license (GPL-2.0-or-later).Pass
- Actively maintained (last published 29 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 7134 tokens (~132/item across 54 items; 54 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 Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage82
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 46% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 10 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 54 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
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.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 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 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +4
- Stability: unverified → 0.27 ▲ functional
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 4 Nov 2026 · Analysed npm/bridgistic-mcp-server@1.5.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | Wordpressistic/bridgistic-claude-marketplace |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Wordpressistic/bridgistic-claude-marketplace/.github/workflows/release.yml@refs/tags/v1.5.2 |
| Rekor log index | 3088230958 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:6619aff83f229866d0160c37c22c5692cbfd790367a6ecaa118dd509247582dcd310e68502dbb7b81f5b744a7deaf5a2a6b633893b591c09e824f3c59 |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
bridgistic_woo_list_products List WooCommerce products ~187
List store products with pagination. Scope: `woo:products:read`. Args: search, status (draft|publish|...), stock_status (instock|outofstock|onbackorder), category (slug), per_page (≤100), page. Returns id/name/sku/type/status/price/stock per product plus total and has_more. Use this instead of SQL or PHP for any product question — it works the same whether or not the store uses High-Performance Order Storage.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Product category slug. |
| page | integer | – | – |
| per_page | integer | – | – |
| search | string | – | – |
| site | string | – | Site alias to target (e.g. "guns2ammo"). Omit when only one site is configured. |
| status | string | – | – |
| stock_status | string | – | – |
No output schema declared.
No examples provided.
bridgistic_woo_sales_summary WooCommerce sales summary ~131
Revenue, order count, average order value, orders by status, and top products for the last N days (default 30, max 365). Scope: `woo:analytics:read`. Counts only processing, completed, and on-hold orders — pending, cancelled, and failed orders are excluded so the revenue figure reconciles with what the store actually took. The counted statuses are echoed back in the response.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
| site | string | – | Site alias to target (e.g. "guns2ammo"). Omit when only one site is configured. |
No output schema declared.
No examples provided.
bridgistic_woo_update_order_status Change a WooCommerce order's status ~291
Move an order to a different status. Scope: `woo:orders:write`. The status is validated against the statuses this store actually defines, so plugin-added ones work and typos are refused with the valid list. SIDE EFFECTS: a status change fires WooCommerce hooks — customer emails, stock adjustments, and payment-gateway actions. Setting the status back afterwards does not un-send an email or un-restock an item, which is why this is marked destructive, snapshots first, and honours the approval queue. Use dry_run to see the transition before committing.
| Name | Type | Req | Description |
|---|---|---|---|
| approval_id | string | – | Approval id returned by a previous call that needed approval. Re-pass the SAME args plus this id once an admin approves. |
| dry_run | boolean | – | If true, return what WOULD change without modifying anything. Nothing is persisted, snapshotted, or queued. |
| force | boolean | – | Proceed even if a pre-op snapshot could not be taken. Irreversible — use sparingly. |
| id | integer | yes | – |
| note | string | – | Order note recorded alongside the change. |
| site | string | – | Site alias to target (e.g. "guns2ammo"). Omit when only one site is configured. |
| status | string | yes | Target status, e.g. "processing", "completed", "refunded". The "wc-" prefix is optional. |
No output schema declared.
No examples provided.
bridgistic_woo_update_product Update a WooCommerce product ~259
Update an existing product. Scope: `woo:products:write`. Only the fields you pass are changed. Overwrites prior values, so the bridge snapshots the product first and dry_run returns an explicit before/after for exactly the fields supplied.
| Name | Type | Req | Description |
|---|---|---|---|
| approval_id | string | – | Approval id returned by a previous call that needed approval. Re-pass the SAME args plus this id once an admin approves. |
| description | string | – | – |
| dry_run | boolean | – | If true, return what WOULD change without modifying anything. Nothing is persisted, snapshotted, or queued. |
| force | boolean | – | Proceed even if a pre-op snapshot could not be taken. Irreversible — use sparingly. |
| id | integer | yes | – |
| manage_stock | boolean | – | – |
| name | string | – | – |
| regular_price | string | – | – |
| sale_price | string | – | – |
| short_description | string | – | – |
| site | string | – | Site alias to target (e.g. "guns2ammo"). Omit when only one site is configured. |
| sku | string | – | – |
| status | string | – | – |
| stock_quantity | integer | – | – |
| stock_status | string | – | – |
No output schema declared.
No examples provided.
How do I install the io.github.Wordpressistic/bridgistic MCP server?
io.github.Wordpressistic/bridgistic runs locally as an npm package, launched with npx -y bridgistic-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · bridgistic-mcp-server
claude mcp add wordpressistic-bridgistic -- npx -y bridgistic-mcp-server
What is the io.github.Wordpressistic/bridgistic MCP server?
io.github.Wordpressistic/bridgistic is an MCP server listed in the public MCP registry as io.github.Wordpressistic/bridgistic. Connect Claude to WordPress safely: signed requests, scoped keys, approvals, logs, snapshots. This page covers its npm package (bridgistic-mcp-server).
Is the io.github.Wordpressistic/bridgistic MCP server safe to use?
io.github.Wordpressistic/bridgistic scores 82 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 io.github.Wordpressistic/bridgistic MCP server expose?
io.github.Wordpressistic/bridgistic exposes 54 tools: bridgistic_list_sites, bridgistic_get_site_info, bridgistic_execute_php, bridgistic_db_query, bridgistic_list_posts, and 49 more. Their descriptions and schemas cost roughly 7,134 tokens of context every time the server is loaded.
Is the io.github.Wordpressistic/bridgistic MCP server still maintained?
io.github.Wordpressistic/bridgistic is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.Wordpressistic/bridgistic MCP server under?
io.github.Wordpressistic/bridgistic declares the GPL-2.0-or-later licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.