Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Today WP

REMOTE · TODAYWP.COM

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

Available components

0 this week 57 Trust /100

Last scanned (19 hours ago)

Scores higher than 44% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Code Search and Documentation

Trust breakdown (7 categories)

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 Security46
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability check failed: schema churn in the 8 days we've observed: 5 tool removals, 1 breaking changes, 0 auth/transport breaks, 3 additions. See how to fix → Fail
Tool Coverage95
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 85% 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
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 26 −2
    • Stability: 0.20 → fail ▼ security
    • A breaking change shipped without a version bump: still 0.1.0 ▼ security
    • Tool “wp_howto” was removed ▼ security
    • Tool “wp_news” was removed ▼ security
    • Tool “wp_now” was removed ▼ security
    • Tool “wp_plugin” was removed ▼ security
    • 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 security
    • Schema quality: 207 → 301 ▼ functional
    • “wp_feedback” added a required parameter “kind”, so existing callers break ▼ functional
    • “wp_feedback” dropped the required parameter “about” ▼ functional
    • Tool coverage: 59% → 85% ▲ functional
    • Schema quality: good → excellent functional
    • New tool “wp_code” functional
    • New tool “wp_plugins” functional
    • New tool “wp_today” functional
    • “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 cosmetic
  • 18 Nov 26 +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.

  • 16 Nov 26 +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.

  • 14 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 13 Nov 26 56

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://todaywp.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=todaywp.com CN=WE1,O=Google Trust Services,C=US 5 Nov 2026 4 Feb 2027 ECDSA 256 ECDSA-SHA256 229ffa1d8c3363a6131d87dbfe58e1b4
SANs: todaywp.com, www.todaywp.com, *.www.todaywp.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 todaywp.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
todaywp.com. No DS 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://todaywp.com/mcp Verified 200
http (plaintext) http://todaywp.com/mcp Inconclusive 406
MCP tools · 6 exposed · ~1,569 tokens

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 →

Tool Tokens
wp_code ~163

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.

NameTypeReqDescription
namesstringyesExact names, separated by commas: "get_theme_mod, save_post, WP_Query::get_posts, wp plugin list, /wp/v2/posts, core/paragraph"

No output schema declared.

No examples provided.

wp_docs ~159

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.

NameTypeReqDescription
limitinteger––
querystringyesThe task or topic in a few words: "register a custom block", "Elementor custom widget", "speed up WooCommerce"

No output schema declared.

No examples provided.

wp_feedback ~411

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.

NameTypeReqDescription
categorystring–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…
itemstring–The public slug, key, path or tool name: "contact-form-7", "elementor", "wp_security". Needed for a rating
kindstringyesWhat it is about
notestringyesOne or two sentences: what you did and what happened, or what is wrong
phpstring––
scoresobject–For a rating: { scale: 0-10 }, e.g. { "works": 9, "spam": 8 }
tagsarray–For a rating: tags from that kind's list
wordpressstring––

No output schema declared.

No examples provided.

wp_plugins ~174

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.

NameTypeReqDescription
pluginsstringyesUp to 3 slugs or names, separated by commas: "contact-form-7, wpforms-lite". Or a need: "booking plugin"

No output schema declared.

No examples provided.

wp_security ~476

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.

NameTypeReqDescription
detailstring–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…
phpstring–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)
pluginsstring–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…
themesstring–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…
wordpressstring–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

No output schema declared.

No examples provided.

wp_today ~186

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.

NameTypeReqDescription
areastring–Only changelog entries for this area
limitinteger–Maximum changelog entries (default 8, or 50 with area or since)
sincestring–Only changes on or after this date (YYYY-MM-DD), e.g. your training cutoff

No output schema declared.

No examples provided.

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.

remote · todaywp.com

# add to Claude Code
claude mcp add --transport http com-todaywp-todaywp 'https://todaywp.com/mcp'
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.