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.

Kahve Tabela — Türkiye heritage, food & coast

REMOTE · KAHVETABELA.COM

Read-only MCP tools for Turkey's heritage places, regional-food atlas, and Mavi Koy coastal atlas.

Available components

0 this week 75 Trust /100

Last scanned (14 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 21 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 Security63
Transport & Reachability100
Schema Quality & AI Usability69
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 449 tokens (~34/item across 13 items; 8 tools + 5 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 Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 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
  • HTTPS
  • 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.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

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.

  • 13 Nov 26 0
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → pass ▲ security
    • TLS certificate: unverified → pass ▲ security
    • HSTS header: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
    • MCP protocol: unverified → fail ▼ functional
    • Endpoint reachability: unreachable → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Schema quality: unverified → 100 ▲ functional
  • 12 Nov 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • HSTS header: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 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
  • 5 Nov 26 0
    • Stability: 0.97 → pass security
  • 4 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Oct 26 0
    • Stability: 0.93 → pass security
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://kahvetabela.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=kahvetabela.com CN=YR2,O=Let's Encrypt,C=US 6 Nov 2026 4 Feb 2027 RSA 2048 SHA256-RSA 6fee6f04c5a514d6145a8e3495f05dbae27
SANs: kahvetabela.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
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 kahvetabela.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
kahvetabela.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
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' 'wasm-unsafe-eval'; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; img-src 'self' data: blob: https:; frame-src 'self' https://www.openstreetmap.org https://www.google.com https://maps.google.com; media-src 'self' data: blob: https://auth.kahvetabela.com https://auzlkoqzqhlbgmccqzaa.supabase.co; connect-src 'self' blob: https://auth.kahvetabela.com https://*.supabase.co https://tiles.openfreemap.org https://*.openstreetmap.org https://www.wikidata.org https://commons.wikimedia.org; worker-src 'self' blob:; object-src 'none'; base-uri 'self'; form-action 'self'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(self)

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://kahvetabela.com/api/mcp Verified 200
http (plaintext) http://kahvetabela.com/api/mcp HTTPS enforced 308 https://kahvetabela.com/api/mcp
MCP tools · 8 exposed · ~366 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_dish ~34

Fetch one Yöre Sofrası dish by slug.

NameTypeReqDescription
langstring––
slugstringyes–

No output schema declared.

No examples provided.

get_mavi_koy_place ~38

Fetch one Mavi Koy coastal atlas entry by slug.

NameTypeReqDescription
langstring––
slugstringyes–

No output schema declared.

No examples provided.

get_page_markdown ~30

Render a supported public Kahve Tabela path as compact markdown.

NameTypeReqDescription
pathstringyes–

No output schema declared.

No examples provided.

get_place ~34

Fetch one Kahve Tabela public heritage place by id.

NameTypeReqDescription
idstringyes–
langstring––

No output schema declared.

No examples provided.

nearby_places ~52

Return nearby public heritage places for a coordinate.

NameTypeReqDescription
audioboolean––
langstring––
latnumberyes–
limitinteger––
lonnumberyes–

No output schema declared.

No examples provided.

search_dishes ~63

Search Yöre Sofrası public regional-food records.

NameTypeReqDescription
categorystring––
citystring––
giOnlyboolean––
langstring––
limitinteger––
qstring––

No output schema declared.

No examples provided.

search_mavi_koy ~56

Search Mavi Koy public coastal atlas entries.

NameTypeReqDescription
categorystring––
langstring––
limitinteger––
qstring––
regionstring––

No output schema declared.

No examples provided.

search_places ~59

Search Kahve Tabela public heritage places.

NameTypeReqDescription
categorystring––
citystring––
districtstring––
langstring––
limitinteger––
qstring––

No output schema declared.

No examples provided.

Install

How do I install the Kahve Tabela — Türkiye heritage, food & coast MCP server?

Kahve Tabela — Türkiye heritage, food & coast is a hosted endpoint at https://kahvetabela.com/api/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 · kahvetabela.com

# add to Claude Code
claude mcp add --transport http com-kahvetabela-public-read 'https://kahvetabela.com/api/mcp'
Common questions

What is the Kahve Tabela — Türkiye heritage, food & coast MCP server?

Kahve Tabela — Türkiye heritage, food & coast is an MCP server listed in the public MCP registry as com.kahvetabela/public-read. Read-only MCP tools for Turkey's heritage places, regional-food atlas, and Mavi Koy coastal atlas. This page covers its hosted endpoint (https://kahvetabela.com/api/mcp).

Is the Kahve Tabela — Türkiye heritage, food & coast MCP server safe to use?

Kahve Tabela — Türkiye heritage, food & coast scores 75 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 Kahve Tabela — Türkiye heritage, food & coast MCP server expose?

Kahve Tabela — Türkiye heritage, food & coast exposes 8 tools: search_places, get_place, nearby_places, get_page_markdown, search_dishes, and 3 more. Their descriptions and schemas cost roughly 366 tokens of context every time the server is loaded.

Does the Kahve Tabela — Türkiye heritage, food & coast MCP server require authentication?

No. We connected to Kahve Tabela — Türkiye heritage, food & coast without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Kahve Tabela — Türkiye heritage, food & coast MCP server still maintained?

Kahve Tabela — Türkiye heritage, food & coast 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 Kahve Tabela — Türkiye heritage, food & coast MCP server?

VerifyMCP ran 12 checks on Kahve Tabela — Türkiye heritage, food & coast, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Kahve Tabela — Türkiye heritage, food & coast: Authorization. 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.