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.

Asian Recs

REMOTE · ASIANRECS.COM · SCANNED OCT 7

SF and NYC restaurants, cafes, desserts and bars ranked by how Asian diners rate them.

Available components

+4 this week 77 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 Security80
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 640 tokens (~213/item across 3 items; 3 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 Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
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 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the Asian Recs MCP server?

Asian Recs is a hosted endpoint at https://asianrecs.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 · asianrecs.com

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

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.

  • 7 Oct 26 +2

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 27. That category is still filling its 30-day observation window: 5 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.

  • 3 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.

  • 1 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.

  • 30 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 29 Sept 26 73

    First indexed and scored.

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 7 Oct 2026 · Probed https://asianrecs.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=*.asianrecs.com CN=YR2,O=Let's Encrypt,C=US 26 Sept 2026 25 Dec 2026 RSA 2048 SHA256-RSA 53898d5a52ce7e6d63ace69429d40d61eee
SANs: *.asianrecs.com, asianrecs.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 asianrecs.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
asianrecs.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
Header Value
strict-transport-security max-age=63072000

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://asianrecs.com/api/mcp Verified 200
http (plaintext) http://asianrecs.com/api/mcp HTTPS enforced 308 https://asianrecs.com/api/mcp
MCP tools · 3 exposed · ~460 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_place ~108

Full Asian Recs page for one place: both ratings and the gap, share of reviewers who are Asian, dishes Asian diners mention most, quotes from Asian diners, Google and Yelp ratings, and links (Asian Recs, Google Maps, Yelp, Instagram).

NameTypeReqDescription
citystringyessf = San Francisco, nyc = New York
namestringyesPlace name; partial names work.
typestring–Narrow to one kind of place when a name is ambiguous.

No output schema declared.

No examples provided.

list_filters ~60

Areas, neighborhoods and cuisines available for a city and kind of place, with how many ranked places each has.

NameTypeReqDescription
citystringyessf = San Francisco, nyc = New York
typestring–Kind of place. Default restaurants.

No output schema declared.

No examples provided.

search_places ~292

Find places in San Francisco or New York ranked by how Asian diners rate them. Each result has the Asian diners' rating, everyone else's rating, the gap between them, how many Asian diners reviewed it, top dishes, neighborhood and a link to its page.

NameTypeReqDescription
citystringyessf = San Francisco, nyc = New York
cuisinestring–Cuisine or drink category, e.g. "ramen", "sichuan", "korean", "boba", "dim sum".
limitinteger–Default 10.
locationstring–Neighborhood or area, e.g. "Mission", "East Village", "Flushing", "Manhattan — Downtown".
nearobject–A point to measure distance from; adds distance_mi to results.
querystring–Free text matched against name, cuisine, neighborhood and dishes, e.g. a dish like "soup dumplings".
radius_minumber–With near: only places within this many miles.
sortstring–asian_rating: Asian diners' rating, highest first; loved_more: Biggest gap above everyone else; most_asian_diners: Most Asian diners; share_asian: Highest share of Asian reviewers; distance: Closest…
typestring–Kind of place. Default restaurants.

No output schema declared.

No examples provided.

Common questions

What is the Asian Recs MCP server?

Asian Recs is an MCP server listed in the public MCP registry as com.asianrecs/asianrecs. SF and NYC restaurants, cafes, desserts and bars ranked by how Asian diners rate them. This page covers its hosted endpoint (https://asianrecs.com/api/mcp).

Is the Asian Recs MCP server safe to use?

Asian Recs 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 Asian Recs MCP server expose?

Asian Recs exposes 3 tools: search_places, get_place, list_filters. Their descriptions and schemas cost roughly 460 tokens of context every time the server is loaded.

Does the Asian Recs MCP server require authentication?

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

Is the Asian Recs MCP server still maintained?

Asian Recs is still listed as active in the MCP registry. We last reached this channel on 7 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.