Oku-Akasaka Sushi Tanji
REMOTE · SUSHI-TANJI.COM · SCANNED SEP 29
Omakase courses at a sushi counter in Akasaka, Tokyo, with a pre-filled link to the booking page.
Available components
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 Security74
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability44
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 552 tokens (~110/item across 5 items; 4 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 70% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
How do I install the Oku-Akasaka Sushi Tanji MCP server?
Oku-Akasaka Sushi Tanji is a hosted endpoint at https://sushi-tanji.com/wp-json/bmp/v1/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 · sushi-tanji.com
claude mcp add --transport http com-sushi-tanji-reservations 'https://sushi-tanji.com/wp-json/bmp/v1/mcp'
{
"mcpServers": {
"com-sushi-tanji-reservations": {
"url": "https://sushi-tanji.com/wp-json/bmp/v1/mcp"
}
}
} {
"servers": {
"com-sushi-tanji-reservations": {
"type": "http",
"url": "https://sushi-tanji.com/wp-json/bmp/v1/mcp"
}
}
} [mcp_servers.com-sushi-tanji-reservations] url = "https://sushi-tanji.com/wp-json/bmp/v1/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-sushi-tanji-reservations": {
"type": "remote",
"url": "https://sushi-tanji.com/wp-json/bmp/v1/mcp",
"enabled": true
}
}
} openclaw mcp add com-sushi-tanji-reservations --url 'https://sushi-tanji.com/wp-json/bmp/v1/mcp' --transport streamable-http
mcp_servers:
com-sushi-tanji-reservations:
url: "https://sushi-tanji.com/wp-json/bmp/v1/mcp" {
"McpServers": {
"com-sushi-tanji-reservations": {
"Transport": "http",
"Url": "https://sushi-tanji.com/wp-json/bmp/v1/mcp"
}
}
} assistant mcp add com-sushi-tanji-reservations -t streamable-http -u 'https://sushi-tanji.com/wp-json/bmp/v1/mcp'
{
"mcpServers": {
"com-sushi-tanji-reservations": {
"type": "http",
"url": "https://sushi-tanji.com/wp-json/bmp/v1/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 29 Sept 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.
- 28 Sept 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
- 27 Sept 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.
- 26 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 25 Sept 26 65
First indexed and scored.
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 29 Sept 2026 · Probed https://sushi-tanji.com/wp-json/bmp/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sushi-tanji.com | CN=YR2,O=Let's Encrypt,C=US | 26 Jul 2026 | 24 Oct 2026 | RSA 2048 | SHA256-RSA | 5c55eac3ce5efaf5d6371642124ac940daa |
| SANs: sushi-tanji.com, www.sushi-tanji.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 sushi-tanji.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| sushi-tanji.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 |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://sushi-tanji.com/wp-json/bmp/v1/mcp | Verified | 200 | |
| http (plaintext) | http://sushi-tanji.com/wp-json/bmp/v1/mcp | HTTPS enforced | 301 | https://sushi-tanji.com/wp-json/bmp/v1/mcp |
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 →
get_booking_link Open the booking page with the choices filled in ~139
Link to the restaurant's TableCheck booking page with the course, date and party size already selected. The guest picks a time there, agrees to the restaurant's notice, enters their name and contact, and confirms. This tool never books, never takes payment and does not know which times are free. Refuses dates the restaurant has told us it is closed.
| Name | Type | Req | Description |
|---|---|---|---|
| course | string | yes | – |
| date | string | yes | YYYY-MM-DD (Japan time). |
| lang | string | – | ja, en or zh (Simplified Chinese). ko opens the booking page in Korean (texts in English). Default en. |
| people | integer | yes | – |
No output schema declared.
No examples provided.
get_restaurant_info Answer a question about the restaurant ~101
The restaurant's own answer (from its FAQ) about one topic: price, reservation, duration, seating, tea_room, allergies, english, payment or location. Opening hours, lunch and days off are not answered here: point the guest to the booking page.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | ja, en or zh (Simplified Chinese). ko opens the booking page in Korean (texts in English). Default en. |
| topic | string | yes | – |
No output schema declared.
No examples provided.
list_courses Courses and prices at Oku-Akasaka Sushi Tanji ~58
The three courses with price per person and what is included. Prices include tax and service charge.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | ja, en or zh (Simplified Chinese). ko opens the booking page in Korean (texts in English). Default en. |
No output schema declared.
No examples provided.
recommend_course Suggest a course ~111
Suggest a course from the budget per person and whether the guest wants sake. Returns the suggestion with a reason, plus the other courses.
| Name | Type | Req | Description |
|---|---|---|---|
| budget_per_person_jpy | integer | – | Budget per person in JPY, food (and sake if wanted) included. |
| lang | string | – | ja, en or zh (Simplified Chinese). ko opens the booking page in Korean (texts in English). Default en. |
| wants_sake | boolean | – | True if the guest would like sake with the meal. |
No output schema declared.
No examples provided.
What is the Oku-Akasaka Sushi Tanji MCP server?
Oku-Akasaka Sushi Tanji is an MCP server listed in the public MCP registry as com.sushi-tanji/reservations. Omakase courses at a sushi counter in Akasaka, Tokyo, with a pre-filled link to the booking page. This page covers its hosted endpoint (https://sushi-tanji.com/wp-json/bmp/v1/mcp).
Is the Oku-Akasaka Sushi Tanji MCP server safe to use?
Oku-Akasaka Sushi Tanji scores 67 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 Oku-Akasaka Sushi Tanji MCP server expose?
Oku-Akasaka Sushi Tanji exposes 4 tools: list_courses, recommend_course, get_booking_link, get_restaurant_info. Their descriptions and schemas cost roughly 409 tokens of context every time the server is loaded.
Does the Oku-Akasaka Sushi Tanji MCP server require authentication?
No. We connected to Oku-Akasaka Sushi Tanji without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Oku-Akasaka Sushi Tanji MCP server still maintained?
Oku-Akasaka Sushi Tanji is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.