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.

Still Relevant

REMOTE · STILLRELEVANT.UK

Send a fax from your AI agent to the UK and 108 countries. Pay per fax, charged only if delivered.

Available components

65 Trust /100

Last scanned (16 hours ago)

Scores higher than 46% of remote servers

Reachable. Last reached 21 Nov 2026.

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 Usability68
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 405 tokens (~202/item across 2 items; 2 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 Management3
  • Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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 0
    • Stability: unverified → 0.03 ▲ functional
  • 20 Nov 26 65

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

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=stillrelevant.uk CN=WE1,O=Google Trust Services,C=US 20 Nov 2026 18 Feb 2027 ECDSA 256 ECDSA-SHA256 87ffd2e8a8038f7f13e6b1ab26cb7219
SANs: stillrelevant.uk, *.stillrelevant.uk
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 secure

Validation of stillrelevant.uk. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
uk. DS published 43876 8 Verified
stillrelevant.uk. DS published 2371 13 Verified
stillrelevant.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://stillrelevant.uk/mcp Verified 200
http (plaintext) http://stillrelevant.uk/mcp Inconclusive 405
MCP tools · 2 exposed · ~333 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
fax_status ~45

Check whether a fax has been paid for, is sending, was delivered (charged) or failed (not charged).

NameTypeReqDescription
idstringyesThe id returned by send_fax.

No output schema declared.

No examples provided.

send_fax ~288

Prepare a fax to a fax number anywhere in the world and get a payment link for the user. £2.49 per fax within the UK and to most of Europe, the US and Canada (up to 25 pages); some countries cost more and the exact price comes back in the result. Charged only if the fax is delivered. Accepts almost any document: PDF, Word, images, text, Markdown, spreadsheets, slides. Give the file as a public https URL (file_url) or base64 (file_base64 with filename). Returns pay_url (the user must open it and pay; nothing is sent before that) and status_url. Do not open pay_url yourself.

NameTypeReqDescription
countrystring–Two-letter country code of the fax number, if it has no + code. Default GB.
coverobject–Optional cover page.
file_base64string–The document as base64, if there is no URL.
file_urlstring–Public https URL of the document.
filenamestring–File name with extension, e.g. "letter.docx". Needed with file_base64.
tostringyesFax number. Include the country code ("+44 20 7946 0000") or give country. UK numbers like "020 7946 0000" work without it.

No output schema declared.

No examples provided.

Install

How do I install the Still Relevant MCP server?

Still Relevant is a hosted endpoint at https://stillrelevant.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 · stillrelevant.uk

# add to Claude Code
claude mcp add --transport http uk-stillrelevant-still-relevant 'https://stillrelevant.uk/mcp'
Common questions

What is the Still Relevant MCP server?

Still Relevant is an MCP server listed in the public MCP registry as uk.stillrelevant/still-relevant. Send a fax from your AI agent to the UK and 108 countries. Pay per fax, charged only if delivered. This page covers its hosted endpoint (https://stillrelevant.uk/mcp).

Is the Still Relevant MCP server safe to use?

Still Relevant scores 65 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 Still Relevant MCP server expose?

Still Relevant exposes 2 tools: send_fax, fax_status. Their descriptions and schemas cost roughly 333 tokens of context every time the server is loaded.

Does the Still Relevant MCP server require authentication?

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

Is the Still Relevant MCP server still maintained?

Still Relevant 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 Still Relevant MCP server?

VerifyMCP ran 12 checks on Still Relevant, 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 Still Relevant: 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.