# Oxyforge WordPress (remote · api.oxyforge.com)

Create, build and hand over real WordPress sites, hosted by Oxyforge on Google Cloud.

- Trust score: 68/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `api.oxyforge.com`: 68/100 (this document), [markdown](https://verifymcp.io/servers/com-oxyforge-wordpress/api.md), [page](https://verifymcp.io/servers/com-oxyforge-wordpress/api)

## Channel facts

- Endpoint: `https://api.oxyforge.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (delete_file).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 90% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-oxyforge-wordpress 'https://api.oxyforge.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-oxyforge-wordpress": {
      "url": "https://api.oxyforge.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-oxyforge-wordpress": {
      "type": "http",
      "url": "https://api.oxyforge.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-oxyforge-wordpress]
url = "https://api.oxyforge.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-oxyforge-wordpress": {
      "type": "remote",
      "url": "https://api.oxyforge.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-oxyforge-wordpress --url 'https://api.oxyforge.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-oxyforge-wordpress:
    url: "https://api.oxyforge.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-oxyforge-wordpress": {
      "Transport": "http",
      "Url": "https://api.oxyforge.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-oxyforge-wordpress -t streamable-http -u 'https://api.oxyforge.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-oxyforge-wordpress": {
      "type": "http",
      "url": "https://api.oxyforge.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 68, +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.

### 2026-11-02 (score 67, +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.

### 2026-10-31 (score 66, +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.

### 2026-10-29 (score 65, +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.

### 2026-10-28 (score 64, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-27 (score 64)

First indexed and scored.

## MCP tools (11)

### `create_site` (~146 tokens)

Create a WordPress site

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.

Input parameters:

- `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

### `list_sites` (~82 tokens)

List my sites

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.

Input parameters:

- `token` (string): the token create_site returned (oxa_...); leave out when Oxyforge is connected with an account agent key

### `backup_site` (~87 tokens)

Back up a site now

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).

Input parameters:

- `site` (string, required): 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

### `get_site` (~83 tokens)

Site status

State (provisioning, awake, asleep, ...), address, logins while unclaimed, claim link and clocks of a site.

Input parameters:

- `site` (string, required): 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

### `run_wp_cli` (~151 tokens)

Run a WP-CLI command

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.

Input parameters:

- `command` (string, required): the WP-CLI command line without "wp"
- `site` (string, required): 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

### `write_file` (~144 tokens)

Write a file

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).

Input parameters:

- `content` (string)
- `content_base64` (string)
- `path` (string, required): relative to wp-content, starting with themes/, plugins/ or uploads/
- `site` (string, required): 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

### `read_files` (~103 tokens)

List or read files

List a folder (a path without a file extension) or read a file under wp-content/themes, plugins or uploads.

Input parameters:

- `path` (string, required): e.g. "themes/bakery" or "themes/bakery/style.css"
- `site` (string, required): 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

### `delete_file` (~76 tokens)

Delete a file

Delete a file or folder under wp-content/themes, plugins or uploads.

Input parameters:

- `path` (string, required)
- `site` (string, required): 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

### `login_link` (~76 tokens)

WordPress admin login link

A one-use link into wp-admin, valid five minutes. The browser asks for the visitor login first.

Input parameters:

- `site` (string, required): 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

### `clear_cache` (~68 tokens)

Clear the cache

Clear the page and object cache if a change does not show.

Input parameters:

- `site` (string, required): 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

### `delete_site` (~67 tokens)

Delete the site

Delete a site nobody has claimed yet. Cannot be undone.

Input parameters:

- `site` (string, required): 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

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-oxyforge-wordpress/api#diagnostics

## Score history

- 2026-11-05: 68
- 2026-11-04: 68
- 2026-11-03: 67
- 2026-11-02: 67
- 2026-11-01: 66
- 2026-10-31: 66
- 2026-10-30: 65
- 2026-10-29: 65
- 2026-10-28: 64
- 2026-10-27: 64

## Common questions

### 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.

## Links

- Remote endpoint: https://api.oxyforge.com/mcp
- Website: https://oxyforge.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-oxyforge-wordpress/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-oxyforge-wordpress/api.json
- HTML version of this page: https://verifymcp.io/servers/com-oxyforge-wordpress/api