# Today WP (remote · todaywp.com)

Current WordPress knowledge for AI agents: versions, security, plugin facts, news and docs.

- Trust score: 57/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `todaywp.com`: 57/100 (this document), [markdown](https://verifymcp.io/servers/com-todaywp-todaywp/todaywp.md), [page](https://verifymcp.io/servers/com-todaywp-todaywp/todaywp)

## Channel facts

- Endpoint: `https://todaywp.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

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

- **Endpoint Security**: 46/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 (wp_feedback).
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 63/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1811 tokens (~301/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability check failed: schema churn in the 8 days we've observed: 5 tool removals, 1 breaking changes, 0 auth/transport breaks, 3 additions.
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 85% 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.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Today WP MCP server?

Today WP is a hosted endpoint at https://todaywp.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-todaywp-todaywp 'https://todaywp.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-todaywp-todaywp": {
      "url": "https://todaywp.com/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.com-todaywp-todaywp]
url = "https://todaywp.com/mcp"
```

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  com-todaywp-todaywp:
    url: "https://todaywp.com/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "com-todaywp-todaywp": {
      "type": "http",
      "url": "https://todaywp.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-20 (score 57, −2)

- [security regression] Stability: 0.20 → fail
- [security regression] A breaking change shipped without a version bump: still 0.1.0
- [security regression] Tool “wp_howto” was removed
- [security regression] Tool “wp_news” was removed
- [security regression] Tool “wp_now” was removed
- [security regression] Tool “wp_plugin” was removed
- [security regression] Tool “wp_report” was removed
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “wp_docs” rewrote its description, which is the text the model reads
- [security] Tool “wp_feedback” rewrote its description, which is the text the model reads
- [security] Tool “wp_security” rewrote its description, which is the text the model reads
- [security] Tool “wp_feedback” is now declared destructive
- [functional regression] Schema quality: 207 → 301
- [functional regression] “wp_feedback” added a required parameter “kind”, so existing callers break
- [functional regression] “wp_feedback” dropped the required parameter “about”
- [functional improvement] Tool coverage: 59% → 85%
- [functional] Schema quality: good → excellent
- [functional] New tool “wp_code”
- [functional] New tool “wp_plugins”
- [functional] New tool “wp_today”
- [cosmetic] “wp_feedback” added an optional parameter “php”
- [cosmetic] “wp_feedback” added an optional parameter “scores”
- [cosmetic] “wp_feedback” added an optional parameter “tags”
- [cosmetic] “wp_security” added an optional parameter “detail”
- [cosmetic] “wp_docs” reworded the description of “query”
- [cosmetic] “wp_feedback” reworded the description of “category”
- [cosmetic] “wp_feedback” reworded the description of “item”
- [cosmetic] “wp_feedback” reworded the description of “note”
- [cosmetic] “wp_security” reworded the description of “wordpress”
- [cosmetic] “wp_feedback” made “category” optional
- [cosmetic] Tool “wp_feedback” changed its title: Flag something wrong or imperfect → Send feedback to Today WP

### 2026-11-18 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 58, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 57, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-13 (score 56)

First indexed and scored.

## MCP tools (6)

### `wp_today` (~186 tokens)

WordPress today

What is true in WordPress today, in one dated call: the current versions of WordPress, PHP, Gutenberg, WP-CLI and the MCP Adapter, the next release with its stage and date, and what changed recently with what to do about it (deprecations, new APIs, security, AI and MCP). Your training data is older than WordPress: call this once before writing or reviewing WordPress code, or when a version question comes up. Pass `since` with your training cutoff to get every change after it, or `area` for one subject.

Input parameters:

- `area` (string): Only changelog entries for this area
- `limit` (integer): Maximum changelog entries (default 8, or 50 with area or since)
- `since` (string): Only changes on or after this date (YYYY-MM-DD), e.g. your training cutoff

### `wp_code` (~163 tokens)

WordPress code reference

Finds the official reference page for exact WordPress names: functions, hooks, classes, methods, WP-CLI commands, REST routes, core blocks and @wordpress packages. Use before writing or reviewing code that calls one, to confirm it exists in WordPress core, since which version, and whether it is deprecated. Pass up to 8 names in one call. Returns links with a one-line summary, never the page content; a name that is not in WordPress core is reported as not found. For a guide or a plugin's documentation, use wp_docs.

Input parameters:

- `names` (string, required): Exact names, separated by commas: "get_theme_mod, save_post, WP_Query::get_posts, wp plugin list, /wp/v2/posts, core/paragraph"

### `wp_docs` (~159 tokens)

Search the WordPress developer docs

Finds the official documentation for a WordPress task or topic: developer handbooks (blocks, themes, plugins, REST API, nonces, cron, roles, caching), step-by-step guides, and the own docs of page builders and major plugins (WooCommerce, ACF, Yoast, Elementor, Bricks and more). Use when you need to know how something is done, or where a product documents it. Returns links with a one-line summary, never the page content. For an exact function, hook or class name, use wp_code.

Input parameters:

- `limit` (integer)
- `query` (string, required): The task or topic in a few words: "register a custom block", "Elementor custom widget", "speed up WooCommerce"

### `wp_plugins` (~174 tokens)

Plugin facts

Dated facts on up to 3 WordPress plugins, from current WordPress.org data: active installs, last update, tested WordPress version, PHP requirement, rating and plain warnings (stale, untested with the current WordPress). Use before recommending, installing, keeping or comparing plugins. Facts only, never a ranking or a pick. A need instead of a name ("booking plugin") returns WordPress.org's own search results with the same facts. Premium and commercial plugins (Gravity Forms, WPML, Elementor Pro) get their vendor and their relation to a free plugin. For vulnerabilities against an installed version, use wp_security.

Input parameters:

- `plugins` (string, required): Up to 3 slugs or names, separated by commas: "contact-form-7, wpforms-lite". Or a need: "booking plugin"

### `wp_security` (~476 tokens)

WordPress and PHP security

Checks a WordPress site against known vulnerabilities and tells what to update first. Use when the user asks if a site is safe or up to date, or before advising on updates or hosting: pass the site's WordPress and PHP versions, plugins and themes (slug:version, or the pasted output of wp plugin list / wp theme list) in one call. Returns an ordered urgent list with the fixed versions, the update commands, and only the plugins and themes that need attention (pass detail "full" for every row). Without a site, returns the latest WordPress and PHP security releases and which branches still get fixes. It compares versions with public records (Wordfence, CVE, CISA KEV): it never scans or logs in to a site.

Input parameters:

- `detail` (string): For a site check. "short" (default): what to do first, and only the plugins and themes that need attention, the others by name. "full": every row with its records, plus the general security actions a…
- `php` (string): The PHP version a site runs, e.g. "8.1.30": says if that branch still gets security fixes (a plugin's minimum PHP can be checked here too, as a branch status)
- `plugins` (string): The site's plugins: "akismet:5.3, contact-form-7:6.0.1, woocommerce", or the raw output of `wp plugin list --fields=name,version,status,update_id --format=csv` (or --format=json) pasted as is. Up to…
- `themes` (string): The site's themes: "astra:4.6, twentytwentyfive:1.2", or the raw output of `wp theme list --fields=name,status,version --format=csv`. Up to 10. Checked for known vulnerabilities against the installed…
- `wordpress` (string): The WordPress version a site runs, e.g. "6.8.2": says if that branch still gets security fixes. Not a plugin's minimum requirement: for what changed since a version, use wp_today with since

### `wp_feedback` (~411 tokens)

Send feedback to Today WP

Tells Today WP how something went, with the user's agreement (ask first: it is public under their name, and the first call returns a one-click sign-in link). Two uses. A rating, after you really used a plugin, page builder, doc, changelog entry or guide for your user: pass kind, item, scores (0 to 10 on that kind's scales) or tags, and a note saying what you did and what happened; for a plugin, wp_plugins gives the exact keys (signals.scaleKeys, signals.tagKeys), for everything else https://todaywp.com/signals.json. A problem, when an answer or page here was wrong, outdated, missing, confusing or broken, or you have an idea: pass kind ("answer" for a tool answer, "site" for todaywp.com), a category and a note. Never include the site address, prompts or code. One rating per item per day; a new one replaces it.

Input parameters:

- `category` (string): For a problem: wrong (A fact that is not true.), outdated (True once, not anymore.), missing (Something an agent needed and did not get.), confusing (Hard to act on, ambiguous or misleading.), broken…
- `item` (string): The public slug, key, path or tool name: "contact-form-7", "elementor", "wp_security". Needed for a rating
- `kind` (string, required): What it is about
- `note` (string, required): One or two sentences: what you did and what happened, or what is wrong
- `php` (string)
- `scores` (object): For a rating: { scale: 0-10 }, e.g. { "works": 9, "spam": 8 }
- `tags` (array): For a rating: tags from that kind's list
- `wordpress` (string)

## Diagnostics

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

## Score history

- 2026-11-21: 57
- 2026-11-20: 57
- 2026-11-19: 59
- 2026-11-18: 59
- 2026-11-17: 58
- 2026-11-16: 58
- 2026-11-15: 57
- 2026-11-14: 57
- 2026-11-13: 56

## Common questions

### What is the Today WP MCP server?

Today WP is an MCP server listed in the public MCP registry as com.todaywp/todaywp. Current WordPress knowledge for AI agents: versions, security, plugin facts, news and docs. This page covers its hosted endpoint (https://todaywp.com/mcp).

### Is the Today WP MCP server safe to use?

Today WP scores 57 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 Today WP MCP server expose?

Today WP exposes 6 tools: wp_today, wp_code, wp_docs, wp_plugins, wp_security, wp_feedback. Their descriptions and schemas cost roughly 1,569 tokens of context every time the server is loaded.

### Does the Today WP MCP server require authentication?

No. We connected to Today WP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Today WP MCP server still maintained?

Today WP 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 Today WP MCP server?

VerifyMCP ran 12 checks on Today WP, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Today WP: HTTPS. 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.

## Links

- Remote endpoint: https://todaywp.com/mcp
- Website: https://todaywp.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-todaywp-todaywp/todaywp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-todaywp-todaywp/todaywp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-todaywp-todaywp/todaywp.json
- HTML version of this page: https://verifymcp.io/servers/com-todaywp-todaywp/todaywp
