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.

CompareFairly

REMOTE · COMPAREFAIRLY.COM · SCANNED SEP 20

Neutral, sourced, real-time comparisons on any topic, in 32 languages.

0 this week 83 Trust /100
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
  • Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 355 tokens (~118/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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
  • 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the CompareFairly MCP server?

CompareFairly is a hosted endpoint at https://comparefairly.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 · comparefairly.com

# add to Claude Code
claude mcp add --transport http cgdev2019-comparefairly-mcp 'https://comparefairly.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "cgdev2019-comparefairly-mcp": {
      "url": "https://comparefairly.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "cgdev2019-comparefairly-mcp": {
      "type": "http",
      "url": "https://comparefairly.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.cgdev2019-comparefairly-mcp]
url = "https://comparefairly.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cgdev2019-comparefairly-mcp": {
      "type": "remote",
      "url": "https://comparefairly.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add cgdev2019-comparefairly-mcp --url 'https://comparefairly.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  cgdev2019-comparefairly-mcp:
    url: "https://comparefairly.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "cgdev2019-comparefairly-mcp": {
      "Transport": "http",
      "Url": "https://comparefairly.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add cgdev2019-comparefairly-mcp -t streamable-http -u 'https://comparefairly.com/mcp'
// mcp.json
{
  "mcpServers": {
    "cgdev2019-comparefairly-mcp": {
      "type": "http",
      "url": "https://comparefairly.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 30 Aug 26 +1
    • Stability: 0.97 → pass security
  • 28 Aug 26 +1

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

  • 26 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 +1

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

  • 23 Aug 26 +1

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

  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 1 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 0

    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 20 Sept 2026 · Probed https://comparefairly.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=comparefairly.com CN=YE2,O=Let's Encrypt,C=US 8 Sept 2026 7 Dec 2026 ECDSA 256 ECDSA-SHA384 64e5c56fe44a5fd212f73fe0da5df3f5a11
SANs: comparefairly.com
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

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of comparefairly.com. Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
comparefairly.com. present 63437 8 Verified
comparefairly.com. 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
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy default-src 'self'; img-src 'self' https: data:; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-inline'; connect-src 'self' https:; base-uri 'self'; form-action 'self'; frame-ancestors 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(), microphone=(), camera=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://comparefairly.com/mcp Verified 200
http (plaintext) http://comparefairly.com/mcp HTTPS enforced 308 https://comparefairly.com/mcp
MCP tools · 3 exposed · ~312 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_comparison ~102

Fetch one full structured comparison (items with scores, sub-scores, per-criterion values, badges, sources, sourced/estimate flags, freshness). Neutral ranking, never paid. Data is localized to the requested lang/country.

NameTypeReqDescription
countrystring2-letter country code. Default: US.
langstring2-letter language code. Default: en.
slugstringyesComparison slug (from search_comparisons).

No output schema declared.

No examples provided.

list_categories ~58

List the top-level categories available for a market, with the number of comparisons in each.

NameTypeReqDescription
countrystring2-letter country code. Default: US.
langstring2-letter language code. Default: en.

No output schema declared.

No examples provided.

search_comparisons ~152

Search CompareFairly's catalog of neutral, sourced comparisons for a given market. Returns matching comparisons (title, slug, url, json_url, popularity). Use this first to find the exact slug, then call get_comparison.

NameTypeReqDescription
countrystring2-letter country code (e.g. US, FR, DE, GB). Default: US.
langstring2-letter language code (e.g. en, fr, de, es, it). Default: en.
limitintegerMax results (default 20, max 50).
querystringFree-text query, e.g. 'best electric car' or 'password manager'.

No output schema declared.

No examples provided.

Common questions

What is the CompareFairly MCP server?

CompareFairly is an MCP server listed in the public MCP registry as io.github.cgdev2019/comparefairly-mcp. Neutral, sourced, real-time comparisons on any topic, in 32 languages. This page covers its hosted endpoint (https://comparefairly.com/mcp).

Is the CompareFairly MCP server safe to use?

CompareFairly scores 83 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 CompareFairly MCP server expose?

CompareFairly exposes 3 tools: search_comparisons, get_comparison, list_categories. Their descriptions and schemas cost roughly 312 tokens of context every time the server is loaded.

Does the CompareFairly MCP server require authentication?

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

Is the CompareFairly MCP server still maintained?

CompareFairly is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.