Asian Recs is an MCP server with 3 tools an agent can call, among them get_place, list_filters, search_places. It answers at https://asianrecs.com/api/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 29 September 2026; the last check, on 15 November 2026, succeeded.
SF and NYC restaurants, cafes, desserts and bars ranked by how Asian diners rate them.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
get_place | 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). Use w Inputs: city, name, type |
list_filters | Areas, neighborhoods and cuisines available for a city and kind of place, with how many ranked places each has. Use to find the exact neighborhood and cuisine names search_places accepts, or to answer what is covered. Inputs: city, type |
search_places | 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 Inputs: city, type, cuisine, location, query, near |
Every block below points at https://asianrecs.com/api/mcp. Pick your client and copy.
claude mcp add --transport http asian-recs https://asianrecs.com/api/mcp
{
"mcpServers": {
"asian-recs": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://asianrecs.com/api/mcp"]
}
}
}{
"mcpServers": {
"asian-recs": {
"url": "https://asianrecs.com/api/mcp"
}
}
}{
"servers": {
"asian-recs": {
"type": "http",
"url": "https://asianrecs.com/api/mcp"
}
}
}{
"context_servers": {
"asian-recs": {
"url": "https://asianrecs.com/api/mcp"
}
}
}{
"mcpServers": {
"asian-recs": {
"serverUrl": "https://asianrecs.com/api/mcp"
}
}
}{
"mcpServers": {
"asian-recs": {
"url": "https://asianrecs.com/api/mcp"
}
}
}name: Asian Recs
version: 0.0.1
schema: v1
mcpServers:
- name: Asian Recs
type: streamable-http
url: https://asianrecs.com/api/mcp{
"mcpServers": {
"asian-recs": {
"httpUrl": "https://asianrecs.com/api/mcp"
}
}
}{
"mcpServers": {
"asian-recs": {
"type": "http",
"url": "https://asianrecs.com/api/mcp"
}
}
}{
"mcpServers": {
"asian-recs": {
"url": "https://asianrecs.com/api/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fasianrecs.com%2Fapi%2Fmcp&type=streamable_http&id=asian-recs&name=Asian%20Recs
It answered our last check on 15 November 2026 in 215 ms. Over 4 checks since 29 September 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by asianrecs.com and served from asianrecs.com, the vendor's own domain: https://asianrecs.com/api/mcp.
3, as returned by the server's own tools/list on 18 November 2026: get_place, list_filters, search_places.
It answered our last check on 15 November 2026 in 215 ms. Over 4 checks since 29 September 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://asianrecs.com/api/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.asianrecs. Endpoint host: asianrecs.com. ARD identifier: urn:air:com.asianrecs:mcp:asianrecs.
First indexed 29 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.