RivoPress
REMOTE · {SITE}
WordPress MCP server with Verified Writes: 127 tools for Claude/ChatGPT, OAuth 2.1, self-hosted.
Available components
Last scanned (20 hours ago)
Scores higher than 59% of remote servers
Reachable. Last reached 21 Nov 2026.
Category E-commerce
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 7856 tokens (~61/item across 127 items; 127 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 8 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "posts_publish" implies "publish" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 128 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 16 Nov 26 +38
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: 0 functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- 15 Nov 26 33
First indexed and scored.
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 21 Nov 2026 · Probed https://rivopress.com/wp-json/rivopress/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=rivopress.com | CN=YE1,O=Let's Encrypt,C=US | 14 Nov 2026 | 12 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 504601b3cf709a744db76a432baa705cc8f |
| SANs: rivopress.com, www.rivopress.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of rivopress.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| rivopress.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
| Header | Value |
|---|---|
| content-security-policy | upgrade-insecure-requests |
| x-content-type-options | nosniff |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | No resource metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://rivopress.com/wp-json/rivopress/v1/mcp | Verified | 200 | |
| http (plaintext) | http://rivopress.com/wp-json/rivopress/v1/mcp | HTTPS enforced | 301 | https://rivopress.com/wp-json/rivopress/v1/mcp |
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 →
tags_update ~71
Update a term in tags. Only provided fields change. Verified after writing.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | New description. |
| id | integer | yes | Term ID. |
| name | string | – | New name. |
| parent_id | integer | – | New parent term ID. |
| slug | string | – | New slug. |
No output schema declared.
No examples provided.
themes_list ~17
All installed themes with the active one marked.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
themes_switch ~39
Switch the active theme by stylesheet slug. Verified by re-reading the active theme.
| Name | Type | Req | Description |
|---|---|---|---|
| stylesheet | string | yes | Theme stylesheet slug as shown by themes_list. |
No output schema declared.
No examples provided.
traffic_diagnose ~105
Diagnose falling traffic: compare the last 28 days with the previous 28 in Search Console, flag pages whose clicks/position fell beyond thresholds, and classify each (position drop, CTR drop, lost impressions, possible deindex, stale content). Read-only — nothing is changed.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum flagged pages (default 50, max 200). |
| min_impressions | integer | – | Ignore pages with fewer previous impressions than this (default 50). |
No output schema declared.
No examples provided.
traffic_fix_apply ~72
Mark a fix plan as applied — call this AFTER the plan edits were made with the normal tools (posts_update, seo_set, links_apply). Opens a 14-day recheck for every post in the plan, measured against its captured baseline.
| Name | Type | Req | Description |
|---|---|---|---|
| plan_id | integer | yes | Plan id from traffic_fix_plan. |
No output schema declared.
No examples provided.
traffic_fix_plan ~86
Store a Traffic Doctor fix plan: for each post, the fix to make (from the diagnosis). Baselines are captured from Search Console at plan time. Nothing on the site changes in this step.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | Fix items: [{post_id, fix}] where fix describes the change (e.g. "update title", "refresh content", "add internal links"). |
No output schema declared.
No examples provided.
traffic_rechecks ~47
List Traffic Doctor rechecks. Those past their 14-day due date are measured against their baseline (when Search Console is connected) with a verdict: recovered, improved, unchanged or worse.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
undo_change ~42
Undo one journalled change by its change ID (from activity_list). Restores the exact state captured before that write.
| Name | Type | Req | Description |
|---|---|---|---|
| change_id | integer | yes | Change ID. |
No output schema declared.
No examples provided.
undo_last ~18
Undo the connected user's most recent undoable change.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
users_create ~74
Create a user. A strong password is generated internally and NEVER returned — WordPress emails the user a set-password link.
| Name | Type | Req | Description |
|---|---|---|---|
| display_name | string | – | Display name (optional). |
| string | yes | Email address. | |
| role | string | – | Role slug (default subscriber). |
| username | string | yes | Login name. |
No output schema declared.
No examples provided.
users_list ~71
List WordPress users with roles (admin only; no password data exists in the output).
| Name | Type | Req | Description |
|---|---|---|---|
| per_page | integer | – | Items per page (default 20, max 100). |
| role | string | – | Filter by role slug (optional). |
| search | string | – | Search name/email/login (optional). |
No output schema declared.
No examples provided.
users_set_role ~52
Change a user's role. Guards: cannot change your own role; cannot demote the last administrator. Verified Write.
| Name | Type | Req | Description |
|---|---|---|---|
| role | string | yes | New role slug. |
| user_id | integer | yes | User id. |
No output schema declared.
No examples provided.
whitelabel_get ~26
The brand name shown in the wp-admin menu and page headings (white-label).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
whitelabel_set ~59
Set the white-label brand name shown in wp-admin. Empty name resets to "RivoPress". Cosmetics only — endpoints and tool names never change.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Brand name (max 40 chars), or empty to reset. |
No output schema declared.
No examples provided.
woo_coupon_create ~67
Create a coupon. Verified Write.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Discount amount as a decimal string. |
| code | string | yes | Coupon code. |
| description | string | – | Internal description (optional). |
| discount_type | string | – | percent, fixed_cart, fixed_product (default percent). |
No output schema declared.
No examples provided.
woo_coupon_delete ~32
Move a coupon to trash (never a permanent delete). Verified Write.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Coupon id. |
No output schema declared.
No examples provided.
woo_coupons_list ~37
List coupons with amounts and usage.
| Name | Type | Req | Description |
|---|---|---|---|
| per_page | integer | – | Items per page (default 20, max 100). |
No output schema declared.
No examples provided.
woo_order_add_note ~58
Add an order note (optionally emailed to the customer).
| Name | Type | Req | Description |
|---|---|---|---|
| customer_note | boolean | – | Send to the customer (default false = private note). |
| id | integer | yes | Order id. |
| note | string | yes | Note text. |
No output schema declared.
No examples provided.
woo_order_get ~31
One order in detail: items, totals, customer, addresses.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Order id. |
No output schema declared.
No examples provided.
woo_order_set_status ~51
Change an order's status (e.g. completed, on-hold). Verified Write.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Order id. |
| status | string | yes | New status without the wc- prefix. |
No output schema declared.
No examples provided.
woo_orders_list ~66
List recent orders with totals and statuses.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (default 1). |
| per_page | integer | – | Items per page (default 20, max 100). |
| status | string | – | Order status filter, e.g. processing (optional). |
No output schema declared.
No examples provided.
woo_product_create ~143
Create a product (simple type). Verified Write.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Full description (HTML allowed). |
| force | boolean | – | Create even if a same-named product exists (default false). |
| name | string | yes | Product name. |
| regular_price | string | – | Regular price as a decimal string, e.g. "499.00". |
| sale_price | string | – | Sale price (optional). |
| short_description | string | – | Short description (optional). |
| sku | string | – | SKU (optional). |
| status | string | – | publish or draft (default draft). |
| stock_quantity | integer | – | Stock quantity (enables stock management). |
No output schema declared.
No examples provided.
woo_product_get ~23
One product in detail.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Product id. |
No output schema declared.
No examples provided.
woo_product_trash ~33
Move a product to trash (never a permanent delete). Verified Write.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Product id. |
No output schema declared.
No examples provided.
woo_product_update ~123
Update a product's name, prices, SKU, stock or status. Verified Write.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | New description. |
| id | integer | yes | Product id. |
| name | string | – | New name. |
| regular_price | string | – | New regular price. |
| sale_price | string | – | New sale price (empty string clears it). |
| short_description | string | – | New short description. |
| sku | string | – | New SKU. |
| status | string | – | publish, draft or pending. |
| stock_quantity | integer | – | New stock quantity. |
No output schema declared.
No examples provided.
woo_products_list ~74
List products with price, stock and status.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (default 1). |
| per_page | integer | – | Items per page (default 20, max 100). |
| search | string | – | Search by name or SKU. |
| status | string | – | Post status (default publish). |
No output schema declared.
No examples provided.
woo_status ~26
WooCommerce status: active or not, version, currency, store counts. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the RivoPress MCP server?
RivoPress is a hosted endpoint at https://{site}/wp-json/rivopress/v1/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · {site}
claude mcp add --transport http com-rivopress-rivopress 'https://{site}/wp-json/rivopress/v1/mcp'
What is the RivoPress MCP server?
RivoPress is an MCP server listed in the public MCP registry as com.rivopress/rivopress. WordPress MCP server with Verified Writes: 127 tools for Claude/ChatGPT, OAuth 2.1, self-hosted. This page covers its hosted endpoint (https://{site}/wp-json/rivopress/v1/mcp).
Is the RivoPress MCP server safe to use?
RivoPress scores 73 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 RivoPress MCP server expose?
RivoPress exposes 127 tools: site_info, site_health, posts_list, posts_get, posts_create, and 122 more. Their descriptions and schemas cost roughly 7,825 tokens of context every time the server is loaded.
Does the RivoPress MCP server require authentication?
Yes. RivoPress asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the RivoPress MCP server still maintained?
RivoPress is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the RivoPress MCP server?
VerifyMCP ran 13 checks on RivoPress, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.