← Registry

eCommerce

sushi-tanji.com

Recommends restaurant courses based on budget and sake preference and provides a TableCheck booking link with selected details.

1 endpoint3 known toolsFirst detected September 25, 2026Last detected September 25, 2026

ENDPOINT 1

https://sushi-tanji.com/wp-json/bmp/v1/mcp

No auth detected

MCP server metadata

Name
sushi-tanji
Version
0.1.0
Capabilities
tools
Server instructions

Oku-Akasaka Sushi Tanji is a sushi counter in Akasaka, Tokyo, by reservation only, with three omakase courses. Use list_courses or recommend_course, then get_booking_link with the course, date and party size the guest chose, and give them the booking_url. The guest chooses the time and confirms on that page; this server never books, never takes payment and cannot see which times are free. Do not state cancellation terms or opening hours: tell the guest to read the restaurant's notice on the booking page ("Message from Venue" in English, 「お店からのお知らせ」 in Japanese, 「商家通知」 in Chinese).

Known tools 3

list_courses

The three courses with price per person and what is included.

Inferred read-only
recommend_course

Suggest a course from the budget per person and whether the guest wants sake.

Inferred read-only
get_booking_link

Link to the restaurant's TableCheck booking page with the course, date and party size already selected.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.sushi-tanji]
url = "https://sushi-tanji.com/wp-json/bmp/v1/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "sushi-tanji": {
      "type": "http",
      "url": "https://sushi-tanji.com/wp-json/bmp/v1/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: sushi-tanji
Remote MCP URL: https://sushi-tanji.com/wp-json/bmp/v1/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "sushi-tanji": {
      "url": "https://sushi-tanji.com/wp-json/bmp/v1/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "sushi-tanji": {
      "type": "http",
      "url": "https://sushi-tanji.com/wp-json/bmp/v1/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "sushi-tanji",
  "transport": "streamable-http",
  "url": "https://sushi-tanji.com/wp-json/bmp/v1/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.