# SiteHelm (remote · {site_host})

Let an AI agent run your WordPress site: every write previewed, verified and reversible.

- Trust score: 0/100 (low)
- Registry status: active
- Liveness: dead
- Owner verified: no
- Last scored: 2026-09-20

> **Dead**: every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically.

## Components

- remote · `{site_host}`: 0/100 (this document), [markdown](https://verifymcp.io/servers/mrshahidali420-sitehelm/https-site-host-wp-json-sitehelm-v1-mcp.md), [page](https://verifymcp.io/servers/mrshahidali420-sitehelm/https-site-host-wp-json-sitehelm-v1-mcp)

## Channel facts

- Endpoint: `https://{site_host}/wp-json/sitehelm/v1/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.16.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-09-20.

- **Endpoint Security**: 0/100
  - TLS not yet verified: we couldn't open a connection to check the certificate.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS enforcement could not be verified: this endpoint is not published over https, so there is no plaintext variant to compare against.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC not yet verified: we couldn't validate it against a resolver.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but we couldn't connect to verify it.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 6 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the SiteHelm MCP server?

SiteHelm is a hosted endpoint at https://{site_host}/wp-json/sitehelm/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.

### Claude

```bash
claude mcp add --transport http mrshahidali420-sitehelm 'https://{site_host}/wp-json/sitehelm/v1/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "mrshahidali420-sitehelm": {
      "url": "https://{site_host}/wp-json/sitehelm/v1/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "mrshahidali420-sitehelm": {
      "type": "http",
      "url": "https://{site_host}/wp-json/sitehelm/v1/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.mrshahidali420-sitehelm]
url = "https://{site_host}/wp-json/sitehelm/v1/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mrshahidali420-sitehelm": {
      "type": "remote",
      "url": "https://{site_host}/wp-json/sitehelm/v1/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mrshahidali420-sitehelm --url 'https://{site_host}/wp-json/sitehelm/v1/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  mrshahidali420-sitehelm:
    url: "https://{site_host}/wp-json/sitehelm/v1/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "mrshahidali420-sitehelm": {
      "Transport": "http",
      "Url": "https://{site_host}/wp-json/sitehelm/v1/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add mrshahidali420-sitehelm -t streamable-http -u 'https://{site_host}/wp-json/sitehelm/v1/mcp'
```

### Other

```json
{
  "mcpServers": {
    "mrshahidali420-sitehelm": {
      "type": "http",
      "url": "https://{site_host}/wp-json/sitehelm/v1/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-09-14 (score 0)

First indexed and scored.

## MCP tools (0)

No tool schema has been captured from this endpoint yet.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/mrshahidali420-sitehelm/https-site-host-wp-json-sitehelm-v1-mcp#diagnostics

## Score history

- 2026-09-20: 0
- 2026-09-19: 0
- 2026-09-18: 0
- 2026-09-17: 0
- 2026-09-16: 0
- 2026-09-15: 0
- 2026-09-14: 0

## Common questions

### What is the SiteHelm MCP server?

SiteHelm is an MCP server listed in the public MCP registry as io.github.Mrshahidali420/sitehelm. Let an AI agent run your WordPress site: every write previewed, verified and reversible. This page covers its hosted endpoint (https://{site_host}/wp-json/sitehelm/v1/mcp).

### Is the SiteHelm MCP server safe to use?

SiteHelm scores 0 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.

### Does the SiteHelm MCP server require authentication?

Its publisher declares that SiteHelm requires credentials, so you will need to authorise it in your MCP client. We have not been able to confirm that against the live endpoint.

### Is the SiteHelm MCP server still maintained?

SiteHelm has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://{site_host}/wp-json/sitehelm/v1/mcp
- Authorisation metadata: https://{site_host}/.well-known/oauth-protected-resource/wp-json/sitehelm/v1/mcp
- Repository: https://github.com/Mrshahidali420/SiteHelm
- Website: https://www.wpsitehelm.com/
- Changelog RSS feed: https://verifymcp.io/servers/mrshahidali420-sitehelm/https-site-host-wp-json-sitehelm-v1-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/mrshahidali420-sitehelm/https-site-host-wp-json-sitehelm-v1-mcp.json
- HTML version of this page: https://verifymcp.io/servers/mrshahidali420-sitehelm/https-site-host-wp-json-sitehelm-v1-mcp