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.

KnowKensington

REMOTE · KNOWKENSINGTON.COM

Curated places in Kensington, London: restaurants, coffee, pubs, parks and shops.

+7 this week 77 Trust /100

Last scanned (8 hours ago)

Scores higher than 69% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Maps and Location

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. 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 is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability73
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 719 tokens (~102/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 85% 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 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 (13)

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

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.

  • 5 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 4 Nov 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.

  • 3 Nov 26 +5
    • HTTPS: fail → pass ▲ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_guide” rewrote its description, which is the text the model reads security
    • Tool “get_place” rewrote its description, which is the text the model reads security
    • Tool “list_guides” rewrote its description, which is the text the model reads security
    • Tool “list_places” rewrote its description, which is the text the model reads security
    • Tool “search_places” rewrote its description, which is the text the model reads security
    • Server version: 1.1.0 → 1.2.0 functional
    • “search_places” reworded the description of “query” cosmetic
  • 1 Nov 26 0
    • “compare_places” reworded the description of “slugs” cosmetic
    • “get_place” reworded the description of “slug” cosmetic

    2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.

  • 31 Oct 26 +1

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

  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 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 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 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 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 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 5 Nov 2026 · Probed https://knowkensington.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=knowkensington.com CN=YE2,O=Let's Encrypt,C=US 22 Oct 2026 20 Jan 2027 ECDSA 256 ECDSA-SHA384 6ff09f1470fd800af3d5dba4a635a447c1a
SANs: *.knowkensington.com, knowkensington.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 insecure

Validation of knowkensington.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
knowkensington.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
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
content-security-policy base-uri 'self'; object-src 'none'; frame-ancestors 'self'
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), payment=(), interest-cohort=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://knowkensington.com/mcp Verified 200
http (plaintext) http://knowkensington.com/mcp HTTPS enforced 301 https://knowkensington.com/mcp
MCP tools · 7 exposed · ~598 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
compare_places ~59

Side-by-side sourced records for 2 to 4 Kensington places by slug, with the tags they share.

NameTypeReqDescription
slugsarrayyesDistinct place slugs, for example ["lytte-coffee", "the-harwood-arms"]

No output schema declared.

No examples provided.

get_guide ~59

One published Kensington guide by slug: its introduction and its ranked places, every field sourced.

NameTypeReqDescription
limitinteger–Max places to return (default 25)
slugstringyesGuide slug from list_guides, for example brunch

No output schema declared.

No examples provided.

get_place ~46

Full editorial record for one Kensington place by slug, including the guide's description and the public /place URL.

NameTypeReqDescription
slugstringyesURL slug, for example lytte-coffee

No output schema declared.

No examples provided.

list_guides ~35

Published Kensington themed guides (https://knowkensington.com/guides/{slug}), with sourced titles, summaries and place counts.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_places ~120

Curated places in Kensington, optionally filtered by category, use-case tag or featured picks. Each result links to its https://knowkensington.com/place/{slug} page; ranked pages live at https://knowkensington.com/best/{category}.

NameTypeReqDescription
categorystring–Place category, for example coffee or restaurant
featuredboolean–When true, only return featured picks
limitinteger–Max places to return (default 25)
tagstring–Use-case tag, for example brunch or with-kids

No output schema declared.

No examples provided.

nearby_places ~80

Nearest curated Kensington places to a WGS84 coordinate supplied in the request, with distance in metres.

NameTypeReqDescription
categorystring––
latitudenumberyes–
limitinteger–Max places to return (default 10)
longitudenumberyes–
radiusinteger–Search radius in metres (default 500)

No output schema declared.

No examples provided.

search_places ~199

Filter curated Kensington places by category, sub-zone, tags, featured picks or text, ranked like https://knowkensington.com/best/{category}. Every field carries its source; addresses, coordinates, hours, websites and photos are not included, so follow each place url for them. open_now only matches owner-supplied or official-site hours, and none are recorded yet.

NameTypeReqDescription
categorystring–Place category, for example coffee or restaurant
featuredboolean–When true, only return featured picks
limitinteger–Max places to return (default 25)
open_nowboolean–When true, only places open now by owner-supplied or official-site hours
querystring–Text matched against names and the guide's descriptions and tips
sub_zonestring–Part of Kensington
tagsarray–Use-case tags; a place must carry every tag given

No output schema declared.

No examples provided.

Install

How do I install the KnowKensington MCP server?

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

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

What is the KnowKensington MCP server?

KnowKensington is an MCP server listed in the public MCP registry as com.knowkensington/places. Curated places in Kensington, London: restaurants, coffee, pubs, parks and shops. This page covers its hosted endpoint (https://knowkensington.com/mcp).

Is the KnowKensington MCP server safe to use?

KnowKensington scores 77 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 KnowKensington MCP server expose?

KnowKensington exposes 7 tools: list_places, get_place, nearby_places, search_places, compare_places, and 2 more. Their descriptions and schemas cost roughly 598 tokens of context every time the server is loaded.

Does the KnowKensington MCP server require authentication?

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

Is the KnowKensington MCP server still maintained?

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

VerifyMCP ran 13 checks on KnowKensington, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.