Oxyforge WordPress
REMOTE · API.OXYFORGE.COM
Create, build and hand over real WordPress sites, hosted by Oxyforge on Google Cloud.
Available components
Last scanned (8 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Cloud Infrastructure
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (delete_file). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability70
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1469 tokens (~133/item across 11 items; 11 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 Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 90% 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 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 12 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
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 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.
- 29 Oct 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.
- 28 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 27 Oct 26 64
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 5 Nov 2026 · Probed https://api.oxyforge.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=oxyforge.com | CN=WE1,O=Google Trust Services,C=US | 15 Oct 2026 | 13 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 8a13f6ca8fa44755135a4d4d50bca327 |
| SANs: oxyforge.com, *.oxyforge.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.oxyforge.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| oxyforge.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.oxyforge.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.oxyforge.com/mcp | HTTPS enforced | 301 | https://api.oxyforge.com/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 →
backup_site Back up a site now ~87
Take a backup of one of the account's sites now, before a risky change (account agent key that may make changes; one every few minutes per site).
| Name | Type | Req | Description |
|---|---|---|---|
| site | string | yes | the site name, from create_site or list_sites |
| token | string | – | the token create_site returned (oxa_...); leave out when Oxyforge is connected with an account agent key |
No output schema declared.
No examples provided.
clear_cache Clear the cache ~68
Clear the page and object cache if a change does not show.
| Name | Type | Req | Description |
|---|---|---|---|
| site | string | yes | the site name, from create_site or list_sites |
| token | string | – | the token create_site returned (oxa_...); leave out when Oxyforge is connected with an account agent key |
No output schema declared.
No examples provided.
create_site Create a WordPress site ~146
Create a new password-protected temporary WordPress site. No account needed. Returns the site name, a token (save it, it is shown once), the visitor login, the WordPress admin login and a claim link for the person.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | a short hint for the address, e.g. "bakery" |
| ref | string | – | an Oxyforge affiliate code, only if the person gave you one (it goes on the claim link so their sign-up is credited) |
| site_password | string | – | visitor password, at least 8 characters; one is made up when left out |
| title | string | – | the WordPress site title |
No output schema declared.
No examples provided.
delete_file Delete a file ~76
Delete a file or folder under wp-content/themes, plugins or uploads.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
| site | string | yes | the site name, from create_site or list_sites |
| token | string | – | the token create_site returned (oxa_...); leave out when Oxyforge is connected with an account agent key |
No output schema declared.
No examples provided.
delete_site Delete the site ~67
Delete a site nobody has claimed yet. Cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| site | string | yes | the site name, from create_site or list_sites |
| token | string | – | the token create_site returned (oxa_...); leave out when Oxyforge is connected with an account agent key |
No output schema declared.
No examples provided.
get_site Site status ~83
State (provisioning, awake, asleep, ...), address, logins while unclaimed, claim link and clocks of a site.
| Name | Type | Req | Description |
|---|---|---|---|
| site | string | yes | the site name, from create_site or list_sites |
| token | string | – | the token create_site returned (oxa_...); leave out when Oxyforge is connected with an account agent key |
No output schema declared.
No examples provided.
list_sites List my sites ~82
The sites in the Oxyforge account this connection belongs to (needs an account agent key, made in the members area under Connect MCP, my.oxyforge.com/mcp). Says whether the key may make changes.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | – | the token create_site returned (oxa_...); leave out when Oxyforge is connected with an account agent key |
No output schema declared.
No examples provided.
login_link WordPress admin login link ~76
A one-use link into wp-admin, valid five minutes. The browser asks for the visitor login first.
| Name | Type | Req | Description |
|---|---|---|---|
| site | string | yes | the site name, from create_site or list_sites |
| token | string | – | the token create_site returned (oxa_...); leave out when Oxyforge is connected with an account agent key |
No output schema declared.
No examples provided.
read_files List or read files ~103
List a folder (a path without a file extension) or read a file under wp-content/themes, plugins or uploads.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | e.g. "themes/bakery" or "themes/bakery/style.css" |
| site | string | yes | the site name, from create_site or list_sites |
| token | string | – | the token create_site returned (oxa_...); leave out when Oxyforge is connected with an account agent key |
No output schema declared.
No examples provided.
run_wp_cli Run a WP-CLI command ~151
Run one WP-CLI command on the site, without the leading "wp", e.g. "post create --post_type=page --post_title=About --post_status=publish --porcelain". Put long content in stdin and use "-" as the file argument. eval, shell and db import/export are not available.
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | yes | the WP-CLI command line without "wp" |
| site | string | yes | the site name, from create_site or list_sites |
| stdin | string | – | standard input for the command (optional) |
| token | string | – | the token create_site returned (oxa_...); leave out when Oxyforge is connected with an account agent key |
No output schema declared.
No examples provided.
write_file Write a file ~144
Create or replace a file under wp-content/themes, wp-content/plugins or wp-content/uploads, e.g. path "themes/bakery/style.css". Folders are made as needed. Use content for text or content_base64 for binary (25 MB at most).
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | – |
| content_base64 | string | – | – |
| path | string | yes | relative to wp-content, starting with themes/, plugins/ or uploads/ |
| site | string | yes | the site name, from create_site or list_sites |
| token | string | – | the token create_site returned (oxa_...); leave out when Oxyforge is connected with an account agent key |
No output schema declared.
No examples provided.
How do I install the Oxyforge WordPress MCP server?
Oxyforge WordPress is a hosted endpoint at https://api.oxyforge.com/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 · api.oxyforge.com
claude mcp add --transport http com-oxyforge-wordpress 'https://api.oxyforge.com/mcp'
What is the Oxyforge WordPress MCP server?
Oxyforge WordPress is an MCP server listed in the public MCP registry as com.oxyforge/wordpress. Create, build and hand over real WordPress sites, hosted by Oxyforge on Google Cloud. This page covers its hosted endpoint (https://api.oxyforge.com/mcp).
Is the Oxyforge WordPress MCP server safe to use?
Oxyforge WordPress scores 68 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 Oxyforge WordPress MCP server expose?
Oxyforge WordPress exposes 11 tools: create_site, list_sites, backup_site, get_site, run_wp_cli, and 6 more. Their descriptions and schemas cost roughly 1,083 tokens of context every time the server is loaded.
Does the Oxyforge WordPress MCP server require authentication?
No. We connected to Oxyforge WordPress without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Oxyforge WordPress MCP server still maintained?
Oxyforge WordPress is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.