MCP server for Atlassian Confluence Data Center - access and manage content
Nothing to run from here
Oxyforge WordPress is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
90/100
tool-list score
11
tools declared
remote
at its publisher
—
calls last 7d
What it does
Create, build and hand over real WordPress sites, hosted by Oxyforge on Google Cloud.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http oxyforge-wordpress-mcp https://api.oxyforge.com/mcp
# 2 — ask your agent for something these tools do
# create_site, list_sites, backup_site and 8 more
Oxyforge WordPress costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
OXAll 1 server
oxyforge1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http oxyforge-wordpress-mcp https://api.oxyforge.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
11 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | no | a short hint for the address, e.g. "bakery" |
| title | string | no | the WordPress site title |
| site_password | string | no | visitor password, at least 8 characters; one is made up when left out |
| ref | string | no | an Oxyforge affiliate code, only if the person gave you one (it goes on the claim link so their sign-up is credited) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| token | string | no | the token create_site returned (oxa_...); leave out when Oxyforge is connected with an account agent key |
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site | string | yes | the site name, from create_site or list_sites |
| token | string | no | the token create_site returned (oxa_...); leave out when Oxyforge is connected with an account agent key |
State (provisioning, awake, asleep, ...), address, logins while unclaimed, claim link and clocks of a site.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site | string | yes | the site name, from create_site or list_sites |
| token | string | no | the token create_site returned (oxa_...); leave out when Oxyforge is connected with an account agent key |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site | string | yes | the site name, from create_site or list_sites |
| token | string | no | the token create_site returned (oxa_...); leave out when Oxyforge is connected with an account agent key |
| command | string | yes | the WP-CLI command line without "wp" |
| stdin | string | no | standard input for the command (optional) |
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site | string | yes | the site name, from create_site or list_sites |
| token | string | no | the token create_site returned (oxa_...); leave out when Oxyforge is connected with an account agent key |
| path | string | yes | relative to wp-content, starting with themes/, plugins/ or uploads/ |
| content | string | no | — |
| content_base64 | string | no | — |
List a folder (a path without a file extension) or read a file under wp-content/themes, plugins or uploads.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site | string | yes | the site name, from create_site or list_sites |
| token | string | no | the token create_site returned (oxa_...); leave out when Oxyforge is connected with an account agent key |
| path | string | yes | e.g. "themes/bakery" or "themes/bakery/style.css" |
Delete a file or folder under wp-content/themes, plugins or uploads.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site | string | yes | the site name, from create_site or list_sites |
| token | string | no | the token create_site returned (oxa_...); leave out when Oxyforge is connected with an account agent key |
| path | string | yes | — |
A one-use link into wp-admin, valid five minutes. The browser asks for the visitor login first.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site | string | yes | the site name, from create_site or list_sites |
| token | string | no | the token create_site returned (oxa_...); leave out when Oxyforge is connected with an account agent key |
Clear the page and object cache if a change does not show.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site | string | yes | the site name, from create_site or list_sites |
| token | string | no | the token create_site returned (oxa_...); leave out when Oxyforge is connected with an account agent key |
Delete a site nobody has claimed yet. Cannot be undone.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site | string | yes | the site name, from create_site or list_sites |
| token | string | no | the token create_site returned (oxa_...); leave out when Oxyforge is connected with an account agent key |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Oxyforge WordPress or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 90 / 100
Release 1.0.0 · scanned 28 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score90
Findings0 threat · 10 capability
Capabilityhigh
Coveragemanifest
Verificationnot in this report
Surface digest317756e7edc5223e57fe534685b48716c78c91043d214b3774674e712036a9ae
Score vectorthreat 100 → client 90
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| create_site | no tags | |
| list_sites | no tags | |
| backup_site | no tags | |
| get_site | no tags | |
| run_wp_cli | code-exec | code-exec: parameter "command" |
| write_file | file-write | file-write: keyword "write_file" in tool name |
| read_files | sensitive-source | sensitive-source: keyword "read_file" |
| delete_file | file-writestate-write | file-write: keyword "delete_file" in tool name; state-write: declares destructiveHint: true |
| login_link | no tags | |
| clear_cache | no tags | |
| delete_site | state-write | state-write: declares destructiveHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
read_files → run_wp_cli
A sensitive-source → external-sink chain exists: read_files → run_wp_cli.
Supply chain and provenance
Integrityfirst-seen
Surface digest317756e7edc5223e
Scanned2026-10-28
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Oxyforge WordPress can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.