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.

Point Topic — UK Broadband Market Reference

REMOTE · MCP.POINT-TOPIC.COM · SCANNED SEP 20

Point Topic public MCP: UK broadband market reference data — ISPs, networks, links and standards.

+3 this week 74 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 Security63
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 237 tokens (~237/item across 1 items; 1 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 Management83
  • Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 50% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "database_tools_execute_query" implies "execute" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
  • An AI judge read all 2 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 Point Topic — UK Broadband Market Reference MCP server?

Point Topic — UK Broadband Market Reference is a hosted endpoint at https://mcp.point-topic.com/public, 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.point-topic.com

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

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.

  • 20 Sept 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.

  • 18 Sept 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.

  • 16 Sept 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.

  • 13 Sept 26 +1

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

  • 11 Sept 26 +1

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

  • 9 Sept 26 +1

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

  • 7 Sept 26 +1

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

  • 5 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 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 20 Sept 2026 · Probed https://mcp.point-topic.com/public

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.point-topic.com CN=YR1,O=Let's Encrypt,C=US 25 Aug 2026 23 Nov 2026 RSA 4096 SHA256-RSA 5f7f98bb185bdaa69432a8c4026092dc2fb
SANs: mcp.point-topic.com
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.point-topic.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
point-topic.com. absent 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://mcp.point-topic.com/public Verified 200
http (plaintext) http://mcp.point-topic.com/public Inconclusive 404
MCP tools · 1 exposed · ~194 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
database_tools_execute_query ~194

Query Point Topic's public broadband ontology (ClickHouse) — read-only. Exposes the public reference tables (the visitor view): the entity graph of ISPs, network operators, networks, links, link standards and their relationships. Discover tables with SHOW TABLES FROM ontology; inspect columns with DESCRIBE TABLE <name>. Licensed measurement data (footprints, premises, speeds, tariffs, forecasts, take-up, subscribers) is not queryable here and requires a Point Topic licence — denied queries return contact details. Only SELECT/WITH/SHOW/DESCRIBE/EXPLAIN allowed; returns CSV (large results are truncated at ~50k tokens with a leading notice — add LIMIT to keep results small).

NameTypeReqDescription
ctx
sql_querystringyesThe SQL query to execute. Only SELECT/WITH/SHOW/DESCRIBE/EXPLAIN allowed.
NameTypeReqDescription
resultstringyes

No examples provided.

Common questions

What is the Point Topic — UK Broadband Market Reference MCP server?

Point Topic — UK Broadband Market Reference is an MCP server listed in the public MCP registry as com.point-topic/point-topic-mcp-public. Point Topic public MCP: UK broadband market reference data, ISPs, networks, links and standards. This page covers its hosted endpoint (https://mcp.point-topic.com/public).

Is the Point Topic — UK Broadband Market Reference MCP server safe to use?

Point Topic — UK Broadband Market Reference scores 74 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 Point Topic — UK Broadband Market Reference MCP server expose?

Point Topic — UK Broadband Market Reference exposes 1 tool: database_tools_execute_query. Their descriptions and schemas cost roughly 194 tokens of context every time the server is loaded.

Does the Point Topic — UK Broadband Market Reference MCP server require authentication?

No. We connected to Point Topic — UK Broadband Market Reference without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Point Topic — UK Broadband Market Reference MCP server still maintained?

Point Topic — UK Broadband Market Reference 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.