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.

Dim Hour

REMOTE · MCP.DIMHOUR.COM · 2 COMPONENTS

Search 19,000+ verified places to eat and drink across 24 cities, each with a 0-100 quality score.

−1 this week 81 Trust /100

Last scanned (17 hours ago)

Scores higher than 79% of remote servers

Reachable. Last reached 21 Nov 2026.

Category E-commerce

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
  • 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 enforcement could not be verified: the plaintext port answered with HTTP 406, 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 Usability79
  • 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 2946 tokens (~196/item across 15 items; 14 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 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 16 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 406, 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.

  • 21 Nov 26 0
    • Tool “get_hours” rewrote its description, which is the text the model reads security
  • 20 Nov 26 0
    • Tool “get_booking_options” rewrote its description, which is the text the model reads security
    • “get_booking_options” added an optional parameter “time” cosmetic
  • 18 Nov 26 −1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “find_places” rewrote its description, which is the text the model reads security
    • “search_venues” reworded the description of “sort” cosmetic
  • 15 Nov 26 0
    • Schema quality: 2385 → 2725 ▼ functional
    • New tool “search_menus” functional
  • 13 Nov 26 0
    • Schema quality: 1991 → 2385 ▼ functional
    • New tool “get_venue_menus” functional
    • New tool “get_menu_coverage” functional
  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_hours” rewrote its description, which is the text the model reads security
    • Tool “find_places” rewrote its description, which is the text the model reads security
    • “search_venues” reworded the description of “fields” cosmetic
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 9 Nov 26 +1
    • Stability: 0.97 → 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://mcp.dimhour.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=dimhour.com CN=WE1,O=Google Trust Services,C=US 31 Oct 2026 29 Jan 2027 ECDSA 256 ECDSA-SHA256 f6e57c709e20327a13b30191ea6e210f
SANs: dimhour.com, mcp.dimhour.com, *.mcp.dimhour.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.dimhour.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
dimhour.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://mcp.dimhour.com/mcp Verified 200
http (plaintext) http://mcp.dimhour.com/mcp Inconclusive 406
MCP tools · 14 exposed · ~2,385 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
fetch ~76

Get the full Dim Hour record for one venue by the id returned from `search`: description, signature dishes, address, hours, phone, happy hour, reservation platform, awards, website and Instagram.

NameTypeReqDescription
idstringyesVenue id from `search`, in the form 'city:id' e.g. 'nyc:1367'
NameTypeReqDescription
evidenceobjectyes–
evidence_notestringyes–
idstringyes–
metadataobject––
receiptobjectyes–
textstringyes–
titlestringyes–
urlstringyes–

No examples provided.

find_places ~178

Find places for a specific occasion in one city — the task-shaped entry point. Give the city and what the evening needs (a cuisine, a neighborhood, a budget, a vibe) and it returns ranked, citable venues with a freshness receipt. Use it to plan an outing; use search_venues to browse. It never returns a permanently closed venue; search_venues and get_venue still show one, with closed: true.

NameTypeReqDescription
citystringyesCity name or key from list_cities
limitinteger–Max results, default 6
looking_forstring–What the occasion needs, e.g. 'omakase', 'patio', 'birthday dinner'
max_priceinteger–Max price tier 1-4
neighborhoodstring–Narrow to a neighborhood
NameTypeReqDescription
citystringyes–
notestring––
receiptobjectyes–
showingnumberyes–
total_matchesnumberyes–
venuesarrayyes–

No examples provided.

get_booking_options ~290

How to book one venue: its booking platform and link from the Dim Hour catalog. For SevenRooms venues only, given a date, it also returns real bookable times from SevenRooms. Times are a snapshot from SevenRooms at checkedAt. No table is held. Confirm on the booking page before telling anyone it is booked. Other platforms (Resy, OpenTable and the rest) return no times and a times_note saying so. Given a date, a venue whose stored link is a Resy venue page, an OpenTable /r/ page or a Tock venue or search page also gets booking_url_for_date: the same booking page opened on that date and party size (and time, where the platform takes one). Other link shapes get none and keep booking_url only. It is a link, not a table: nothing is held or checked.

NameTypeReqDescription
citystringyesCity name or key
datestring–Day to check, YYYY-MM-DD. Without it, no times are read.
idintegeryesVenue id from search_venues
partyinteger–Party size, 1-20. Default 2.
timestring–Preferred time, HH:MM 24-hour, used in booking_url_for_date where the platform takes one (OpenTable, Tock). Default 19:00. Reads no times.
NameTypeReqDescription
booking_urlstring|nullyes–
booking_url_for_datestring––
citystringyes–
idnumberyes–
namestringyes–
noticestring––
platformstring|nullyes–
prefillobject––
receiptobjectyes–
timesobject––
times_notestring––
urlstringyes–

No examples provided.

get_hours ~162

Opening hours for one venue, from the Dim Hour catalog. Every answer carries `as_of` and never claims to be live — hours are catalog data, not a live feed, and the receipt says how old they are. Measured 2026-09-16, 82% of venues carry hours; when a venue has none this ABSTAINS and says so rather than guessing. The evidence block separately names each field source and read date; null means unknown. The city-file receipt is not the hours verification date. Confirm with the venue before relying on it.

NameTypeReqDescription
citystringyesCity name or key
idinteger–Venue id from search_venues
namestring–Venue name (used if id not given)
NameTypeReqDescription
citystringyes–
evidenceobjectyes–
evidence_notestringyes–
hoursstring|nullyes–
idnumberyes–
namestringyes–
receiptobjectyes–
urlstringyes–
warningstringyes–

No examples provided.

get_menu_coverage ~183

How many venues in each city have menus Dim Hour can stand behind, counted from one menu snapshot. Every city is listed, including cities with none. Each city splits its public venues three ways, and each split covers every venue once: applicability (food or drink venue, not one, or unknown), source (verified_source, unverified_catalog_link, no_link) and completeness (complete, partial, unavailable, requirements_unknown, not_applicable). structured_content counts venues with verified menu sections; fresh_complete counts complete venues whose every verified menu is 90 days old or less at measured_at. These are counts, not a claim that menus are covered. status is unavailable, with no counts, when the menu snapshot does not match the live catalog; reasons names each city that failed.

NameTypeReqDescription
citystring–City name or key. Omit for every city.
NameTypeReqDescription
citiesarrayyes–
coversstring––
measured_atstringyes–
notestringyes–
policy_versionstring|nullyes–
reasonsarrayyes–
receiptobjectyes–
snapshot_idstring|nullyes–
stale_after_daysnumberyes–
statusstringyes–

No examples provided.

get_my_usage ~59

Your own Dim Hour MCP usage for the current UTC day: total calls, the daily limit for your plan, and calls per tool. Identified callers only (a read-only connection or an API key). Calling it does not count as a call.

Input schema present but exposes no named parameters.

NameTypeReqDescription
countnumber––
daystringyes–
limitnumber|nullyes–
meteredbooleanyes–
planstringyes–
toolsobject––

No examples provided.

get_venue ~95

Get the full Dim Hour record for one venue: description, signature dishes, address, hours, phone, happy hour, reservation platform, awards, website, Instagram, and (for Iconic 50 venues) the long-form story.

NameTypeReqDescription
citystringyesCity name or key
idinteger–Venue id from search_venues
namestring–Venue name (used if id not given)
NameTypeReqDescription
addressstringyes–
awardsstringyes–
city_namestringyes–
closedboolean––
cuisinestringyes–
descriptionstringyes–
dishesarrayyes–
embedded_menuobject––
evidenceobjectyes–
evidence_notestringyes–
happy_hourstringyes–
highlightsarray––
hoursstringyes–
iconicboolean––
idnumberyes–
instagramstringyes–
latnumber––
lngnumber––
namestringyes–
neighborhoodstringyes–
openedstring––
other_locationsarray––
phonestringyes–
photoUrlstringyes–
pricestring––
price_tiernumber––
receiptobjectyes–
reservationstringyes–
scorenumber––
storystring––
tagsarrayyes–
trendingboolean––
urlstringyes–
websitestringyes–

No examples provided.

get_venue_menus ~211

The menus Dim Hour holds for one venue, with the source and date of each. status is verified (menus read from the venue's own site, with sections and prices), link_only (a menu link from the catalog that nobody has verified), no_link, or unavailable. A link_only answer proves nothing about what the menu says. Each menu carries verified_at and a freshness state; past 90 days it is stale, and with no date it is unknown, never fresh. completeness says whether every menu this venue is expected to have is verified; requirements_unknown means nobody has recorded which menus to expect. At most 300 menu items are returned per call; `truncated` counts the rest. Prices and dishes change: confirm with the venue before relying on them.

NameTypeReqDescription
citystringyesCity name or key
idintegeryesVenue id from search_venues
typestring–Only this menu type, e.g. dinner, brunch, cocktails, wine
NameTypeReqDescription
addressstringyes–
applicability–yes–
citystringyes–
city_namestringyes–
completeness–yes–
fresh_completebooleanyes–
idnumberyes–
linkobject––
menusarrayyes–
missing_typesarrayyes–
namestringyes–
policy_versionstring|nullyes–
reasonsarrayyes–
receiptobjectyes–
requirementsobject––
snapshot_idstring|nullyes–
stale_after_daysnumberyes–
statusstringyes–
truncatedobject––
urlstringyes–

No examples provided.

list_cities ~29

List the 26 cities Dim Hour covers, with the city key to pass to the other tools.

Input schema present but exposes no named parameters.

NameTypeReqDescription
citiesarrayyes–

No examples provided.

list_curated ~82

Dim Hour's editorial themed lists for a city (e.g. 'Unmarked Doors' speakeasies). Without list_id: returns all list titles. With list_id: returns that list's venues with editorial notes.

NameTypeReqDescription
citystringyesCity name or key
list_idstring–A list id from the no-arg call
NameTypeReqDescription
citystringyes–
idstring––
listsarray––
notestring––
receiptobjectyes–
subtitlestring––
titlestring––
venuesarray––

No examples provided.

list_new_venues ~147

Venues recently added to the Dim Hour catalog — across all 26 cities or one city. Use for 'what's new on Dim Hour' / new-opening alerts / weekly digests. Scored places to eat and drink come first; hotels, malls, museums and landmarks carry no `score` and follow them. Recency orders within each group. Dates earlier than 2026-06-06 are estimates reconstructed from history.

NameTypeReqDescription
citystring–Optional city name or key; omit for all cities
daysinteger–Look-back window in days, default 30 (max 90)
limitinteger–Max results, default 25
NameTypeReqDescription
citystringyes–
feed_generatedstring––
receiptobjectyes–
showingnumberyes–
total_newnumberyes–
venuesarrayyes–
window_daysnumberyes–

No examples provided.

search ~94

Search Dim Hour's restaurant, bar and venue catalog across all 26 cities. Returns ranked venues with a dimhour.com link for each. Use for questions about where to eat or drink — by cuisine, dish, neighborhood, city, vibe, or award.

NameTypeReqDescription
querystringyesWhat to look for, e.g. 'best ramen in NYC', 'michelin dallas', 'rooftop bar miami'
NameTypeReqDescription
receiptobjectyes–
resultsarrayyes–

No examples provided.

search_menus ~340

Find dishes and drinks by name on the menus Dim Hour has verified from venues' own sites, in one city. Each result names the venue, the dish, its printed price (null when the menu prints none), the menu and section, and source_line, the same source and check date the venue page prints. Only verified menus are searched: a venue whose menu nobody has verified never appears, so zero results means no verified menu lists the dish, not that no venue serves it. Terms match at word starts, in the dish name first and then its description (matched_in says which). Optional filters: max_price keeps rows whose ONE printed price is at or under it (a row with no printed price, or several, never matches and is counted in unpriced_excluded); kind is food or drink; menu matches the printed menu name, e.g. 'happy hour'. total_matches counts the filtered rows. Past 90 days a menu is stale and its rows say so. At most 50 results per call; truncated says how many more matched. Prices and dishes change: confirm with the venue before relying on them.

NameTypeReqDescription
citystringyesCity name or key
kindstring–Only food or only drink sections
limitinteger–Results to return (default 20)
max_pricenumber–Highest printed price, in the menu's currency, e.g. 12
menustring–Printed menu name, e.g. 'happy hour', 'brunch'
querystringyesA dish or drink, e.g. 'guacamole', 'espresso martini'
NameTypeReqDescription
citystringyes–
city_namestringyes–
filtersobject––
policy_versionstring|nullyes–
querystringyes–
reasonsarrayyes–
receiptobjectyes–
resultsarrayyes–
skippedobjectyes–
snapshot_idstring|nullyes–
stale_after_daysnumberyes–
statusstringyes–
termsarrayyes–
total_matchesnumberyes–
truncatedobject––
unpriced_excludednumber––
venues_matchednumberyes–
venues_searchednumberyes–

No examples provided.

search_venues ~439

Search Dim Hour's restaurant, bar and venue catalog. Pass `city` to search one city, or OMIT `city` to search every venue across every city at once (e.g. 'best ramen anywhere', 'michelin spots'). Returns ranked matches with score (0-100 quality), price tier, neighborhood, happy-hour info, and a dimhour.com link. Free-text `query` matches each content word individually across cuisine, dish, vibe, and name (filler like 'best' or 'tonight' is ignored) - one strong keyword beats a sentence; combine with filters.

NameTypeReqDescription
awards_containsstring–Only venues whose awards field matches, e.g. 'michelin', 'james beard', 'bib gourmand'
citystring–City name or key, e.g. 'NYC', 'dallas'. OMIT to search ALL cities at once.
cuisinestring–Filter to a cuisine (substring match)
fieldsarray–Return only these fields on each venue, to keep a result small. `id`, `name` and `url` are in every result, whatever you ask for — `url` is the citation link.
happy_hour_onlyboolean–Only venues with happy hour info
iconic_onlyboolean–Only 'Iconic 50' venues (NYC has these today)
limitinteger–Max results, default 10
max_priceinteger–Max price tier 1-4 ($-$$$$)
min_scorenumber–Minimum quality score 0-100
neighborhoodstring–Filter to a neighborhood (substring match)
querystring–Free text; every content word must appear in name, cuisine, neighborhood, tags, dishes, or description (filler like 'best'/'tonight' is ignored). One strong keyword beats a full sentence.
sortstring–Result order. Default score_desc (highest quality first). Unscored venues come last in both score orders.
trending_onlyboolean–Only trending venues
NameTypeReqDescription
citystring––
notestring––
receiptobjectyes–
scopestring––
showingnumberyes–
total_exactbooleanyes–
total_matchesnumberyes–
venuesarrayyes–

No examples provided.

Install

How do I install the Dim Hour MCP server?

Dim Hour is a hosted endpoint at https://mcp.dimhour.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 · mcp.dimhour.com

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

What is the Dim Hour MCP server?

Dim Hour is an MCP server listed in the public MCP registry as com.dimhour/catalog. Search 19,000+ verified places to eat and drink across 24 cities, each with a 0-100 quality score. This page covers its hosted endpoint (https://mcp.dimhour.com/mcp).

Is the Dim Hour MCP server safe to use?

Dim Hour scores 81 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 Dim Hour MCP server expose?

Dim Hour exposes 14 tools: list_cities, search_venues, list_new_venues, get_venue, search, and 9 more. Their descriptions and schemas cost roughly 2,385 tokens of context every time the server is loaded.

Does the Dim Hour MCP server require authentication?

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

Is the Dim Hour MCP server still maintained?

Dim Hour 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 Dim Hour MCP server?

VerifyMCP ran 13 checks on Dim Hour, 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 Dim Hour: 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.