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.

Ricky Moorhouse's blog

REMOTE · MCP.RICKYMOORHOUSE.UK

Search and read Ricky Moorhouse's posts on API architecture, API Connect, SRE, AI and travel.

69 Trust /100

Last scanned (11 hours ago)

Scores higher than 53% 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 Security66
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 241 tokens (~80/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 71% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (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 405, 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.

  • 21 Nov 26 +1
    • Server version: 0.2.0 → 0.2.1 functional
  • 19 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.

  • 17 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 16 Nov 26 66

    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://mcp.rickymoorhouse.uk/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.rickymoorhouse.uk CN=YE2,O=Let's Encrypt,C=US 19 Nov 2026 17 Feb 2027 ECDSA 256 ECDSA-SHA384 65a0cf5a5e5bca972fc0e95ff523237bbcb
SANs: mcp.rickymoorhouse.uk
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd
CN=ISRG Root X1,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 4 Jun 2015 4 Jun 2035 RSA 4096 SHA256-RSA 8210cfb0d240e3594463e0bb63828b00

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of mcp.rickymoorhouse.uk. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
uk. DS published 43876 8 Verified
rickymoorhouse.uk. DS published 22351 10 Verified
mcp.rickymoorhouse.uk. Verified address RRset verified with the apex keys
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://mcp.rickymoorhouse.uk/mcp Verified 200
http (plaintext) http://mcp.rickymoorhouse.uk/mcp Inconclusive 405
MCP tools · 3 exposed · ~204 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
get_post ~47

Fetch the full text of a page on rickymoorhouse.uk as Markdown, given its URL.

NameTypeReqDescription
urlstringyesURL of a page on rickymoorhouse.uk.

No output schema declared.

No examples provided.

list_recent ~42

List the most recent posts, newest first, optionally from one section.

NameTypeReqDescription
limitinteger––
sectionstring–Only return posts from this section.

No output schema declared.

No examples provided.

search_posts ~115

Full-text search across Ricky Moorhouse's blog posts, microblog notes, talks and projects. Covers API architecture, IBM API Connect, SRE, observability and AI agents, plus travel, photography and walking. Returns matching posts with their URL, date, tags and description; use get_post to read one in full.

NameTypeReqDescription
limitinteger––
querystringyesSearch terms.
sectionstring–Only return posts from this section.
tagstring–Only return posts with this tag.

No output schema declared.

No examples provided.

Install

How do I install the Ricky Moorhouse's blog MCP server?

Ricky Moorhouse's blog is a hosted endpoint at https://mcp.rickymoorhouse.uk/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 · mcp.rickymoorhouse.uk

# add to Claude Code
claude mcp add --transport http uk-rickymoorhouse-blog 'https://mcp.rickymoorhouse.uk/mcp'
Common questions

What is the Ricky Moorhouse's blog MCP server?

Ricky Moorhouse's blog is an MCP server listed in the public MCP registry as uk.rickymoorhouse/blog. Search and read Ricky Moorhouse's posts on API architecture, API Connect, SRE, AI and travel. This page covers its hosted endpoint (https://mcp.rickymoorhouse.uk/mcp).

Is the Ricky Moorhouse's blog MCP server safe to use?

Ricky Moorhouse's blog scores 69 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 Ricky Moorhouse's blog MCP server expose?

Ricky Moorhouse's blog exposes 3 tools: search_posts, get_post, list_recent. Their descriptions and schemas cost roughly 204 tokens of context every time the server is loaded.

Does the Ricky Moorhouse's blog MCP server require authentication?

No. We connected to Ricky Moorhouse's blog without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Ricky Moorhouse's blog MCP server still maintained?

Ricky Moorhouse's blog 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 Ricky Moorhouse's blog MCP server?

VerifyMCP ran 12 checks on Ricky Moorhouse's blog, 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 Ricky Moorhouse's blog: 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.