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.

Fibre Compare

REMOTE · FIBRECOMPARE.COM

Check which fibre and broadband deals are available at a UK postcode or address (fibrecompare.com).

Available components

+7 this week 88 Trust /100

Last scanned (18 hours ago)

Scores higher than 95% of remote servers

Reachable. Last reached 6 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 Security80
  • 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, and every tool looks verifiably read-only (it declares readOnlyHint: true, starts its name with a read verb and describes no write), so an anonymous caller can read but cannot change anything. We can't see whether a tool returns data specific to one caller, so keep any per-user data behind authorisation. View diagnostics → Pass
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 403, 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability77
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1019 tokens (~254/item across 4 items; 3 tools + 1 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 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.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 5 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
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (13)

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

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 403, 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.

  • 6 Nov 26 +7
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Oct 26 0
    • Stability: 0.97 → pass security
  • 29 Oct 26 +1

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

  • 27 Oct 26 +1

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

  • 25 Oct 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 Oct 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.

  • 21 Oct 26 +1

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

  • 19 Oct 26 +1

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

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

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=fibrecompare.com CN=Amazon RSA 2048 M01,O=Amazon,C=US 17 Jul 2026 30 Jan 2027 RSA 2048 SHA256-RSA c67ec6029807ecc736961df9dacdfdd
SANs: fibrecompare.com, *.fibrecompare.com
CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 23 Aug 2022 23 Aug 2030 RSA 2048 SHA256-RSA 77312380b9d6688a33b1ed9bf9ccda68e0e0f
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of fibrecompare.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
fibrecompare.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://fibrecompare.com/mcp Verified 200
http (plaintext) http://fibrecompare.com/mcp Inconclusive 403
MCP tools · 3 exposed · ~625 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
check_fibre_availability ~479

Check which fibre and broadband deals are available at a UK postcode (or exact address via UPRN/UDPRN) using fibrecompare.com. Returns providers, download speeds, monthly prices, contract lengths, key features and a sign-up link for each deal. Optionally filter by minimum speed, maximum price, provider or contract length.

NameTypeReqDescription
addressstring–House number/name and optionally street, e.g. '12', 'Flat 3, 12', 'Rose Cottage'. If it matches one premises at the postcode the check is done at address level in this same call.
address_keystring–An address_key from a previous result's addresses list. Runs the check for that exact premises.
limitinteger–Maximum number of deals to return (default 5). The full list is always available at view_more_url.
max_contract_monthsinteger–Only return deals with a contract of at most this many months (0 = rolling/no contract).
max_monthly_cost_gbpnumber–Only return deals costing at most this much per month in GBP.
min_download_mbpsnumber–Only return deals whose average download speed is at least this many Mbps (e.g. 100, 500, 900).
postcodestringyesUK postcode to check, e.g. 'SW1A 1AA'. Spacing and case do not matter.
providerstring–Only return deals from providers whose name contains this text, e.g. 'BT', 'Hyperoptic'.
sortstring–Ordering: 'recommended' (default; fibrecompare.com's editorial ranking), 'value' (cheapest effective monthly cost), 'price' (cheapest headline monthly cost), 'speed' (fastest first) or 'site' (backen…
udprnstring–Royal Mail Unique Delivery Point Reference Number, if known and no UPRN is available.
uprnstring–Unique Property Reference Number for the exact premises, if known. Gives an address-level rather than postcode-level answer.
visitor_idstring–The visitor_id from a previous result in this conversation. Reuse it so checks and deal clicks are attributed to the same visit. Omit on the first call.
NameTypeReqDescription
address_levelstringyes–
addressesarray–For postcode-level results: the premises at this postcode. Pass one's address_key back to get an exact-address check.
addresses_notestring––
dealsarrayyes–
display_addressstring––
postcodestringyes–
returned_dealsnumberyes–
total_dealsnumberyes–
udprnstring––
uprnstring––
view_more_urlstringyesfibrecompare.com results page for this address, listing every available deal.
visitor_idstring–Pass back as visitor_id on later calls in this conversation.

No examples provided.

fetch ~51

Compatibility tool paired with search. Retrieves the full details of one broadband deal returned by search, by its id.

NameTypeReqDescription
idstringyesA deal id returned by search (format '<postcode>|<product_id>').
NameTypeReqDescription
idstringyes–
metadataobject––
textstringyes–
titlestringyes–
urlstringyes–

No examples provided.

search ~95

Compatibility tool for clients that require search/fetch (e.g. ChatGPT deep research). Prefer check_fibre_availability. Searches fibrecompare.com for broadband deals available at a UK postcode contained in the query; returns deal ids for fetch.

NameTypeReqDescription
querystringyesFree-text query containing a UK postcode, e.g. 'fibre deals at SW1A 1AA' or 'Hyperoptic EC2A 1AA'.
NameTypeReqDescription
resultsarrayyes–

No examples provided.

Install

How do I install the Fibre Compare MCP server?

Fibre Compare is a hosted endpoint at https://fibrecompare.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 · fibrecompare.com

# add to Claude Code
claude mcp add --transport http com-fibrecompare-availability 'https://fibrecompare.com/mcp'
Common questions

What is the Fibre Compare MCP server?

Fibre Compare is an MCP server listed in the public MCP registry as com.fibrecompare/availability. Check which fibre and broadband deals are available at a UK postcode or address (fibrecompare.com). This page covers its hosted endpoint (https://fibrecompare.com/mcp).

Is the Fibre Compare MCP server safe to use?

Fibre Compare scores 88 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 Fibre Compare MCP server expose?

Fibre Compare exposes 3 tools: check_fibre_availability, search, fetch. Their descriptions and schemas cost roughly 625 tokens of context every time the server is loaded.

Does the Fibre Compare MCP server require authentication?

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

Is the Fibre Compare MCP server still maintained?

Fibre Compare is still listed as active in the MCP registry. We last reached this channel on 6 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 Fibre Compare MCP server?

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