com.tableall/mcp
com.tableall/mcp
Access Japan's finest Michelin-starred restaurants. Search, check availability, and browse menus.
Status
Degraded
Score
77.0
Transport
sse
Tools
11
Production readiness
Verdict
Needs remediation
Current validation evidence shows operational or discovery gaps that should be fixed first.
Critical alerts
0
Production verdicts degrade quickly when critical alerts are active.
Evidence confidence
Confidence score
60.0
Based on 20 recent validations, 26 captured checks, and validation age of 594.2 hours.
Live checks captured
26
More direct checks increase trust in the current verdict.
Validation age
594.2h
Lower age means fresher evidence.
Recommended for
Claude Desktop
Claude Desktop is marked compatible with score 83.
Smithery
Smithery is marked compatible with score 100.
Generic Streamable HTTP
Generic Streamable HTTP is marked compatible with score 100.
Client readiness verdicts
Ready for ChatGPT custom connector
Partial
Requires a streamable HTTP endpoint.; Dynamic client registration materially improves connector setup.; Transport compliance should be in good shape.
Confidence: medium (60.0)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history, server_card
Disagreements: none
initialize• OKtools_list• OKtransport_compliance_probe• Errorstep_up_auth_probe• Warningconnector_replay_probe• OK — Frozen tool snapshots must survive refresh.request_association_probe• Missing — Roots, sampling, and elicitation should stay request-scoped.
Ready for Claude remote MCP
Ready
Transport behavior should match Claude-compatible HTTP expectations.
Confidence: medium (60.0)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history, server_card
Disagreements: none
initialize• OKtools_list• OKtransport_compliance_probe• Error
Unsafe for write actions
No
Current write surface is bounded enough for cautious review.
Confidence: medium (60.0)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history
Disagreements: none
action_safety_probe• Warning
Snapshot churn risk
Low
No material tool-surface churn detected in the latest comparison.
Confidence: medium (60.0)
Evidence provenance
Winner: history
Supporting sources: history, live_validation
Disagreements: none
tool_snapshot_probe• OKconnector_replay_probe• OK
Why not ready by client
ChatGPT custom connector
Partial
Remediation checklist
- No explicit blockers recorded.
Claude remote MCP
Ready
Remediation checklist
- No explicit blockers recorded.
Write-safe publishing
Ready
Remediation checklist
- No explicit blockers recorded.
Verdict traces
Production verdict
Needs remediation
Current validation evidence shows operational or discovery gaps that should be fixed first.
Confidence: medium (60.0)
Winning source: live_validation
Triggering alerts
validation_stale• medium • Validation evidence is staleserver_degraded• medium • Latest validation is degraded
Client verdict trace table
| Verdict | Status | Checks | Winning source | Conflicts |
|---|---|---|---|---|
openai_connectors |
Partial | initialize, tools_list, transport_compliance_probe, step_up_auth_probe, connector_replay_probe, request_association_probe | live_validation | none |
claude_desktop |
Ready | initialize, tools_list, transport_compliance_probe | live_validation | none |
unsafe_for_write_actions |
No | action_safety_probe | live_validation | none |
snapshot_churn_risk |
Low | tool_snapshot_probe, connector_replay_probe | history | none |
Publishability policy profiles
ChatGPT custom connector publishability
Caution
Requires a streamable HTTP endpoint.; Dynamic client registration materially improves connector setup.; Transport compliance should be in good shape.
- Search Fetch Only: No
- Write Actions Present: Yes
- Oauth Configured: Yes
- Admin Refresh Required: No
- Safe For Company Knowledge: No
- Safe For Messages Api Remote Mcp: No
Claude remote MCP publishability
Ready
Transport behavior should match Claude-compatible HTTP expectations.
- Search Fetch Only: No
- Write Actions Present: Yes
- Oauth Configured: Yes
- Admin Refresh Required: No
- Safe For Company Knowledge: No
- Safe For Messages Api Remote Mcp: No
Compatibility fixtures
ChatGPT custom connector fixture
Degraded
Requires a streamable HTTP endpoint.; Dynamic client registration materially improves connector setup.; Transport compliance should be in good shape.
- remote_http_endpoint: Passes
- oauth_discovery: Passes
- frozen_tool_snapshot_refresh: Passes
- request_association: Passes
Anthropic remote MCP fixture
Degraded
Transport behavior should match Claude-compatible HTTP expectations.
- remote_transport: Passes
- tool_discovery: Passes
- auth_connect: Passes
- safe_write_review: Passes
Authenticated validation sessions
Latest profile
remote_mcp
Authenticated session used
Public score isolation
Preview endpoint
/v1/verifyCI preview endpoint
/v1/ci/previewPublic server reputation
Validation success 7d
n/a
Validation success 30d
0.67
Mean time to recover
n/a
Breaking diffs 30d
0
Registry drift frequency 30d
0
Snapshot changes 30d
0
Incident & change feed
| Timestamp | Event | Details |
|---|---|---|
| Apr 09, 2026 08:55:13 AM UTC | Latest validation: degraded | Score 77.0 with status degraded. |
| Apr 09, 2026 08:55:13 AM UTC | Score changed | Score delta -0.5 versus the previous run. |
| Apr 09, 2026 12:54:57 AM UTC | Validation summary changed | Summary moved from healthy to degraded. |
| Apr 09, 2026 12:54:57 AM UTC | Score changed | Score delta +1.6 versus the previous run. |
| Apr 09, 2026 12:54:57 AM UTC | Auth mode changed | Auth mode moved from public to oauth_supported. |
Capabilities
- OAuth:
- DCR/CIMD:
- Prompts:
- Homepage: none
- Docs: none
- Support: none
- Icon: none
- Remote endpoint: https://mcp.tableall.com/sse
- Server card: none
Use-case taxonomy
development search communication productivity
Security posture
Tools analyzed
11
High-risk tools
2
Destructive tools
0
Exec tools
0
Egress tools
0
Secret tools
4
Bulk-access tools
1
Risk distribution
low:4, medium:5, high:2
Tool capability & risk inventory
| Tool | Capabilities | Risk | Findings | Notes |
|---|---|---|---|---|
search_restaurants |
read | Low | none | No explicit safeguard hints detected. |
get_restaurant_details |
read | Low | none | No explicit safeguard hints detected. |
get_restaurant_menu |
read | Low | none | No explicit safeguard hints detected. |
check_availability |
read admin | Medium | none | No explicit safeguard hints detected. |
search_available_restaurants |
read write network admin export | Medium | bulk data access admin mutation | Safeguards hinted in metadata. |
get_restaurant_resource |
read | Low | none | No explicit safeguard hints detected. |
get_cancel_policies |
read write network admin | Medium | admin mutation | Safeguards hinted in metadata. |
create_reservation |
read write network filesystem admin secrets | High | secret material access freeform input surface filesystem mutation admin mutation | Safeguards hinted in metadata. |
get_reservation_status |
read write admin secrets | Medium | secret material access admin mutation | No explicit safeguard hints detected. |
create_reservation_request |
read write network filesystem admin secrets | High | secret material access freeform input surface filesystem mutation admin mutation | Safeguards hinted in metadata. |
get_reservation_request_status |
read write network admin secrets | Medium | secret material access admin mutation | No explicit safeguard hints detected. |
Write-action governance
Governance status
Warning
Safe to publish
Auth boundary
oauth_or_auth_required
Blast radius
High
High-risk tools
2
Confirmation signals
get_cancel_policies, create_reservation, create_reservation_request
Safeguard count
4
Status detail: 2 high-risk tool(s); auth boundary is oauth or auth required with 4 safeguard(s) and 3 confirmation signal(s).
| Tool | Risk | Flags | Safeguards |
|---|---|---|---|
create_reservation |
High | secret material access freeform input surface filesystem mutation admin mutation | yes |
create_reservation_request |
High | secret material access freeform input surface filesystem mutation admin mutation | yes |
Action-controls diff
Snapshot changed
no
Disabled-by-default candidates
none
Manual review candidates
none
New actions
| Action | Risk | Flags |
|---|---|---|
| No newly added actions. | ||
Changed actions
| Action | Change types | Risk |
|---|---|---|
| No materially changed actions. | ||
Why this score?
Access & Protocol
34/44
Connectivity, auth, and transport expectations for common clients.
Interface Quality
38.4/56
How well the tool/resource interface communicates and behaves under automation.
Security Posture
28/36
How safely the exposed tool surface handles destructive actions, egress, execution, secrets, and risky inputs.
Reliability & Trust
23/24
Operational stability, consistency, and trustworthiness over time.
Discovery & Governance
22.5/28
How well the server is documented, listed, and governed in public registries.
Adoption & Market
5/8
Adoption clues and public evidence that the server is intended for external use.
Algorithmic score breakdown
Auth Operability
3/4
Measures whether auth discovery and protected access behave predictably for clients.
Error Contract Quality
3.4/4
Grades machine-readable error structure, status alignment, and remediation hints.
Rate-Limit Semantics
2/4
Checks whether quota/throttle responses are deterministic and automation-friendly.
Schema Completeness
3/4
Completeness of tool descriptions, parameter docs, examples, and schema shape.
Backward Compatibility
4/4
Stability score across tool schema/name drift relative to prior validations.
SLO Health
3/4
Availability, latency, and burst-failure profile across recent validation history.
Security Hygiene
4/4
HTTPS posture, endpoint hygiene, and response-surface hardening checks.
Task Success
4/4
Can an agent reliably initialize, enumerate tools, and execute core MCP flows?
Trust Confidence
4/4
Confidence-adjusted reliability score that penalizes low evidence volume.
Abuse/Noise Resilience
4/4
How well the server preserves core behavior in the presence of noisy traffic patterns.
Prompt Contract
2/4
Quality of prompt metadata, argument shape, and prompt discoverability for clients.
Resource Contract
2/4
How completely resources and resource templates describe URIs, types, and usage shape.
Discovery Metadata
3/4
Homepage, docs, icon, repository, support, and license coverage for directory consumers.
Registry Consistency
2/4
Agreement between stored registry metadata, live server-card data, and current validation output.
Installability
4/4
How cleanly a real client can connect, initialize, enumerate tools, and proceed through auth.
Session Semantics
4/4
Determinism and state behavior across repeated MCP calls, including sticky-session surprises.
Tool Surface Design
3/4
Naming clarity, schema ergonomics, and parameter complexity across the tool surface.
Result Shape Stability
3/4
Stability of declared output schemas across validations, with penalties for drift or missing shapes.
OAuth Interop
3/4
Depth and client compatibility of OAuth/OIDC metadata beyond the minimal protected-resource check.
Recovery Semantics
0/4
Whether failures include actionable machine-readable next steps such as retry or upgrade guidance.
Maintenance Signal
3/4
Versioning, update recency, and historical validation cadence that indicate active stewardship.
Adoption Signal
2/4
Directory presence and distribution clues that suggest the server is intended for external use.
Freshness Confidence
4/4
Confidence that recent validations are current enough and dense enough to trust operationally.
Transport Fidelity
4/4
Whether declared transport metadata matches the observed endpoint behavior and response formats.
Spec Recency
4/4
How close the server’s claimed MCP protocol version is to the latest known public revision.
Session Resume
3/4
Whether Streamable HTTP session identifiers and resumed requests behave cleanly for real clients.
Step-Up Auth
3/4
Whether OAuth metadata and WWW-Authenticate challenges support granular, incremental consent instead of broad upfront scopes.
Transport Compliance
0/4
Checks session headers, protocol-version enforcement, session teardown, and expired-session behavior.
Utility Coverage
2/4
Signals support for completions, pagination, and task-oriented utility surfaces that larger clients increasingly expect.
Advanced Capability Coverage
2/4
Coverage of newer MCP surfaces like roots, sampling, elicitation, structured output, and related metadata.
Connector Publishability
3/4
How ready the server looks for client catalogs and managed connector programs.
Tool Snapshot Churn
4/4
Stability of the tool surface across recent validations, including add/remove and output-shape drift.
Connector Replay
4/4
Whether a previously published frozen connector snapshot would remain backward compatible after the latest tool refresh.
Request Association
3/4
Whether roots, sampling, and elicitation appear tied to active client requests instead of arriving unsolicited on idle sessions.
Interactive Flow Safety
4/4
Whether prompts and docs steer users toward safe auth flows instead of pasting secrets directly.
Action Safety
2/4
Risk-weighted view of destructive, exec, egress, and confirmation semantics across the tool surface.
Official Registry Presence
4/4
Whether the server appears directly or indirectly in the official MCP registry.
Provenance Divergence
4/4
How closely official registry metadata, the live server card, and public repo/package signals agree with each other.
Safety Transparency
4/4
Clarity of docs, auth disclosure, support links, and other trust signals visible to integrators.
Tool Capability Clarity
4/4
How clearly the tool surface communicates whether each action reads, writes, deletes, executes, or exports data.
Destructive Operation Safety
3/4
Penalizes delete/revoke/destroy style tools unless auth and safeguards reduce blast radius.
Egress / SSRF Resilience
3/4
Assesses arbitrary URL fetch, crawl, webhook, and remote-request exposure on the tool surface.
Execution / Sandbox Safety
4/4
Evaluates shell, code, script, and command-execution exposure and whether that surface appears contained.
Data Exfiltration Resilience
3/4
Assesses export, dump, backup, and bulk-read behavior against the surrounding auth and safeguard signals.
Least Privilege Scope
3/4
Rewards scoped auth metadata and penalizes broad or missing scopes around privileged tools.
Secret Handling Hygiene
2/4
Assesses secret-bearing tools, token leakage risk, and whether the public surface avoids obvious secret exposure.
Supply Chain Signal
2.5/4
Public metadata signal for repository, changelog, license, versioning, and recency that supports supply-chain trust.
Input Sanitization Safety
3/4
Penalizes risky freeform string inputs when schemas do not constrain URLs, code, paths, queries, or templates.
Tool Namespace Clarity
4/4
Measures naming uniqueness and ambiguity across the tool namespace to reduce collision and confusion risk.
Compatibility profiles
OpenAI Connectors
66.7
partial
Requires a streamable HTTP endpoint.; Dynamic client registration materially improves connector setup.; Transport compliance should be in good shape.
Connector URL: https://mcp.tableall.com/sse # Complete OAuth in the client when prompted. # Server: com.tableall/mcp
Claude Desktop
83.3
compatible
Transport behavior should match Claude-compatible HTTP expectations.
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": ["mcp-remote", "https://mcp.tableall.com/sse"]
}
}
}
Smithery
100.0
compatible
No major blockers detected.
smithery mcp add "https://mcp.tableall.com/sse"
Generic Streamable HTTP
100.0
compatible
No major blockers detected.
curl -sS https://mcp.tableall.com/sse -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"mcp-verify","version":"0.1.0"}}}'
Actionable remediation
| Severity | Remediation | Why it matters | Recommended action |
|---|---|---|---|
| High | Add confirmation and dry-run semantics for risky actions | High-risk write, delete, exec, or egress tools should communicate safeguards clearly. | Inspect the latest validation evidence and resolve the client-visible regression.Playbook
|
| High | Align session and protocol behavior with Streamable HTTP expectations | Clients increasingly rely on MCP-Protocol-Version, session teardown, and expired-session semantics. | Align MCP-Protocol-Version, MCP-Session-Id, DELETE teardown, and expired-session handling with the transport spec.Playbook
|
| High | Associate roots, sampling, and elicitation with active client requests | Modern MCP guidance expects roots, sampling, and elicitation traffic to be tied to an active client request instead of arriving unsolicited on idle sessions. | Inspect the latest validation evidence and resolve the client-visible regression.Playbook
|
| High | Publish OAuth authorization-server metadata | Clients need authorization-server metadata to discover issuer, endpoints, and DCR support. | Publish /.well-known/oauth-authorization-server from your issuer and include registration_endpoint when supported.Playbook
|
| High | Publish a complete server card | Missing or incomplete server-card metadata weakens discovery, documentation, and trust signals. | Serve /.well-known/mcp/server-card.json and include tools, prompts/resources, homepage, and support links.Playbook
|
| Medium | Adopt a current MCP protocol revision | Older protocol revisions reduce compatibility with newer clients and registry programs. | Inspect the latest validation evidence and resolve the client-visible regression.Playbook
|
| Medium | Close connector-publishing gaps | Connector catalogs care about protocol recency, session behavior, auth clarity, and tool-surface stability. | Inspect the latest validation evidence and resolve the client-visible regression.Playbook
|
| Medium | Document minimal scopes and return cleaner auth challenges | Modern clients expect granular scopes and step-up auth signals such as WWW-Authenticate scope hints. | Return granular scopes and WWW-Authenticate challenge hints instead of forcing overly broad auth upfront.Playbook
|
| Medium | Repair prompts/list or stop advertising prompts | Prompt metadata should either work live or be removed from the advertised capability set. | Only advertise prompts if prompts/list works and prompt arguments are documented.Playbook
|
| Medium | Repair resources/list or stop advertising resources | Resource metadata should either work live or be removed from the advertised capability set. | Only advertise resources if resources/list works and resources expose stable URIs/types.Playbook
|
| Medium | Respond to latest validation is degraded | The server is reachable but at least one important behavior regressed. | Resolve the regressed checks and review the latest validation diff.Playbook
|
| Medium | Respond to validation evidence is stale | Latest validation is 594.2 hours old. | Trigger a fresh validation run or increase scheduler priority for this server.Playbook
|
| Medium | Support resumable HTTP sessions cleanly | Modern MCP clients increasingly expect resumable session behavior on streamable HTTP transports. | Inspect the latest validation evidence and resolve the client-visible regression.Playbook
|
| Low | Expose modern utility surfaces like completions, pagination, or tasks | Utility coverage improves interoperability with larger clients and long-lived agent workflows. | Expose completions, pagination, and task metadata where supported so larger clients can plan and resume work safely.Playbook
|
| Low | Publish newer MCP capability signals | Roots, sampling, elicitation, structured outputs, and related metadata improve client understanding and ranking. | Inspect the latest validation evidence and resolve the client-visible regression.Playbook
|
Point loss breakdown
| Component | Current | Points missing |
|---|---|---|
| Transport Compliance | 0/4 | -4.0 |
| Recovery Semantics | 0/4 | -4.0 |
| Utility Coverage | 2/4 | -2.0 |
| Secret Handling Hygiene | 2/4 | -2.0 |
| Resource Contract | 2/4 | -2.0 |
| Registry Consistency | 2/4 | -2.0 |
| Rate Limit Semantics | 2/4 | -2.0 |
| Prompt Contract | 2/4 | -2.0 |
| Advanced Capability Coverage | 2/4 | -2.0 |
| Adoption Signal | 2/4 | -2.0 |
| Action Safety | 2/4 | -2.0 |
| Dependency Supply Chain Signal | 2.5/4 | -1.5 |
Validation diff
Score delta
-0.51
Summary changed
no
Tool delta
0
Prompt delta
0
Auth mode changed
no
Write surface expanded
no
Protocol regressed
no
Registry drift changed
no
Regressed checks: none
Improved checks: none
| Component | Previous | Latest | Delta |
|---|---|---|---|
secret_handling_hygiene_score | 4.0 | 2.0 | -2.0 |
least_privilege_scope_score | 2.0 | 3.0 | 1.0 |
Tool snapshot diff & changelog
Snapshot changed
no
Added tools
none
Removed tools
none
Required-argument changes
| Tool | Added required args | Removed required args |
|---|---|---|
| No required-argument changes detected. | ||
Output-schema drift
| Tool | Previous properties | Latest properties |
|---|---|---|
| No output-schema drift detected. | ||
Connector replay
Status
OK
Backward compatible
Would break after refresh
Added tools
none
Removed tools
none
Additive output changes
none
Required-argument replay breaks
| Tool | Added required args | Removed required args |
|---|---|---|
| No required-argument replay breaks detected. | ||
Output-schema replay breaks
| Tool | Removed properties | Added properties |
|---|---|---|
| No output-schema replay breaks detected. | ||
Transport compliance drilldown
Probe status
Error
Transport
sse
Session header
no
Protocol header
no
Bad protocol response
200
DELETE teardown
n/a
Expired session retry
n/a
Last-Event-ID visible
no
Issues: missing_session_id, missing_protocol_header, bad_protocol_not_rejected
Request association
Status
Missing
Advertised capabilities
none
Observed idle methods
none
Violating methods
none
Probe HTTP status
n/a
Issues
none
Utility coverage
Probe status
Missing
Completions
not detected
Completion probe target: none
Pagination
not detected
No nextCursor evidence.
Tasks
Missing
Advertised: no
Benchmark tasks
| Benchmark task | Status | Evidence |
|---|---|---|
| Discover tools | Passes |
|
| Read-only fetch flow | Degraded |
|
| OAuth-required connect | Passes |
|
| Safe write flow with confirmation | Degraded |
|
Registry & provenance divergence
Probe status
OK
Direct official match
yes
Drift fields
none
| Field | Registry | Live server card |
|---|---|---|
| Title | n/a | n/a |
| Version | n/a | n/a |
| Homepage | n/a | n/a |
Active alerts
- Validation evidence is stale (medium)
Latest validation is 594.2 hours old. - Latest validation is degraded (medium)
The server is reachable but at least one important behavior regressed.
Aliases & registry graph
| Identifier | Source | Canonical | Score |
|---|---|---|---|
com.tableall/mcp |
official_registry | yes | 76.99 |
Alias consolidation
Canonical identifier
com.tableall/mcp
Duplicate aliases
0
Registry sources
official_registry
Remote URLs
Homepages
none
Source disagreements
| Field | What differs | Observed values |
|---|---|---|
| No source disagreements detected. | ||
Install snippets
Openai Connectors
Connector URL: https://mcp.tableall.com/sse # Complete OAuth in the client when prompted. # Server: com.tableall/mcp
Claude Desktop
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": ["mcp-remote", "https://mcp.tableall.com/sse"]
}
}
}
Smithery
smithery mcp add "https://mcp.tableall.com/sse"
Generic Http
curl -sS https://mcp.tableall.com/sse -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"mcp-verify","version":"0.1.0"}}}'
Agent access & tool surface
Live server tools
search_restaurants get_restaurant_details get_restaurant_menu check_availability search_available_restaurants get_restaurant_resource get_cancel_policies create_reservation
Observed from the latest live validation against https://mcp.tableall.com/sse. This is the target server surface, not Verify's own inspection tools.
Live capability counts
11 tools • 0 prompts • 0 resources
Counts come from the latest
tools/list, prompts/list, and resources/list checks.Inspect with Verify
search_servers recommend_servers get_server_report compare_servers
Use Verify itself to search, recommend, compare, and fetch the full report for
com.tableall/mcp.Direct machine links
Claims & monitoring
Server ownership
No verified maintainer claim recorded.
Watch subscriptions
0
Teams: none
Alert routing
Active watches
0
Generic webhooks
0
Slack routes
0
Teams routes
0
Email routes
0
| Watch | Team | Channels | Minimum severity |
|---|---|---|---|
| No active watch destinations. | |||
Maintainer analytics
Validation Run Count
20
Average Latency Ms
4511.27
Healthy Run Ratio Recent
0.8
Registry Presence Count
1
Active Alert Count
2
Watcher Count
0
Verified Claim
False
Taxonomy Tags
development, search, communication, productivity
Score Trend
76.99, 77.5, 75.93, 75.93, 75.93, 75.93, 75.93, 75.93, 75.42, 75.42
Remediation Count
15
High Risk Tool Count
2
Destructive Tool Count
0
Exec Tool Count
0
Maintainer response quality
Score
16.67
Verified claim
Support contact
Changelog present
Incident notes present
Tool changes documented
Annotation history
Annotation count
0
Maintainer annotations
No maintainer annotations have been recorded yet.
Maintainer rebuttals & expected behavior
No maintainer rebuttals or expected-behavior overrides are recorded yet.
Latest validation evidence
Latest summary
Degraded
Validation profile
remote_mcp
Started
Apr 09, 2026 08:55:08 AM UTC
Latency
4880.3 ms
Failures
oauth_authorization_serverClient error '404 Not Found' for url 'https://mcp.tableall.com/.well-known/oauth-authorization-server' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404server_cardClient error '404 Not Found' for url 'https://mcp.tableall.com/.well-known/mcp/server-card.json' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404transport_compliance_probeIssues: missing session id, missing protocol header, bad protocol not rejected (bad protocol=200).
Checks
| Check | Status | Latency | Evidence |
|---|---|---|---|
action_safety_probe |
Warning | n/a | 2 high-risk tool(s); auth present; safeguards=4; confirmation=get cancel policies, create reservation, create reservation request. |
advanced_capabilities_probe |
Missing | n/a | No advanced MCP capability signals detected. |
connector_publishability_probe |
Warning | n/a | Publishability blockers: transport compliance, server card. |
connector_replay_probe |
OK | n/a | Backward compatible with no breaking tool-surface changes. |
determinism_probe |
OK | 237.0 ms | Check completed |
initialize |
OK | 235.5 ms | Protocol 2024-11-05 |
interactive_flow_probe |
OK | n/a | Check completed |
oauth_authorization_server |
Error | 234.1 ms | Client error '404 Not Found' for url 'https://mcp.tableall.com/.well-known/oauth-authorization-server' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404 |
oauth_protected_resource |
OK | 698.9 ms | 1 authorization server(s) |
official_registry_probe |
OK | n/a | Check completed |
openid_configuration |
OK | 702.0 ms | authorization_endpoint, code_challenge_methods_supported, grant_types_supported, issuer |
probe_noise_resilience |
OK | 235.2 ms | Fetched https://mcp.tableall.com/robots.txt |
prompt_get |
Missing | n/a | not advertised |
prompts_list |
Missing | 235.7 ms | not supported |
protocol_version_probe |
Warning | n/a | Claims 2024-11-05; 3 release(s) behind 2025-11-25. |
provenance_divergence_probe |
OK | n/a | Check completed |
request_association_probe |
Missing | n/a | No request-association capabilities were advertised. |
resource_read |
Missing | n/a | not advertised |
resources_list |
Missing | 236.0 ms | not supported |
server_card |
Error | 778.4 ms | Client error '404 Not Found' for url 'https://mcp.tableall.com/.well-known/mcp/server-card.json' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404 |
session_resume_probe |
Warning | n/a | no session id |
step_up_auth_probe |
Warning | n/a | Scopes=email, openid, profile. |
tool_snapshot_probe |
OK | n/a | Check completed |
tools_list |
OK | 468.3 ms | 11 tool(s) exposed |
transport_compliance_probe |
Error | 236.8 ms | Issues: missing session id, missing protocol header, bad protocol not rejected (bad protocol=200). |
utility_coverage_probe |
Missing | 235.4 ms | No completions evidence; no pagination evidence; tasks missing. |
Raw evidence view
Show raw JSON evidence
{
"checks": {
"action_safety_probe": {
"details": {
"auth_present": true,
"confirmation_signals": [
"get_cancel_policies",
"create_reservation",
"create_reservation_request"
],
"safeguard_count": 4,
"summary": {
"bulk_access_tools": 1,
"capability_distribution": {
"admin": 7,
"export": 1,
"filesystem": 2,
"network": 5,
"read": 11,
"secrets": 4,
"write": 6
},
"destructive_tools": 0,
"egress_tools": 0,
"exec_tools": 0,
"high_risk_tools": 2,
"risk_distribution": {
"critical": 0,
"high": 2,
"low": 4,
"medium": 5
},
"secret_tools": 4,
"tool_count": 11
}
},
"latency_ms": null,
"status": "warning"
},
"advanced_capabilities_probe": {
"details": {
"capabilities": {
"completions": false,
"elicitation": false,
"prompts": false,
"resource_links": false,
"resources": false,
"roots": false,
"sampling": false,
"structured_outputs": false
},
"enabled": [],
"enabled_count": 0,
"initialize_capability_keys": [
"resources",
"tools"
]
},
"latency_ms": null,
"status": "missing"
},
"connector_publishability_probe": {
"details": {
"blockers": [
"transport_compliance",
"server_card"
],
"criteria": {
"action_safety": true,
"auth_flow": true,
"connector_replay": true,
"initialize": true,
"protocol_version": true,
"remote_transport": true,
"request_association": true,
"server_card": false,
"session_resume": true,
"step_up_auth": true,
"tool_surface": true,
"tools_list": true,
"transport_compliance": false
},
"high_risk_tools": 2,
"tool_count": 11,
"transport": "sse"
},
"latency_ms": null,
"status": "warning"
},
"connector_replay_probe": {
"details": {
"added_tools": [],
"additive_output_changes": [],
"backward_compatible": true,
"output_breaks": [],
"removed_tools": [],
"required_arg_breaks": [],
"would_break_after_refresh": false
},
"latency_ms": null,
"status": "ok"
},
"determinism_probe": {
"details": {
"attempts": 2,
"baseline_signature": "e610cb80b431859b8f50b4912232fda909ac9d9c36cb91a0ab6071bc4cb3a621",
"errors": [],
"matches": 2,
"stable_ratio": 1.0,
"successful": 2
},
"latency_ms": 236.99,
"status": "ok"
},
"initialize": {
"details": {
"headers": {
"content-type": "application/json; charset=utf-8"
},
"http_status": 200,
"payload": {
"id": 1,
"jsonrpc": "2.0",
"result": {
"capabilities": {
"resources": {},
"tools": {}
},
"protocolVersion": "2024-11-05",
"serverInfo": {
"description": "TableAll MCP Server - Japan's premier Michelin-starred restaurant reservation service",
"name": "TableAll MCP Server",
"version": "2.0.0"
}
}
},
"url": "https://mcp.tableall.com/sse"
},
"latency_ms": 235.47,
"status": "ok"
},
"interactive_flow_probe": {
"details": {
"oauth_supported": true,
"prompt_available": false,
"risk_hits": [],
"safe_hits": [
"browser"
]
},
"latency_ms": null,
"status": "ok"
},
"oauth_authorization_server": {
"details": {
"error": "Client error '404 Not Found' for url 'https://mcp.tableall.com/.well-known/oauth-authorization-server'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
"url": "https://mcp.tableall.com/.well-known/oauth-authorization-server"
},
"latency_ms": 234.14,
"status": "error"
},
"oauth_protected_resource": {
"details": {
"headers": {
"content-type": "application/json; charset=utf-8"
},
"http_status": 200,
"payload": {
"authorization_servers": [
"https://mcp.tableall.com"
],
"resource": "https://mcp.tableall.com",
"resource_documentation": "https://tableall.com/docs/mcp",
"scopes_supported": [
"openid",
"email",
"profile"
]
},
"url": "https://mcp.tableall.com/.well-known/oauth-protected-resource"
},
"latency_ms": 698.93,
"status": "ok"
},
"official_registry_probe": {
"details": {
"direct_match": true,
"official_peer_count": 1,
"registry_identifier": "com.tableall/mcp",
"registry_source": "official_registry"
},
"latency_ms": null,
"status": "ok"
},
"openid_configuration": {
"details": {
"headers": {
"content-type": "application/json; charset=utf-8"
},
"http_status": 200,
"payload": {
"authorization_endpoint": "https://tableall-production.auth.ap-southeast-1.amazoncognito.com/oauth2/authorize",
"code_challenge_methods_supported": [
"S256"
],
"grant_types_supported": [
"authorization_code"
],
"issuer": "https://cognito-idp.ap-southeast-1.amazonaws.com/ap-southeast-1_CT7wK6kxZ/",
"jwks_uri": "https://cognito-idp.ap-southeast-1.amazonaws.com/ap-southeast-1_CT7wK6kxZ/.well-known/jwks.json",
"registration_endpoint": "https://mcp.tableall.com/oauth/register",
"response_types_supported": [
"code"
],
"scopes_supported": [
"openid",
"email",
"profile"
],
"token_endpoint": "https://tableall-production.auth.ap-southeast-1.amazoncognito.com/oauth2/token",
"token_endpoint_auth_methods_supported": [
"client_secret_post",
"client_secret_basic"
],
"userinfo_endpoint": "https://tableall-production.auth.ap-southeast-1.amazoncognito.com/oauth2/userInfo"
},
"url": "https://mcp.tableall.com/.well-known/openid-configuration"
},
"latency_ms": 701.99,
"status": "ok"
},
"probe_noise_resilience": {
"details": {
"headers": {
"content-type": "text/html; charset=utf-8"
},
"http_status": 404,
"url": "https://mcp.tableall.com/robots.txt"
},
"latency_ms": 235.23,
"status": "ok"
},
"prompt_get": {
"details": {
"reason": "not_advertised"
},
"latency_ms": null,
"status": "missing"
},
"prompts_list": {
"details": {
"headers": {
"content-type": "application/json; charset=utf-8"
},
"http_status": 200,
"payload": {
"error": {
"code": -32601,
"message": "Unknown method: prompts/list"
},
"id": 3,
"jsonrpc": "2.0"
},
"reason": "not_supported",
"url": "https://mcp.tableall.com/sse"
},
"latency_ms": 235.71,
"status": "missing"
},
"protocol_version_probe": {
"details": {
"claimed_version": "2024-11-05",
"lag_days": 385,
"latest_known_version": "2025-11-25",
"releases_behind": 3,
"validator_protocol_version": "2025-03-26"
},
"latency_ms": null,
"status": "warning"
},
"provenance_divergence_probe": {
"details": {
"direct_official_match": true,
"drift_fields": [],
"metadata_document_count": 1,
"registry_homepage": null,
"registry_repository": null,
"registry_title": null,
"registry_version": null,
"server_card_homepage": null,
"server_card_repository": null,
"server_card_title": null,
"server_card_version": null
},
"latency_ms": null,
"status": "ok"
},
"request_association_probe": {
"details": {
"reason": "no_request_association_capabilities_advertised"
},
"latency_ms": null,
"status": "missing"
},
"resource_read": {
"details": {
"reason": "not_advertised"
},
"latency_ms": null,
"status": "missing"
},
"resources_list": {
"details": {
"headers": {
"content-type": "application/json; charset=utf-8"
},
"http_status": 200,
"payload": {
"error": {
"code": -32601,
"message": "Unknown method: resources/list"
},
"id": 5,
"jsonrpc": "2.0"
},
"reason": "not_supported",
"url": "https://mcp.tableall.com/sse"
},
"latency_ms": 235.97,
"status": "missing"
},
"server_card": {
"details": {
"error": "Client error '404 Not Found' for url 'https://mcp.tableall.com/.well-known/mcp/server-card.json'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
"url": "https://mcp.tableall.com/.well-known/mcp/server-card.json"
},
"latency_ms": 778.38,
"status": "error"
},
"session_resume_probe": {
"details": {
"protocol_version": "2024-11-05",
"reason": "no_session_id",
"resume_expected": true,
"transport": "sse"
},
"latency_ms": null,
"status": "warning"
},
"step_up_auth_probe": {
"details": {
"auth_required_checks": [],
"broad_scopes": [],
"challenge_headers": [],
"minimal_scope_documented": false,
"oauth_present": true,
"scope_specificity_ratio": 0.25,
"step_up_signals": [],
"supported_scopes": [
"email",
"openid",
"profile"
]
},
"latency_ms": null,
"status": "warning"
},
"tool_snapshot_probe": {
"details": {
"added": [],
"changed_outputs": [],
"current_tool_count": 11,
"previous_tool_count": 11,
"removed": [],
"similarity": 1.0
},
"latency_ms": null,
"status": "ok"
},
"tools_list": {
"details": {
"headers": {
"content-type": "application/json; charset=utf-8"
},
"http_status": 200,
"payload": {
"id": 2,
"jsonrpc": "2.0",
"result": {
"tools": [
{
"annotations": {
"openWorldHint": false,
"readOnlyHint": true
},
"description": "Searches Japan's most exclusive Michelin-starred restaurants via TableAll, the nation's premier fine dining reservation platform.\n\nReturns restaurant list with basic info including price_range.starting_price (minimum price, includes \u00a58,000 Booking Fee).",
"inputSchema": {
"properties": {
"area": {
"description": "Specific area within prefecture (e.g., \"Ginza\", \"Shibuya\")",
"type": "string"
},
"genre": {
"description": "Cuisine type. Available options: \"Sushi\", \"Kaiseki\", \"Tempura\", \"Wagyu\", \"Italian\", \"French\", \"Chinese\", \"Innovative\", \"Spanish\", \"Yakiniku\", \"Yakitori\", \"Teppanyaki\", \"Unagi\", \"Dessert Dining\", \"Kushiage\", \"Shabushabu Sukiyaki\", \"Izakaya\", \"Ramen\", \"Thai\", \"Soba\", \"Tonkatsu\"",
"enum": [
"Sushi",
"Kaiseki",
"Tempura",
"Wagyu",
"Italian",
"French",
"Chinese",
"Innovative",
"Spanish",
"Yakiniku",
"Yakitori",
"Teppanyaki",
"Unagi",
"Dessert Dining",
"Kushiage",
"Shabushabu Sukiyaki",
"Izakaya",
"Ramen",
"Thai",
"Soba",
"Tonkatsu"
],
"type": "string"
},
"prefecture": {
"description": "Prefecture/region filter. Available values: Tokyo, Kyoto, Osaka, Sapporo, Kanazawa, Komatsu, Toyama, Fukuoka, Nagoya, Ise Shima, Kobe, Niseko, Shizuoka, Nagano, Hiroshima, Shikoku, Niigata",
"enum": [
"Tokyo",
"Kyoto",
"Osaka",
"Sapporo",
"Kanazawa",
"Komatsu",
"Toyama",
"Fukuoka",
"Nagoya",
"Ise Shima",
"Kobe",
"Niseko",
"Shizuoka",
"Nagano",
"Hiroshima",
"Shikoku",
"Niigata"
],
"type": "string"
}
},
"type": "object"
},
"name": "search_restaurants"
},
{
"annotations": {
"openWorldHint": false,
"readOnlyHint": true
},
"description": "Get detailed information about a specific Michelin-starred restaurant from TableAll's curated collection of Japan's finest establishments.\n\nReturns full restaurant details including price_range.starting_price (minimum price, includes \u00a58,000 Booking Fee).",
"inputSchema": {
"properties": {
"restaurant_id": {
"description": "The unique ID of the restaurant",
"type": "number"
}
},
"required": [
"restaurant_id"
],
"type": "object"
},
"name": "get_restaurant_details"
},
{
"annotations": {
"openWorldHint": false,
"readOnlyHint": true
},
"description": "Get exclusive menu items and courses for a specific Michelin-starred restaurant through TableAll's premium reservation service.",
"inputSchema": {
"properties": {
"restaurant_id": {
"description": "The unique ID of the restaurant",
"type": "number"
}
},
"required": [
"restaurant_id"
],
"type": "object"
},
"name": "get_restaurant_menu"
},
{
"annotations": {
"openWorldHint": false,
"readOnlyHint": true
},
"description": "Check real-time availability for Japan's most coveted Michelin-starred restaurants through TableAll's exclusive booking system.\n\nDATE HANDLING - CRITICAL:\nWhen user provides only month/day without year:\n1. Default to the current year\n2. If the resulting date would be in the past, use NEXT year instead\nExample (current date: 2026/1/28):\n- User says \"2/12-2/15\" \u2192 use 2026/2/12-2026/2/15 (future date in current year)\nExample (current date: 2026/3/12):\n- User says \"2/12-2/15\" \u2192 use 2027/2/12-2027/2/15 (past date, so use next year)\nNEVER search for dates in the past.\n\nReturns two types of openings:\n1. Fixed seats (seat_type: \"fixed\"): The opening has a fixed number of seats. You MUST book all seats together - partial booking is not allowed. For example, a 4-seat opening requires exactly 4 guests.\n2. Flexible seats (seat_type: \"flexible\"): You can choose your party size within the specified range (min_num_people to max_num_people).\n\nWhen making a reservation:\n- For fixed seats: party_size must equal the fixed_seats value\n- For flexible seats: party_size must be within min_seats and max_seats range",
"inputSchema": {
"properties": {
"by_menu_item": {
"default": false,
"description": "Group availability by menu items",
"type": "boolean"
},
"daily_or_minutes": {
"default": "minutes",
"description": "Time granularity - \"daily\" for daily view or \"minutes\" for minute-level detail",
"enum": [
"daily",
"minutes"
],
"type": "string"
},
"end_date": {
"description": "End date in YYYY-MM-DD format",
"type": "string"
},
"num_people": {
"description": "Number of people/party size (optional)",
"minimum": 1,
"type": "number"
},
"restaurant_id": {
"description": "Specific restaurant ID (optional)",
"type": "number"
},
"start_date": {
"description": "Start date in YYYY-MM-DD format",
"type": "string"
}
},
"type": "object"
},
"name": "check_availability"
},
{
"annotations": {
"openWorldHint": false,
"readOnlyHint": true
},
"description": "Search for restaurants with availability in a specified date range.\n\nThis is the most efficient way to find available restaurants. Instead of:\n1. Calling search_restaurants to get a list\n2. Calling check_availability for each restaurant individually\n\nYou can use this single tool to get all restaurants with openings in one request.\n\nUse this tool when:\n- User wants to find any available restaurant in a region/area\n- User specifies a date range and wants to see what's available\n- User has flexible restaurant preferences but specific date requirements\n\nDATE HANDLING - CRITICAL:\nWhen user provides only month/day without year:\n1. Default to the current year\n2. If the resulting date would be in the past, use NEXT year instead\nExample (current date: 2026/1/28):\n- User says \"2/12-2/15\" \u2192 use 2026/2/12-2026/2/15 (future date in current year)\nExample (current date: 2026/3/12):\n- User says \"2/12-2/15\" \u2192 use 2027/2/12-2027/2/15 (past date, so use next year)\nNEVER search for dates in the past.\n\nDATE RANGE RULE:\nWhen user specifies a single date (e.g., \"December 20th\"):\n- Automatically search from 2 days before to 3 days after the specified date\n- Inform the user: \"I'll search around your preferred date to show you more options.\"\n- Example: User says \"December 20th\" \u2192 start_date: \"2024-12-18\", end_date: \"2024-12-23\"\n- If user explicitly wants only that specific date (e.g., \"only December 20th\", \"exactly on the 20th\"), respect their request and use that single date for both start_date and end_date.\n\nParameters:\n- start_date, end_date: Required. Date range to search (YYYY-MM-DD)\n- prefecture: Optional. Filter by prefecture. Available values: Tokyo, Kyoto, Osaka, Sapporo, Kanazawa, Komatsu, Toyama, Fukuoka, Nagoya, Ise Shima, Kobe, Niseko, Shizuoka, Nagano, Hiroshima, Shikoku, Niigata\n- area: Optional. Filter by area (e.g., \"Ginza\", \"Shibuya\")\n- genre: Optional. Filter by cuisine type (e.g., \"Sushi\", \"French\")\n- num_people: Optional. Filter by party size\n\nReturns restaurants with their available openings, including:\n- Restaurant basic info (name, cuisine, location, michelin stars, price_range, open_time, closed_days)\n- Available openings with date, time, seat type, and course info\n\nPRICE NOTE:\n- price_range.starting_price shows the minimum price (e.g., \"\u00a539,000\u301c\")\n- All prices include TableAll's \u00a58,000 Booking Fee",
"inputSchema": {
"properties": {
"area": {
"description": "Specific area within prefecture (e.g., \"Ginza\", \"Shibuya\")",
"type": "string"
},
"end_date": {
"description": "End date in YYYY-MM-DD format (required)",
"type": "string"
},
"genre": {
"description": "Cuisine type (e.g., \"Sushi\", \"Kaiseki\", \"French\", \"Italian\")",
"enum": [
"Sushi",
"Kaiseki",
"Tempura",
"Wagyu",
"Italian",
"French",
"Chinese",
"Innovative",
"Spanish",
"Yakiniku",
"Yakitori",
"Teppanyaki",
"Unagi",
"Dessert Dining",
"Kushiage",
"Shabushabu Sukiyaki",
"Izakaya",
"Ramen",
"Thai",
"Soba",
"Tonkatsu"
],
"type": "string"
},
"limit": {
"default": 20,
"description": "Maximum number of restaurants to return (default: 20, max: 100)",
"maximum": 100,
"minimum": 1,
"type": "number"
},
"num_people": {
"description": "Number of guests to filter availability",
"minimum": 1,
"type": "number"
},
"offset": {
"default": 0,
"description": "Number of restaurants to skip for pagination (default: 0)",
"minimum": 0,
"type": "number"
},
"prefecture": {
"description": "Prefecture/region filter. Values not in the allowed list will be ignored.",
"enum": [
"Tokyo",
"Kyoto",
"Osaka",
"Sapporo",
"Kanazawa",
"Komatsu",
"Toyama",
"Fukuoka",
"Nagoya",
"Ise Shima",
"Kobe",
"Niseko",
"Shizuoka",
"Nagano",
"Hiroshima",
"Shikoku",
"Niigata"
],
"type": "string"
},
"start_date": {
"description": "Start date in YYYY-MM-DD format (required)",
"type": "string"
}
},
"required": [
"start_date",
"end_date"
],
"type": "object"
},
"name": "search_available_restaurants"
},
{
"annotations": {
"openWorldHint": false,
"readOnlyHint": true
},
"description": "Get formatted information for a specific Michelin-starred restaurant from TableAll's exclusive collection as a readable resource.",
"inputSchema": {
"properties": {
"restaurant_id": {
"description": "The unique ID of the restaurant",
"type": "string"
}
},
"required": [
"restaurant_id"
],
"type": "object"
},
"name": "get_restaurant_resource"
},
{
"annotations": {
"openWorldHint": false,
"readOnlyHint": true
},
"description": "Get cancel policies for a restaurant before making a reservation.\n\nAlways call this tool before create_reservation or create_reservation_request to inform the user about cancellation terms.\n\nIMPORTANT - For RESERVATION REQUESTS (create_reservation_request):\nBefore showing the cancel policy, you MUST first explain how reservation requests work:\n\"How does it work?\nWe will check the availability based on the information you provide below.\n- If available, we will reserve immediately, charge your credit card, and send you a confirmation email.\n- If not available, we will notify you by email. No charge will be made.\n* You can only cancel a request before we confirm the availability with the restaurants (within 10 minutes ~ 24 hours of the request).\"\n\nThen introduce the cancel policy with:\n\"Once your reservation request is confirmed and a booking is made, the following cancellation policy will apply:\"\n\nCRITICAL - BOOKING FEE NOTICE (MUST ALWAYS DISPLAY):\nWhen displaying cancellation policies to users, you MUST ALWAYS include this notice at the end:\n\"* Note: The booking fee is non-refundable regardless of cancellation timing.\"\nThis notice is MANDATORY and must be shown every time you display cancellation policies, whether for direct reservations or reservation requests. NEVER skip this notice.\n\nReturns:\n- policies: Array of cancel policy tiers (days_before, cancel_fee_percentage)\n- no_show_fee_percentage: Fee for no-show\n- booking_fee_note: MUST be displayed to user - booking fee is non-refundable",
"inputSchema": {
"properties": {
"course_id": {
"description": "Course external ID (optional, for course-specific policies)",
"type": "string"
},
"restaurant_id": {
"description": "Restaurant ID to get cancel policies for",
"type": "number"
}
},
"required": [
"restaurant_id"
],
"type": "object"
},
"name": "get_cancel_policies"
},
{
"annotations": {
"destructiveHint": false,
"idempotentHint": false,
"openWorldHint": false,
"readOnlyHint": false
},
"description": "Create a direct reservation for an available opening.\n\nREQUIRED FLOW - Follow these steps in order:\n\nSTEP 1: CANCEL POLICY - Before collecting user information:\n- Call get_cancel_policies to retrieve the cancellation terms\n- Explain the cancel policy to the user clearly\n- MUST include: \"* Note: The booking fee is non-refundable regardless of cancellation timing.\"\n- Ensure the user understands the cancellation fees before proceeding\n\nSTEP 2: COLLECT EMAIL ONLY - First, ask ONLY for email address:\n\"To proceed with the reservation, please provide your email address.\"\n- Do NOT ask for name, country, or phone yet\n- Wait for the user to provide their email\n\nSTEP 3: CHECK USER & COLLECT ADDITIONAL INFO IF NEEDED:\nAfter receiving the email, call this tool with only the email.\n- If user EXISTS: The API will proceed with the existing user info. No additional info needed.\n- If user DOES NOT EXIST: The API will return an error with code \"USER_NOT_FOUND\".\n In this case, ask the user for additional information:\n \"It looks like you don't have a TableAll account yet. To create one, please provide:\n - Full name (first and last name)\n - Country\n - Phone number\"\n Then call this tool again with all the information.\n When a new account is created, the API will return password_reset_url.\n You MUST display this to the user:\n \"Your TableAll account has been created! Please set your password using this link: [password_reset_url]\n Note: The same link has also been sent to your email address.\"\n\nSTEP 4: CONFIRMATION - After collecting all information, you MUST:\n1. Display a summary of all reservation details to the user:\n - Restaurant name\n - Date and time\n - Number of guests\n - Course name\n - Email address (highlight this for verification)\n - Cancel policy summary\n2. Ask the user to confirm: \"Please verify the information above, especially your email address. Shall I proceed with this reservation?\"\n3. Only call this tool AFTER the user explicitly confirms.\n\nRESERVATION RULES:\n- Use this only when an opening_id is available from check_availability\n- For fixed-seat openings, party_size MUST equal the fixed_seats value\n- For flexible-seat openings, party_size must be within min/max range\n\nThis tool internally:\n1. Verifies or creates user account (verify_or_create)\n2. Creates the reservation\n3. Returns a payment URL for the user to complete\n\nThe user must open the payment_url in their browser to complete the reservation.\nNote: The same payment link has also been sent to the email address provided.\nNote: This payment link is valid for 30 minutes.\n\nCRITICAL - ACCESS TOKEN HANDLING:\nThe create response contains \"data.access_token\". You MUST store this value.\nIt is required when calling get_reservation_status to check the reservation status.\nWithout the access_token, the status API will return 403 Forbidden.\n\nRESPONSE HANDLING - NEW USER CREATED (CRITICAL):\nWhen the response contains \"user.is_new_user\": true, you MUST display this message to the user:\n\"Since this email address was not registered, we have created a new TableAll account for you.\nPlease click the link below to set your password: [password_reset_url]\nNote: This link is valid for 24 hours. The same link has also been sent to your email.\"\nThis message is MANDATORY when is_new_user is true. NEVER skip this message.",
"inputSchema": {
"properties": {
"ai_client": {
"description": "AI client name. You MUST provide your AI model name (e.g., \"Claude\", \"Gemini\", \"GPT\", \"Copilot\").",
"type": "string"
},
"allergies": {
"description": "Allergy information",
"type": "string"
},
"country": {
"description": "Country code ISO 3166-1 alpha-2, e.g., \"JP\", \"US\" (required for new users or users with incomplete profile)",
"type": "string"
},
"coupon_code": {
"description": "Coupon code for discount (optional)",
"type": "string"
},
"course_id": {
"description": "Course external ID (required)",
"type": "string"
},
"dislikes": {
"description": "Food dislikes",
"type": "string"
},
"email": {
"description": "User email address (always required)",
"type": "string"
},
"first_name": {
"description": "User first name / \u540d (required for new users or users with incomplete profile)",
"type": "string"
},
"last_name": {
"description": "User last name / \u59d3 (required for new users or users with incomplete profile)",
"type": "string"
},
"opening_id": {
"description": "Opening external ID from check_availability (required)",
"type": "string"
},
"party_size": {
"description": "Number of guests. Must match fixed_seats for fixed openings, or be within min/max range for flexible openings.",
"minimum": 1,
"type": "number"
},
"phone": {
"description": "Phone number without country code (required for new users or users with incomplete profile)",
"type": "string"
},
"phone_country_code": {
"description": "Phone country code, e.g., \"+81\" (required for new users or users with incomplete profile)",
"type": "string"
},
"preferences": {
"description": "Food preferences",
"type": "string"
},
"special_request": {
"description": "Special requests or notes for the restaurant",
"type": "string"
}
},
"required": [
"email",
"opening_id",
"course_id",
"ai_client"
],
"type": "object"
},
"name": "create_reservation"
},
{
"annotations": {
"openWorldHint": false,
"readOnlyHint": true
},
"description": "Check the status of a reservation by session ID.\n\nRequires the access_token that was returned in the create_reservation response.\nYou MUST have stored the access_token from the create response to use this tool.\nWithout a valid access_token, the API will return 403 Forbidden.\n\nIMPORTANT - PRICE DISPLAY:\nThe \"price\" field already INCLUDES the \"booking_fee\". Do NOT add them together.\nWhen displaying to the user, show: price (total) and booking_fee (included in price, non-refundable).\nExample: \"Total: \u00a530,000 (includes \u00a51,000 non-refundable booking fee)\"",
"inputSchema": {
"properties": {
"access_token": {
"description": "Access token returned from create_reservation response (data.access_token). Required for authorization.",
"type": "string"
},
"session_id": {
"description": "Reservation session ID returned from create_reservation",
"type": "string"
}
},
"required": [
"session_id",
"access_token"
],
"type": "object"
},
"name": "get_reservation_status"
},
{
"annotations": {
"destructiveHint": false,
"idempotentHint": false,
"openWorldHint": false,
"readOnlyHint": false
},
"description": "Create a reservation request when no openings are available.\n\nREQUIRED FLOW - Follow these steps in order:\n\nSTEP 1: EXPLAIN HOW RESERVATION REQUEST WORKS - First, explain to the user:\n\"How does it work?\nWe will check the availability based on the information you provide below.\n- If available, we will reserve immediately, charge your credit card, and send you a confirmation email.\n- If not available, we will notify you by email. No charge will be made.\n* You can only cancel a request before we confirm the availability with the restaurants (within 10 minutes ~ 24 hours of the request).\"\n\nSTEP 2: CANCEL POLICY - After explaining how it works:\n- Call get_cancel_policies to retrieve the cancellation terms\n- Explain: \"Once your reservation request is confirmed and a booking is made, the following cancellation policy will apply:\"\n- Display the cancel policy clearly\n- MUST include: \"* Note: The booking fee is non-refundable regardless of cancellation timing.\"\n- Ensure the user understands these fees apply AFTER the reservation is confirmed\n\nSTEP 3: COLLECT GUEST COUNT - You MUST confirm the number of adults and children:\n- If user only says total number (e.g., \"3 people\"), you MUST ask: \"Will there be any children in your party?\"\n- If children: Ask \"How many adults and how many children?\"\n- If no children: Confirm \"So that will be [X] adults, no children. Is that correct?\"\n- NEVER skip this confirmation step\n\nSTEP 4: COLLECT EMAIL ONLY - First, ask ONLY for email address:\n\"To proceed with the reservation request, please provide your email address.\"\n- Do NOT ask for name, country, or phone yet\n- Wait for the user to provide their email\n\nSTEP 5: CHECK USER & COLLECT ADDITIONAL INFO IF NEEDED:\nAfter receiving the email, call this tool with only the email.\n- If user EXISTS: The API will proceed with the existing user info. No additional info needed.\n- If user DOES NOT EXIST: The API will return an error with code \"USER_NOT_FOUND\".\n In this case, ask the user for additional information:\n \"It looks like you don't have a TableAll account yet. To create one, please provide:\n - Full name (first and last name)\n - Country\n - Phone number\"\n Then call this tool again with all the information.\n When a new account is created, the API will return password_reset_url.\n You MUST display this to the user:\n \"Your TableAll account has been created! Please set your password using this link: [password_reset_url]\n Note: The same link has also been sent to your email address.\"\n\nSTEP 6: CONFIRMATION - After collecting all information, you MUST:\n1. Display a summary of all reservation request details to the user:\n - Restaurant name\n - Preferred date(s) and time range (Japan Time)\n - Number of adults\n - Number of children\n - Course name\n - Email address (highlight this for verification)\n2. Ask the user to confirm: \"Please verify the information above, especially your email address. Shall I proceed with this reservation request?\"\n3. Only call this tool AFTER the user explicitly confirms.\n\nRESERVATION REQUEST RULES:\n- Use this when check_availability returns no results\n- Allows specifying multiple preferred dates\n- Restaurant will review and approve/decline the request\n\nDATE HANDLING - CRITICAL:\n- When user says \"any day in [month]\" (e.g., \"any day in January\"), include ALL days of that month\n- When user says \"any day during [period]\" (e.g., \"any day from Jan 10-20\"), include ALL days in that range\n- When user says \"anytime in [week/period]\", include ALL days in that period\n- Do NOT arbitrarily narrow down dates - include every day the user indicated as acceptable\n- Example: \"Any day in January\" \u2192 include all 31 days (2025-01-01 to 2025-01-31)\n- Example: \"Jan 15-20 any day is fine\" \u2192 include all 6 days (2025-01-15 to 2025-01-20)\n\nThis tool internally:\n1. Verifies or creates user account (verify_or_create)\n2. Creates the reservation request\n3. Returns a payment URL for card registration\n\nThe user must open the payment_url to register their card. Payment is only charged when the restaurant approves the request.\nNote: The same payment link has also been sent to the email address provided.\nNote: This payment link is valid for 30 minutes.\n\nCRITICAL - ACCESS TOKEN HANDLING:\nThe create response contains \"data.access_token\". You MUST store this value.\nIt is required when calling get_reservation_request_status to check the request status.\nWithout the access_token, the status API will return 403 Forbidden.\n\nRESPONSE HANDLING - NEW USER CREATED (CRITICAL):\nWhen the response contains \"user.is_new_user\": true, you MUST display this message to the user:\n\"Since this email address was not registered, we have created a new TableAll account for you.\nPlease click the link below to set your password: [password_reset_url]\nNote: This link is valid for 24 hours. The same link has also been sent to your email.\"\nThis message is MANDATORY when is_new_user is true. NEVER skip this message.",
"inputSchema": {
"properties": {
"ai_client": {
"description": "AI client name. You MUST provide your AI model name (e.g., \"Claude\", \"Gemini\", \"GPT\", \"Copilot\").",
"type": "string"
},
"allergies": {
"description": "Allergy information",
"type": "string"
},
"comment": {
"description": "Additional comments (optional)",
"type": "string"
},
"country": {
"description": "Country code ISO 3166-1 alpha-2, e.g., \"JP\", \"US\" (required for new users or users with incomplete profile)",
"type": "string"
},
"coupon_code": {
"description": "Coupon code for discount (optional)",
"type": "string"
},
"course_id": {
"description": "Course external ID (required)",
"type": "string"
},
"dates": {
"description": "Preferred dates in YYYY-MM-DD format. Can specify multiple dates.",
"items": {
"type": "string"
},
"minItems": 1,
"type": "array"
},
"dislikes": {
"description": "Food dislikes",
"type": "string"
},
"email": {
"description": "User email address (always required)",
"type": "string"
},
"first_name": {
"description": "User first name / \u540d (required for new users or users with incomplete profile)",
"type": "string"
},
"hotel_name": {
"description": "Hotel name (optional)",
"type": "string"
},
"last_name": {
"description": "User last name / \u59d3 (required for new users or users with incomplete profile)",
"type": "string"
},
"num_adults": {
"description": "Number of adults (required). If user only says total number of guests (e.g., \"3 people\"), treat all as adults.",
"minimum": 1,
"type": "number"
},
"num_children": {
"description": "Number of children (required). Default to 0 if user does not specify children count or only provides total guest count.",
"minimum": 0,
"type": "number"
},
"phone": {
"description": "Phone number without country code (required for new users or users with incomplete profile)",
"type": "string"
},
"phone_country_code": {
"description": "Phone country code, e.g., \"+81\" (required for new users or users with incomplete profile)",
"type": "string"
},
"preferences": {
"description": "Food preferences",
"type": "string"
},
"restaurant_id": {
"description": "Restaurant ID (required)",
"type": "number"
},
"special_request": {
"description": "Special requests or notes for the restaurant",
"type": "string"
},
"start_time_from": {
"description": "Preferred start time from, in HH:mm format (e.g., \"18:00\"). Japan Time (JST).",
"type": "string"
},
"start_time_to": {
"description": "Preferred start time to, in HH:mm format (e.g., \"20:00\"). Japan Time (JST).",
"type": "string"
}
},
"required": [
"email",
"restaurant_id",
"course_id",
"num_adults",
"num_children",
"dates",
"start_time_from",
"start_time_to",
"ai_client"
],
"type": "object"
},
"name": "create_reservation_request"
},
{
"annotations": {
"openWorldHint": false,
"readOnlyHint": true
},
"description": "Check the status of a reservation request by session ID.\n\nRequires the access_token that was returned in the create_reservation_request response.\nYou MUST have stored the access_token from the create response to use this tool.\nWithout a valid access_token, the API will return 403 Forbidden.\n\nIMPORTANT - PRICE DISPLAY:\nThe \"price\" field already INCLUDES the \"booking_fee\". Do NOT add them together.\nWhen displaying to the user, show: price (total) and booking_fee (included in price, non-refundable).\nExample: \"Total: \u00a530,000 (includes \u00a51,000 non-refundable booking fee)\"",
"inputSchema": {
"properties": {
"access_token": {
"description": "Access token returned from create_reservation_request response (data.access_token). Required for authorization.",
"type": "string"
},
"session_id": {
"description": "Reservation request session ID returned from create_reservation_request",
"type": "string"
}
},
"required": [
"session_id",
"access_token"
],
"type": "object"
},
"name": "get_reservation_request_status"
}
]
}
},
"url": "https://mcp.tableall.com/sse"
},
"latency_ms": 468.34,
"status": "ok"
},
"transport_compliance_probe": {
"details": {
"bad_protocol_error": null,
"bad_protocol_headers": {
"content-type": "application/json; charset=utf-8"
},
"bad_protocol_payload": {
"id": 410,
"jsonrpc": "2.0",
"result": {
"tools": [
{
"annotations": {
"openWorldHint": false,
"readOnlyHint": true
},
"description": "Searches Japan's most exclusive Michelin-starred restaurants via TableAll, the nation's premier fine dining reservation platform.\n\nReturns restaurant list with basic info including price_range.starting_price (minimum price, includes \u00a58,000 Booking Fee).",
"inputSchema": {
"properties": {
"area": {
"description": "Specific area within prefecture (e.g., \"Ginza\", \"Shibuya\")",
"type": "string"
},
"genre": {
"description": "Cuisine type. Available options: \"Sushi\", \"Kaiseki\", \"Tempura\", \"Wagyu\", \"Italian\", \"French\", \"Chinese\", \"Innovative\", \"Spanish\", \"Yakiniku\", \"Yakitori\", \"Teppanyaki\", \"Unagi\", \"Dessert Dining\", \"Kushiage\", \"Shabushabu Sukiyaki\", \"Izakaya\", \"Ramen\", \"Thai\", \"Soba\", \"Tonkatsu\"",
"enum": [
"Sushi",
"Kaiseki",
"Tempura",
"Wagyu",
"Italian",
"French",
"Chinese",
"Innovative",
"Spanish",
"Yakiniku",
"Yakitori",
"Teppanyaki",
"Unagi",
"Dessert Dining",
"Kushiage",
"Shabushabu Sukiyaki",
"Izakaya",
"Ramen",
"Thai",
"Soba",
"Tonkatsu"
],
"type": "string"
},
"prefecture": {
"description": "Prefecture/region filter. Available values: Tokyo, Kyoto, Osaka, Sapporo, Kanazawa, Komatsu, Toyama, Fukuoka, Nagoya, Ise Shima, Kobe, Niseko, Shizuoka, Nagano, Hiroshima, Shikoku, Niigata",
"enum": [
"Tokyo",
"Kyoto",
"Osaka",
"Sapporo",
"Kanazawa",
"Komatsu",
"Toyama",
"Fukuoka",
"Nagoya",
"Ise Shima",
"Kobe",
"Niseko",
"Shizuoka",
"Nagano",
"Hiroshima",
"Shikoku",
"Niigata"
],
"type": "string"
}
},
"type": "object"
},
"name": "search_restaurants"
},
{
"annotations": {
"openWorldHint": false,
"readOnlyHint": true
},
"description": "Get detailed information about a specific Michelin-starred restaurant from TableAll's curated collection of Japan's finest establishments.\n\nReturns full restaurant details including price_range.starting_price (minimum price, includes \u00a58,000 Booking Fee).",
"inputSchema": {
"properties": {
"restaurant_id": {
"description": "The unique ID of the restaurant",
"type": "number"
}
},
"required": [
"restaurant_id"
],
"type": "object"
},
"name": "get_restaurant_details"
},
{
"annotations": {
"openWorldHint": false,
"readOnlyHint": true
},
"description": "Get exclusive menu items and courses for a specific Michelin-starred restaurant through TableAll's premium reservation service.",
"inputSchema": {
"properties": {
"restaurant_id": {
"description": "The unique ID of the restaurant",
"type": "number"
}
},
"required": [
"restaurant_id"
],
"type": "object"
},
"name": "get_restaurant_menu"
},
{
"annotations": {
"openWorldHint": false,
"readOnlyHint": true
},
"description": "Check real-time availability for Japan's most coveted Michelin-starred restaurants through TableAll's exclusive booking system.\n\nDATE HANDLING - CRITICAL:\nWhen user provides only month/day without year:\n1. Default to the current year\n2. If the resulting date would be in the past, use NEXT year instead\nExample (current date: 2026/1/28):\n- User says \"2/12-2/15\" \u2192 use 2026/2/12-2026/2/15 (future date in current year)\nExample (current date: 2026/3/12):\n- User says \"2/12-2/15\" \u2192 use 2027/2/12-2027/2/15 (past date, so use next year)\nNEVER search for dates in the past.\n\nReturns two types of openings:\n1. Fixed seats (seat_type: \"fixed\"): The opening has a fixed number of seats. You MUST book all seats together - partial booking is not allowed. For example, a 4-seat opening requires exactly 4 guests.\n2. Flexible seats (seat_type: \"flexible\"): You can choose your party size within the specified range (min_num_people to max_num_people).\n\nWhen making a reservation:\n- For fixed seats: party_size must equal the fixed_seats value\n- For flexible seats: party_size must be within min_seats and max_seats range",
"inputSchema": {
"properties": {
"by_menu_item": {
"default": false,
"description": "Group availability by menu items",
"type": "boolean"
},
"daily_or_minutes": {
"default": "minutes",
"description": "Time granularity - \"daily\" for daily view or \"minutes\" for minute-level detail",
"enum": [
"daily",
"minutes"
],
"type": "string"
},
"end_date": {
"description": "End date in YYYY-MM-DD format",
"type": "string"
},
"num_people": {
"description": "Number of people/party size (optional)",
"minimum": 1,
"type": "number"
},
"restaurant_id": {
"description": "Specific restaurant ID (optional)",
"type": "number"
},
"start_date": {
"description": "Start date in YYYY-MM-DD format",
"type": "string"
}
},
"type": "object"
},
"name": "check_availability"
},
{
"annotations": {
"openWorldHint": false,
"readOnlyHint": true
},
"description": "Search for restaurants with availability in a specified date range.\n\nThis is the most efficient way to find available restaurants. Instead of:\n1. Calling search_restaurants to get a list\n2. Calling check_availability for each restaurant individually\n\nYou can use this single tool to get all restaurants with openings in one request.\n\nUse this tool when:\n- User wants to find any available restaurant in a region/area\n- User specifies a date range and wants to see what's available\n- User has flexible restaurant preferences but specific date requirements\n\nDATE HANDLING - CRITICAL:\nWhen user provides only month/day without year:\n1. Default to the current year\n2. If the resulting date would be in the past, use NEXT year instead\nExample (current date: 2026/1/28):\n- User says \"2/12-2/15\" \u2192 use 2026/2/12-2026/2/15 (future date in current year)\nExample (current date: 2026/3/12):\n- User says \"2/12-2/15\" \u2192 use 2027/2/12-2027/2/15 (past date, so use next year)\nNEVER search for dates in the past.\n\nDATE RANGE RULE:\nWhen user specifies a single date (e.g., \"December 20th\"):\n- Automatically search from 2 days before to 3 days after the specified date\n- Inform the user: \"I'll search around your preferred date to show you more options.\"\n- Example: User says \"December 20th\" \u2192 start_date: \"2024-12-18\", end_date: \"2024-12-23\"\n- If user explicitly wants only that specific date (e.g., \"only December 20th\", \"exactly on the 20th\"), respect their request and use that single date for both start_date and end_date.\n\nParameters:\n- start_date, end_date: Required. Date range to search (YYYY-MM-DD)\n- prefecture: Optional. Filter by prefecture. Available values: Tokyo, Kyoto, Osaka, Sapporo, Kanazawa, Komatsu, Toyama, Fukuoka, Nagoya, Ise Shima, Kobe, Niseko, Shizuoka, Nagano, Hiroshima, Shikoku, Niigata\n- area: Optional. Filter by area (e.g., \"Ginza\", \"Shibuya\")\n- genre: Optional. Filter by cuisine type (e.g., \"Sushi\", \"French\")\n- num_people: Optional. Filter by party size\n\nReturns restaurants with their available openings, including:\n- Restaurant basic info (name, cuisine, location, michelin stars, price_range, open_time, closed_days)\n- Available openings with date, time, seat type, and course info\n\nPRICE NOTE:\n- price_range.starting_price shows the minimum price (e.g., \"\u00a539,000\u301c\")\n- All prices include TableAll's \u00a58,000 Booking Fee",
"inputSchema": {
"properties": {
"area": {
"description": "Specific area within prefecture (e.g., \"Ginza\", \"Shibuya\")",
"type": "string"
},
"end_date": {
"description": "End date in YYYY-MM-DD format (required)",
"type": "string"
},
"genre": {
"description": "Cuisine type (e.g., \"Sushi\", \"Kaiseki\", \"French\", \"Italian\")",
"enum": [
"Sushi",
"Kaiseki",
"Tempura",
"Wagyu",
"Italian",
"French",
"Chinese",
"Innovative",
"Spanish",
"Yakiniku",
"Yakitori",
"Teppanyaki",
"Unagi",
"Dessert Dining",
"Kushiage",
"Shabushabu Sukiyaki",
"Izakaya",
"Ramen",
"Thai",
"Soba",
"Tonkatsu"
],
"type": "string"
},
"limit": {
"default": 20,
"description": "Maximum number of restaurants to return (default: 20, max: 100)",
"maximum": 100,
"minimum": 1,
"type": "number"
},
"num_people": {
"description": "Number of guests to filter availability",
"minimum": 1,
"type": "number"
},
"offset": {
"default": 0,
"description": "Number of restaurants to skip for pagination (default: 0)",
"minimum": 0,
"type": "number"
},
"prefecture": {
"description": "Prefecture/region filter. Values not in the allowed list will be ignored.",
"enum": [
"Tokyo",
"Kyoto",
"Osaka",
"Sapporo",
"Kanazawa",
"Komatsu",
"Toyama",
"Fukuoka",
"Nagoya",
"Ise Shima",
"Kobe",
"Niseko",
"Shizuoka",
"Nagano",
"Hiroshima",
"Shikoku",
"Niigata"
],
"type": "string"
},
"start_date": {
"description": "Start date in YYYY-MM-DD format (required)",
"type": "string"
}
},
"required": [
"start_date",
"end_date"
],
"type": "object"
},
"name": "search_available_restaurants"
},
{
"annotations": {
"openWorldHint": false,
"readOnlyHint": true
},
"description": "Get formatted information for a specific Michelin-starred restaurant from TableAll's exclusive collection as a readable resource.",
"inputSchema": {
"properties": {
"restaurant_id": {
"description": "The unique ID of the restaurant",
"type": "string"
}
},
"required": [
"restaurant_id"
],
"type": "object"
},
"name": "get_restaurant_resource"
},
{
"annotations": {
"openWorldHint": false,
"readOnlyHint": true
},
"description": "Get cancel policies for a restaurant before making a reservation.\n\nAlways call this tool before create_reservation or create_reservation_request to inform the user about cancellation terms.\n\nIMPORTANT - For RESERVATION REQUESTS (create_reservation_request):\nBefore showing the cancel policy, you MUST first explain how reservation requests work:\n\"How does it work?\nWe will check the availability based on the information you provide below.\n- If available, we will reserve immediately, charge your credit card, and send you a confirmation email.\n- If not available, we will notify you by email. No charge will be made.\n* You can only cancel a request before we confirm the availability with the restaurants (within 10 minutes ~ 24 hours of the request).\"\n\nThen introduce the cancel policy with:\n\"Once your reservation request is confirmed and a booking is made, the following cancellation policy will apply:\"\n\nCRITICAL - BOOKING FEE NOTICE (MUST ALWAYS DISPLAY):\nWhen displaying cancellation policies to users, you MUST ALWAYS include this notice at the end:\n\"* Note: The booking fee is non-refundable regardless of cancellation timing.\"\nThis notice is MANDATORY and must be shown every time you display cancellation policies, whether for direct reservations or reservation requests. NEVER skip this notice.\n\nReturns:\n- policies: Array of cancel policy tiers (days_before, cancel_fee_percentage)\n- no_show_fee_percentage: Fee for no-show\n- booking_fee_note: MUST be displayed to user - booking fee is non-refundable",
"inputSchema": {
"properties": {
"course_id": {
"description": "Course external ID (optional, for course-specific policies)",
"type": "string"
},
"restaurant_id": {
"description": "Restaurant ID to get cancel policies for",
"type": "number"
}
},
"required": [
"restaurant_id"
],
"type": "object"
},
"name": "get_cancel_policies"
},
{
"annotations": {
"destructiveHint": false,
"idempotentHint": false,
"openWorldHint": false,
"readOnlyHint": false
},
"description": "Create a direct reservation for an available opening.\n\nREQUIRED FLOW - Follow these steps in order:\n\nSTEP 1: CANCEL POLICY - Before collecting user information:\n- Call get_cancel_policies to retrieve the cancellation terms\n- Explain the cancel policy to the user clearly\n- MUST include: \"* Note: The booking fee is non-refundable regardless of cancellation timing.\"\n- Ensure the user understands the cancellation fees before proceeding\n\nSTEP 2: COLLECT EMAIL ONLY - First, ask ONLY for email address:\n\"To proceed with the reservation, please provide your email address.\"\n- Do NOT ask for name, country, or phone yet\n- Wait for the user to provide their email\n\nSTEP 3: CHECK USER & COLLECT ADDITIONAL INFO IF NEEDED:\nAfter receiving the email, call this tool with only the email.\n- If user EXISTS: The API will proceed with the existing user info. No additional info needed.\n- If user DOES NOT EXIST: The API will return an error with code \"USER_NOT_FOUND\".\n In this case, ask the user for additional information:\n \"It looks like you don't have a TableAll account yet. To create one, please provide:\n - Full name (first and last name)\n - Country\n - Phone number\"\n Then call this tool again with all the information.\n When a new account is created, the API will return password_reset_url.\n You MUST display this to the user:\n \"Your TableAll account has been created! Please set your password using this link: [password_reset_url]\n Note: The same link has also been sent to your email address.\"\n\nSTEP 4: CONFIRMATION - After collecting all information, you MUST:\n1. Display a summary of all reservation details to the user:\n - Restaurant name\n - Date and time\n - Number of guests\n - Course name\n - Email address (highlight this for verification)\n - Cancel policy summary\n2. Ask the user to confirm: \"Please verify the information above, especially your email address. Shall I proceed with this reservation?\"\n3. Only call this tool AFTER the user explicitly confirms.\n\nRESERVATION RULES:\n- Use this only when an opening_id is available from check_availability\n- For fixed-seat openings, party_size MUST equal the fixed_seats value\n- For flexible-seat openings, party_size must be within min/max range\n\nThis tool internally:\n1. Verifies or creates user account (verify_or_create)\n2. Creates the reservation\n3. Returns a payment URL for the user to complete\n\nThe user must open the payment_url in their browser to complete the reservation.\nNote: The same payment link has also been sent to the email address provided.\nNote: This payment link is valid for 30 minutes.\n\nCRITICAL - ACCESS TOKEN HANDLING:\nThe create response contains \"data.access_token\". You MUST store this value.\nIt is required when calling get_reservation_status to check the reservation status.\nWithout the access_token, the status API will return 403 Forbidden.\n\nRESPONSE HANDLING - NEW USER CREATED (CRITICAL):\nWhen the response contains \"user.is_new_user\": true, you MUST display this message to the user:\n\"Since this email address was not registered, we have created a new TableAll account for you.\nPlease click the link below to set your password: [password_reset_url]\nNote: This link is valid for 24 hours. The same link has also been sent to your email.\"\nThis message is MANDATORY when is_new_user is true. NEVER skip this message.",
"inputSchema": {
"properties": {
"ai_client": {
"description": "AI client name. You MUST provide your AI model name (e.g., \"Claude\", \"Gemini\", \"GPT\", \"Copilot\").",
"type": "string"
},
"allergies": {
"description": "Allergy information",
"type": "string"
},
"country": {
"description": "Country code ISO 3166-1 alpha-2, e.g., \"JP\", \"US\" (required for new users or users with incomplete profile)",
"type": "string"
},
"coupon_code": {
"description": "Coupon code for discount (optional)",
"type": "string"
},
"course_id": {
"description": "Course external ID (required)",
"type": "string"
},
"dislikes": {
"description": "Food dislikes",
"type": "string"
},
"email": {
"description": "User email address (always required)",
"type": "string"
},
"first_name": {
"description": "User first name / \u540d (required for new users or users with incomplete profile)",
"type": "string"
},
"last_name": {
"description": "User last name / \u59d3 (required for new users or users with incomplete profile)",
"type": "string"
},
"opening_id": {
"description": "Opening external ID from check_availability (required)",
"type": "string"
},
"party_size": {
"description": "Number of guests. Must match fixed_seats for fixed openings, or be within min/max range for flexible openings.",
"minimum": 1,
"type": "number"
},
"phone": {
"description": "Phone number without country code (required for new users or users with incomplete profile)",
"type": "string"
},
"phone_country_code": {
"description": "Phone country code, e.g., \"+81\" (required for new users or users with incomplete profile)",
"type": "string"
},
"preferences": {
"description": "Food preferences",
"type": "string"
},
"special_request": {
"description": "Special requests or notes for the restaurant",
"type": "string"
}
},
"required": [
"email",
"opening_id",
"course_id",
"ai_client"
],
"type": "object"
},
"name": "create_reservation"
},
{
"annotations": {
"openWorldHint": false,
"readOnlyHint": true
},
"description": "Check the status of a reservation by session ID.\n\nRequires the access_token that was returned in the create_reservation response.\nYou MUST have stored the access_token from the create response to use this tool.\nWithout a valid access_token, the API will return 403 Forbidden.\n\nIMPORTANT - PRICE DISPLAY:\nThe \"price\" field already INCLUDES the \"booking_fee\". Do NOT add them together.\nWhen displaying to the user, show: price (total) and booking_fee (included in price, non-refundable).\nExample: \"Total: \u00a530,000 (includes \u00a51,000 non-refundable booking fee)\"",
"inputSchema": {
"properties": {
"access_token": {
"description": "Access token returned from create_reservation response (data.access_token). Required for authorization.",
"type": "string"
},
"session_id": {
"description": "Reservation session ID returned from create_reservation",
"type": "string"
}
},
"required": [
"session_id",
"access_token"
],
"type": "object"
},
"name": "get_reservation_status"
},
{
"annotations": {
"destructiveHint": false,
"idempotentHint": false,
"openWorldHint": false,
"readOnlyHint": false
},
"description": "Create a reservation request when no openings are available.\n\nREQUIRED FLOW - Follow these steps in order:\n\nSTEP 1: EXPLAIN HOW RESERVATION REQUEST WORKS - First, explain to the user:\n\"How does it work?\nWe will check the availability based on the information you provide below.\n- If available, we will reserve immediately, charge your credit card, and send you a confirmation email.\n- If not available, we will notify you by email. No charge will be made.\n* You can only cancel a request before we confirm the availability with the restaurants (within 10 minutes ~ 24 hours of the request).\"\n\nSTEP 2: CANCEL POLICY - After explaining how it works:\n- Call get_cancel_policies to retrieve the cancellation terms\n- Explain: \"Once your reservation request is confirmed and a booking is made, the following cancellation policy will apply:\"\n- Display the cancel policy clearly\n- MUST include: \"* Note: The booking fee is non-refundable regardless of cancellation timing.\"\n- Ensure the user understands these fees apply AFTER the reservation is confirmed\n\nSTEP 3: COLLECT GUEST COUNT - You MUST confirm the number of adults and children:\n- If user only says total number (e.g., \"3 people\"), you MUST ask: \"Will there be any children in your party?\"\n- If children: Ask \"How many adults and how many children?\"\n- If no children: Confirm \"So that will be [X] adults, no children. Is that correct?\"\n- NEVER skip this confirmation step\n\nSTEP 4: COLLECT EMAIL ONLY - First, ask ONLY for email address:\n\"To proceed with the reservation request, please provide your email address.\"\n- Do NOT ask for name, country, or phone yet\n- Wait for the user to provide their email\n\nSTEP 5: CHECK USER & COLLECT ADDITIONAL INFO IF NEEDED:\nAfter receiving the email, call this tool with only the email.\n- If user EXISTS: The API will proceed with the existing user info. No additional info needed.\n- If user DOES NOT EXIST: The API will return an error with code \"USER_NOT_FOUND\".\n In this case, ask the user for additional information:\n \"It looks like you don't have a TableAll account yet. To create one, please provide:\n - Full name (first and last name)\n - Country\n - Phone number\"\n Then call this tool again with all the information.\n When a new account is created, the API will return password_reset_url.\n You MUST display this to the user:\n \"Your TableAll account has been created! Please set your password using this link: [password_reset_url]\n Note: The same link has also been sent to your email address.\"\n\nSTEP 6: CONFIRMATION - After collecting all information, you MUST:\n1. Display a summary of all reservation request details to the user:\n - Restaurant name\n - Preferred date(s) and time range (Japan Time)\n - Number of adults\n - Number of children\n - Course name\n - Email address (highlight this for verification)\n2. Ask the user to confirm: \"Please verify the information above, especially your email address. Shall I proceed with this reservation request?\"\n3. Only call this tool AFTER the user explicitly confirms.\n\nRESERVATION REQUEST RULES:\n- Use this when check_availability returns no results\n- Allows specifying multiple preferred dates\n- Restaurant will review and approve/decline the request\n\nDATE HANDLING - CRITICAL:\n- When user says \"any day in [month]\" (e.g., \"any day in January\"), include ALL days of that month\n- When user says \"any day during [period]\" (e.g., \"any day from Jan 10-20\"), include ALL days in that range\n- When user says \"anytime in [week/period]\", include ALL days in that period\n- Do NOT arbitrarily narrow down dates - include every day the user indicated as acceptable\n- Example: \"Any day in January\" \u2192 include all 31 days (2025-01-01 to 2025-01-31)\n- Example: \"Jan 15-20 any day is fine\" \u2192 include all 6 days (2025-01-15 to 2025-01-20)\n\nThis tool internally:\n1. Verifies or creates user account (verify_or_create)\n2. Creates the reservation request\n3. Returns a payment URL for card registration\n\nThe user must open the payment_url to register their card. Payment is only charged when the restaurant approves the request.\nNote: The same payment link has also been sent to the email address provided.\nNote: This payment link is valid for 30 minutes.\n\nCRITICAL - ACCESS TOKEN HANDLING:\nThe create response contains \"data.access_token\". You MUST store this value.\nIt is required when calling get_reservation_request_status to check the request status.\nWithout the access_token, the status API will return 403 Forbidden.\n\nRESPONSE HANDLING - NEW USER CREATED (CRITICAL):\nWhen the response contains \"user.is_new_user\": true, you MUST display this message to the user:\n\"Since this email address was not registered, we have created a new TableAll account for you.\nPlease click the link below to set your password: [password_reset_url]\nNote: This link is valid for 24 hours. The same link has also been sent to your email.\"\nThis message is MANDATORY when is_new_user is true. NEVER skip this message.",
"inputSchema": {
"properties": {
"ai_client": {
"description": "AI client name. You MUST provide your AI model name (e.g., \"Claude\", \"Gemini\", \"GPT\", \"Copilot\").",
"type": "string"
},
"allergies": {
"description": "Allergy information",
"type": "string"
},
"comment": {
"description": "Additional comments (optional)",
"type": "string"
},
"country": {
"description": "Country code ISO 3166-1 alpha-2, e.g., \"JP\", \"US\" (required for new users or users with incomplete profile)",
"type": "string"
},
"coupon_code": {
"description": "Coupon code for discount (optional)",
"type": "string"
},
"course_id": {
"description": "Course external ID (required)",
"type": "string"
},
"dates": {
"description": "Preferred dates in YYYY-MM-DD format. Can specify multiple dates.",
"items": {
"type": "string"
},
"minItems": 1,
"type": "array"
},
"dislikes": {
"description": "Food dislikes",
"type": "string"
},
"email": {
"description": "User email address (always required)",
"type": "string"
},
"first_name": {
"description": "User first name / \u540d (required for new users or users with incomplete profile)",
"type": "string"
},
"hotel_name": {
"description": "Hotel name (optional)",
"type": "string"
},
"last_name": {
"description": "User last name / \u59d3 (required for new users or users with incomplete profile)",
"type": "string"
},
"num_adults": {
"description": "Number of adults (required). If user only says total number of guests (e.g., \"3 people\"), treat all as adults.",
"minimum": 1,
"type": "number"
},
"num_children": {
"description": "Number of children (required). Default to 0 if user does not specify children count or only provides total guest count.",
"minimum": 0,
"type": "number"
},
"phone": {
"description": "Phone number without country code (required for new users or users with incomplete profile)",
"type": "string"
},
"phone_country_code": {
"description": "Phone country code, e.g., \"+81\" (required for new users or users with incomplete profile)",
"type": "string"
},
"preferences": {
"description": "Food preferences",
"type": "string"
},
"restaurant_id": {
"description": "Restaurant ID (required)",
"type": "number"
},
"special_request": {
"description": "Special requests or notes for the restaurant",
"type": "string"
},
"start_time_from": {
"description": "Preferred start time from, in HH:mm format (e.g., \"18:00\"). Japan Time (JST).",
"type": "string"
},
"start_time_to": {
"description": "Preferred start time to, in HH:mm format (e.g., \"20:00\"). Japan Time (JST).",
"type": "string"
}
},
"required": [
"email",
"restaurant_id",
"course_id",
"num_adults",
"num_children",
"dates",
"start_time_from",
"start_time_to",
"ai_client"
],
"type": "object"
},
"name": "create_reservation_request"
},
{
"annotations": {
"openWorldHint": false,
"readOnlyHint": true
},
"description": "Check the status of a reservation request by session ID.\n\nRequires the access_token that was returned in the create_reservation_request response.\nYou MUST have stored the access_token from the create response to use this tool.\nWithout a valid access_token, the API will return 403 Forbidden.\n\nIMPORTANT - PRICE DISPLAY:\nThe \"price\" field already INCLUDES the \"booking_fee\". Do NOT add them together.\nWhen displaying to the user, show: price (total) and booking_fee (included in price, non-refundable).\nExample: \"Total: \u00a530,000 (includes \u00a51,000 non-refundable booking fee)\"",
"inputSchema": {
"properties": {
"access_token": {
"description": "Access token returned from create_reservation_request response (data.access_token). Required for authorization.",
"type": "string"
},
"session_id": {
"description": "Reservation request session ID returned from create_reservation_request",
"type": "string"
}
},
"required": [
"session_id",
"access_token"
],
"type": "object"
},
"name": "get_reservation_request_status"
}
]
}
},
"bad_protocol_status_code": 200,
"delete_error": null,
"delete_status_code": null,
"expired_session_error": null,
"expired_session_status_code": null,
"issues": [
"missing_session_id",
"missing_protocol_header",
"bad_protocol_not_rejected"
],
"last_event_id_visible": false,
"protocol_header_present": false,
"requested_protocol_version": "2024-11-05",
"session_id_present": false,
"transport": "sse"
},
"latency_ms": 236.76,
"status": "error"
},
"utility_coverage_probe": {
"details": {
"completions": {
"advertised": false,
"live_probe": "not_executed",
"sample_target": null
},
"initialize_capability_keys": [
"resources",
"tools"
],
"pagination": {
"metadata_signal": false,
"next_cursor_methods": [],
"supported": false
},
"tasks": {
"advertised": false,
"http_status": 200,
"probe_status": "missing"
}
},
"latency_ms": 235.37,
"status": "missing"
}
},
"failures": {
"oauth_authorization_server": {
"error": "Client error '404 Not Found' for url 'https://mcp.tableall.com/.well-known/oauth-authorization-server'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
"url": "https://mcp.tableall.com/.well-known/oauth-authorization-server"
},
"server_card": {
"error": "Client error '404 Not Found' for url 'https://mcp.tableall.com/.well-known/mcp/server-card.json'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
"url": "https://mcp.tableall.com/.well-known/mcp/server-card.json"
},
"transport_compliance_probe": {
"bad_protocol_error": null,
"bad_protocol_headers": {
"content-type": "application/json; charset=utf-8"
},
"bad_protocol_payload": {
"id": 410,
"jsonrpc": "2.0",
"result": {
"tools": [
{
"annotations": {
"openWorldHint": false,
"readOnlyHint": true
},
"description": "Searches Japan's most exclusive Michelin-starred restaurants via TableAll, the nation's premier fine dining reservation platform.\n\nReturns restaurant list with basic info including price_range.starting_price (minimum price, includes \u00a58,000 Booking Fee).",
"inputSchema": {
"properties": {
"area": {
"description": "Specific area within prefecture (e.g., \"Ginza\", \"Shibuya\")",
"type": "string"
},
"genre": {
"description": "Cuisine type. Available options: \"Sushi\", \"Kaiseki\", \"Tempura\", \"Wagyu\", \"Italian\", \"French\", \"Chinese\", \"Innovative\", \"Spanish\", \"Yakiniku\", \"Yakitori\", \"Teppanyaki\", \"Unagi\", \"Dessert Dining\", \"Kushiage\", \"Shabushabu Sukiyaki\", \"Izakaya\", \"Ramen\", \"Thai\", \"Soba\", \"Tonkatsu\"",
"enum": [
"Sushi",
"Kaiseki",
"Tempura",
"Wagyu",
"Italian",
"French",
"Chinese",
"Innovative",
"Spanish",
"Yakiniku",
"Yakitori",
"Teppanyaki",
"Unagi",
"Dessert Dining",
"Kushiage",
"Shabushabu Sukiyaki",
"Izakaya",
"Ramen",
"Thai",
"Soba",
"Tonkatsu"
],
"type": "string"
},
"prefecture": {
"description": "Prefecture/region filter. Available values: Tokyo, Kyoto, Osaka, Sapporo, Kanazawa, Komatsu, Toyama, Fukuoka, Nagoya, Ise Shima, Kobe, Niseko, Shizuoka, Nagano, Hiroshima, Shikoku, Niigata",
"enum": [
"Tokyo",
"Kyoto",
"Osaka",
"Sapporo",
"Kanazawa",
"Komatsu",
"Toyama",
"Fukuoka",
"Nagoya",
"Ise Shima",
"Kobe",
"Niseko",
"Shizuoka",
"Nagano",
"Hiroshima",
"Shikoku",
"Niigata"
],
"type": "string"
}
},
"type": "object"
},
"name": "search_restaurants"
},
{
"annotations": {
"openWorldHint": false,
"readOnlyHint": true
},
"description": "Get detailed information about a specific Michelin-starred restaurant from TableAll's curated collection of Japan's finest establishments.\n\nReturns full restaurant details including price_range.starting_price (minimum price, includes \u00a58,000 Booking Fee).",
"inputSchema": {
"properties": {
"restaurant_id": {
"description": "The unique ID of the restaurant",
"type": "number"
}
},
"required": [
"restaurant_id"
],
"type": "object"
},
"name": "get_restaurant_details"
},
{
"annotations": {
"openWorldHint": false,
"readOnlyHint": true
},
"description": "Get exclusive menu items and courses for a specific Michelin-starred restaurant through TableAll's premium reservation service.",
"inputSchema": {
"properties": {
"restaurant_id": {
"description": "The unique ID of the restaurant",
"type": "number"
}
},
"required": [
"restaurant_id"
],
"type": "object"
},
"name": "get_restaurant_menu"
},
{
"annotations": {
"openWorldHint": false,
"readOnlyHint": true
},
"description": "Check real-time availability for Japan's most coveted Michelin-starred restaurants through TableAll's exclusive booking system.\n\nDATE HANDLING - CRITICAL:\nWhen user provides only month/day without year:\n1. Default to the current year\n2. If the resulting date would be in the past, use NEXT year instead\nExample (current date: 2026/1/28):\n- User says \"2/12-2/15\" \u2192 use 2026/2/12-2026/2/15 (future date in current year)\nExample (current date: 2026/3/12):\n- User says \"2/12-2/15\" \u2192 use 2027/2/12-2027/2/15 (past date, so use next year)\nNEVER search for dates in the past.\n\nReturns two types of openings:\n1. Fixed seats (seat_type: \"fixed\"): The opening has a fixed number of seats. You MUST book all seats together - partial booking is not allowed. For example, a 4-seat opening requires exactly 4 guests.\n2. Flexible seats (seat_type: \"flexible\"): You can choose your party size within the specified range (min_num_people to max_num_people).\n\nWhen making a reservation:\n- For fixed seats: party_size must equal the fixed_seats value\n- For flexible seats: party_size must be within min_seats and max_seats range",
"inputSchema": {
"properties": {
"by_menu_item": {
"default": false,
"description": "Group availability by menu items",
"type": "boolean"
},
"daily_or_minutes": {
"default": "minutes",
"description": "Time granularity - \"daily\" for daily view or \"minutes\" for minute-level detail",
"enum": [
"daily",
"minutes"
],
"type": "string"
},
"end_date": {
"description": "End date in YYYY-MM-DD format",
"type": "string"
},
"num_people": {
"description": "Number of people/party size (optional)",
"minimum": 1,
"type": "number"
},
"restaurant_id": {
"description": "Specific restaurant ID (optional)",
"type": "number"
},
"start_date": {
"description": "Start date in YYYY-MM-DD format",
"type": "string"
}
},
"type": "object"
},
"name": "check_availability"
},
{
"annotations": {
"openWorldHint": false,
"readOnlyHint": true
},
"description": "Search for restaurants with availability in a specified date range.\n\nThis is the most efficient way to find available restaurants. Instead of:\n1. Calling search_restaurants to get a list\n2. Calling check_availability for each restaurant individually\n\nYou can use this single tool to get all restaurants with openings in one request.\n\nUse this tool when:\n- User wants to find any available restaurant in a region/area\n- User specifies a date range and wants to see what's available\n- User has flexible restaurant preferences but specific date requirements\n\nDATE HANDLING - CRITICAL:\nWhen user provides only month/day without year:\n1. Default to the current year\n2. If the resulting date would be in the past, use NEXT year instead\nExample (current date: 2026/1/28):\n- User says \"2/12-2/15\" \u2192 use 2026/2/12-2026/2/15 (future date in current year)\nExample (current date: 2026/3/12):\n- User says \"2/12-2/15\" \u2192 use 2027/2/12-2027/2/15 (past date, so use next year)\nNEVER search for dates in the past.\n\nDATE RANGE RULE:\nWhen user specifies a single date (e.g., \"December 20th\"):\n- Automatically search from 2 days before to 3 days after the specified date\n- Inform the user: \"I'll search around your preferred date to show you more options.\"\n- Example: User says \"December 20th\" \u2192 start_date: \"2024-12-18\", end_date: \"2024-12-23\"\n- If user explicitly wants only that specific date (e.g., \"only December 20th\", \"exactly on the 20th\"), respect their request and use that single date for both start_date and end_date.\n\nParameters:\n- start_date, end_date: Required. Date range to search (YYYY-MM-DD)\n- prefecture: Optional. Filter by prefecture. Available values: Tokyo, Kyoto, Osaka, Sapporo, Kanazawa, Komatsu, Toyama, Fukuoka, Nagoya, Ise Shima, Kobe, Niseko, Shizuoka, Nagano, Hiroshima, Shikoku, Niigata\n- area: Optional. Filter by area (e.g., \"Ginza\", \"Shibuya\")\n- genre: Optional. Filter by cuisine type (e.g., \"Sushi\", \"French\")\n- num_people: Optional. Filter by party size\n\nReturns restaurants with their available openings, including:\n- Restaurant basic info (name, cuisine, location, michelin stars, price_range, open_time, closed_days)\n- Available openings with date, time, seat type, and course info\n\nPRICE NOTE:\n- price_range.starting_price shows the minimum price (e.g., \"\u00a539,000\u301c\")\n- All prices include TableAll's \u00a58,000 Booking Fee",
"inputSchema": {
"properties": {
"area": {
"description": "Specific area within prefecture (e.g., \"Ginza\", \"Shibuya\")",
"type": "string"
},
"end_date": {
"description": "End date in YYYY-MM-DD format (required)",
"type": "string"
},
"genre": {
"description": "Cuisine type (e.g., \"Sushi\", \"Kaiseki\", \"French\", \"Italian\")",
"enum": [
"Sushi",
"Kaiseki",
"Tempura",
"Wagyu",
"Italian",
"French",
"Chinese",
"Innovative",
"Spanish",
"Yakiniku",
"Yakitori",
"Teppanyaki",
"Unagi",
"Dessert Dining",
"Kushiage",
"Shabushabu Sukiyaki",
"Izakaya",
"Ramen",
"Thai",
"Soba",
"Tonkatsu"
],
"type": "string"
},
"limit": {
"default": 20,
"description": "Maximum number of restaurants to return (default: 20, max: 100)",
"maximum": 100,
"minimum": 1,
"type": "number"
},
"num_people": {
"description": "Number of guests to filter availability",
"minimum": 1,
"type": "number"
},
"offset": {
"default": 0,
"description": "Number of restaurants to skip for pagination (default: 0)",
"minimum": 0,
"type": "number"
},
"prefecture": {
"description": "Prefecture/region filter. Values not in the allowed list will be ignored.",
"enum": [
"Tokyo",
"Kyoto",
"Osaka",
"Sapporo",
"Kanazawa",
"Komatsu",
"Toyama",
"Fukuoka",
"Nagoya",
"Ise Shima",
"Kobe",
"Niseko",
"Shizuoka",
"Nagano",
"Hiroshima",
"Shikoku",
"Niigata"
],
"type": "string"
},
"start_date": {
"description": "Start date in YYYY-MM-DD format (required)",
"type": "string"
}
},
"required": [
"start_date",
"end_date"
],
"type": "object"
},
"name": "search_available_restaurants"
},
{
"annotations": {
"openWorldHint": false,
"readOnlyHint": true
},
"description": "Get formatted information for a specific Michelin-starred restaurant from TableAll's exclusive collection as a readable resource.",
"inputSchema": {
"properties": {
"restaurant_id": {
"description": "The unique ID of the restaurant",
"type": "string"
}
},
"required": [
"restaurant_id"
],
"type": "object"
},
"name": "get_restaurant_resource"
},
{
"annotations": {
"openWorldHint": false,
"readOnlyHint": true
},
"description": "Get cancel policies for a restaurant before making a reservation.\n\nAlways call this tool before create_reservation or create_reservation_request to inform the user about cancellation terms.\n\nIMPORTANT - For RESERVATION REQUESTS (create_reservation_request):\nBefore showing the cancel policy, you MUST first explain how reservation requests work:\n\"How does it work?\nWe will check the availability based on the information you provide below.\n- If available, we will reserve immediately, charge your credit card, and send you a confirmation email.\n- If not available, we will notify you by email. No charge will be made.\n* You can only cancel a request before we confirm the availability with the restaurants (within 10 minutes ~ 24 hours of the request).\"\n\nThen introduce the cancel policy with:\n\"Once your reservation request is confirmed and a booking is made, the following cancellation policy will apply:\"\n\nCRITICAL - BOOKING FEE NOTICE (MUST ALWAYS DISPLAY):\nWhen displaying cancellation policies to users, you MUST ALWAYS include this notice at the end:\n\"* Note: The booking fee is non-refundable regardless of cancellation timing.\"\nThis notice is MANDATORY and must be shown every time you display cancellation policies, whether for direct reservations or reservation requests. NEVER skip this notice.\n\nReturns:\n- policies: Array of cancel policy tiers (days_before, cancel_fee_percentage)\n- no_show_fee_percentage: Fee for no-show\n- booking_fee_note: MUST be displayed to user - booking fee is non-refundable",
"inputSchema": {
"properties": {
"course_id": {
"description": "Course external ID (optional, for course-specific policies)",
"type": "string"
},
"restaurant_id": {
"description": "Restaurant ID to get cancel policies for",
"type": "number"
}
},
"required": [
"restaurant_id"
],
"type": "object"
},
"name": "get_cancel_policies"
},
{
"annotations": {
"destructiveHint": false,
"idempotentHint": false,
"openWorldHint": false,
"readOnlyHint": false
},
"description": "Create a direct reservation for an available opening.\n\nREQUIRED FLOW - Follow these steps in order:\n\nSTEP 1: CANCEL POLICY - Before collecting user information:\n- Call get_cancel_policies to retrieve the cancellation terms\n- Explain the cancel policy to the user clearly\n- MUST include: \"* Note: The booking fee is non-refundable regardless of cancellation timing.\"\n- Ensure the user understands the cancellation fees before proceeding\n\nSTEP 2: COLLECT EMAIL ONLY - First, ask ONLY for email address:\n\"To proceed with the reservation, please provide your email address.\"\n- Do NOT ask for name, country, or phone yet\n- Wait for the user to provide their email\n\nSTEP 3: CHECK USER & COLLECT ADDITIONAL INFO IF NEEDED:\nAfter receiving the email, call this tool with only the email.\n- If user EXISTS: The API will proceed with the existing user info. No additional info needed.\n- If user DOES NOT EXIST: The API will return an error with code \"USER_NOT_FOUND\".\n In this case, ask the user for additional information:\n \"It looks like you don't have a TableAll account yet. To create one, please provide:\n - Full name (first and last name)\n - Country\n - Phone number\"\n Then call this tool again with all the information.\n When a new account is created, the API will return password_reset_url.\n You MUST display this to the user:\n \"Your TableAll account has been created! Please set your password using this link: [password_reset_url]\n Note: The same link has also been sent to your email address.\"\n\nSTEP 4: CONFIRMATION - After collecting all information, you MUST:\n1. Display a summary of all reservation details to the user:\n - Restaurant name\n - Date and time\n - Number of guests\n - Course name\n - Email address (highlight this for verification)\n - Cancel policy summary\n2. Ask the user to confirm: \"Please verify the information above, especially your email address. Shall I proceed with this reservation?\"\n3. Only call this tool AFTER the user explicitly confirms.\n\nRESERVATION RULES:\n- Use this only when an opening_id is available from check_availability\n- For fixed-seat openings, party_size MUST equal the fixed_seats value\n- For flexible-seat openings, party_size must be within min/max range\n\nThis tool internally:\n1. Verifies or creates user account (verify_or_create)\n2. Creates the reservation\n3. Returns a payment URL for the user to complete\n\nThe user must open the payment_url in their browser to complete the reservation.\nNote: The same payment link has also been sent to the email address provided.\nNote: This payment link is valid for 30 minutes.\n\nCRITICAL - ACCESS TOKEN HANDLING:\nThe create response contains \"data.access_token\". You MUST store this value.\nIt is required when calling get_reservation_status to check the reservation status.\nWithout the access_token, the status API will return 403 Forbidden.\n\nRESPONSE HANDLING - NEW USER CREATED (CRITICAL):\nWhen the response contains \"user.is_new_user\": true, you MUST display this message to the user:\n\"Since this email address was not registered, we have created a new TableAll account for you.\nPlease click the link below to set your password: [password_reset_url]\nNote: This link is valid for 24 hours. The same link has also been sent to your email.\"\nThis message is MANDATORY when is_new_user is true. NEVER skip this message.",
"inputSchema": {
"properties": {
"ai_client": {
"description": "AI client name. You MUST provide your AI model name (e.g., \"Claude\", \"Gemini\", \"GPT\", \"Copilot\").",
"type": "string"
},
"allergies": {
"description": "Allergy information",
"type": "string"
},
"country": {
"description": "Country code ISO 3166-1 alpha-2, e.g., \"JP\", \"US\" (required for new users or users with incomplete profile)",
"type": "string"
},
"coupon_code": {
"description": "Coupon code for discount (optional)",
"type": "string"
},
"course_id": {
"description": "Course external ID (required)",
"type": "string"
},
"dislikes": {
"description": "Food dislikes",
"type": "string"
},
"email": {
"description": "User email address (always required)",
"type": "string"
},
"first_name": {
"description": "User first name / \u540d (required for new users or users with incomplete profile)",
"type": "string"
},
"last_name": {
"description": "User last name / \u59d3 (required for new users or users with incomplete profile)",
"type": "string"
},
"opening_id": {
"description": "Opening external ID from check_availability (required)",
"type": "string"
},
"party_size": {
"description": "Number of guests. Must match fixed_seats for fixed openings, or be within min/max range for flexible openings.",
"minimum": 1,
"type": "number"
},
"phone": {
"description": "Phone number without country code (required for new users or users with incomplete profile)",
"type": "string"
},
"phone_country_code": {
"description": "Phone country code, e.g., \"+81\" (required for new users or users with incomplete profile)",
"type": "string"
},
"preferences": {
"description": "Food preferences",
"type": "string"
},
"special_request": {
"description": "Special requests or notes for the restaurant",
"type": "string"
}
},
"required": [
"email",
"opening_id",
"course_id",
"ai_client"
],
"type": "object"
},
"name": "create_reservation"
},
{
"annotations": {
"openWorldHint": false,
"readOnlyHint": true
},
"description": "Check the status of a reservation by session ID.\n\nRequires the access_token that was returned in the create_reservation response.\nYou MUST have stored the access_token from the create response to use this tool.\nWithout a valid access_token, the API will return 403 Forbidden.\n\nIMPORTANT - PRICE DISPLAY:\nThe \"price\" field already INCLUDES the \"booking_fee\". Do NOT add them together.\nWhen displaying to the user, show: price (total) and booking_fee (included in price, non-refundable).\nExample: \"Total: \u00a530,000 (includes \u00a51,000 non-refundable booking fee)\"",
"inputSchema": {
"properties": {
"access_token": {
"description": "Access token returned from create_reservation response (data.access_token). Required for authorization.",
"type": "string"
},
"session_id": {
"description": "Reservation session ID returned from create_reservation",
"type": "string"
}
},
"required": [
"session_id",
"access_token"
],
"type": "object"
},
"name": "get_reservation_status"
},
{
"annotations": {
"destructiveHint": false,
"idempotentHint": false,
"openWorldHint": false,
"readOnlyHint": false
},
"description": "Create a reservation request when no openings are available.\n\nREQUIRED FLOW - Follow these steps in order:\n\nSTEP 1: EXPLAIN HOW RESERVATION REQUEST WORKS - First, explain to the user:\n\"How does it work?\nWe will check the availability based on the information you provide below.\n- If available, we will reserve immediately, charge your credit card, and send you a confirmation email.\n- If not available, we will notify you by email. No charge will be made.\n* You can only cancel a request before we confirm the availability with the restaurants (within 10 minutes ~ 24 hours of the request).\"\n\nSTEP 2: CANCEL POLICY - After explaining how it works:\n- Call get_cancel_policies to retrieve the cancellation terms\n- Explain: \"Once your reservation request is confirmed and a booking is made, the following cancellation policy will apply:\"\n- Display the cancel policy clearly\n- MUST include: \"* Note: The booking fee is non-refundable regardless of cancellation timing.\"\n- Ensure the user understands these fees apply AFTER the reservation is confirmed\n\nSTEP 3: COLLECT GUEST COUNT - You MUST confirm the number of adults and children:\n- If user only says total number (e.g., \"3 people\"), you MUST ask: \"Will there be any children in your party?\"\n- If children: Ask \"How many adults and how many children?\"\n- If no children: Confirm \"So that will be [X] adults, no children. Is that correct?\"\n- NEVER skip this confirmation step\n\nSTEP 4: COLLECT EMAIL ONLY - First, ask ONLY for email address:\n\"To proceed with the reservation request, please provide your email address.\"\n- Do NOT ask for name, country, or phone yet\n- Wait for the user to provide their email\n\nSTEP 5: CHECK USER & COLLECT ADDITIONAL INFO IF NEEDED:\nAfter receiving the email, call this tool with only the email.\n- If user EXISTS: The API will proceed with the existing user info. No additional info needed.\n- If user DOES NOT EXIST: The API will return an error with code \"USER_NOT_FOUND\".\n In this case, ask the user for additional information:\n \"It looks like you don't have a TableAll account yet. To create one, please provide:\n - Full name (first and last name)\n - Country\n - Phone number\"\n Then call this tool again with all the information.\n When a new account is created, the API will return password_reset_url.\n You MUST display this to the user:\n \"Your TableAll account has been created! Please set your password using this link: [password_reset_url]\n Note: The same link has also been sent to your email address.\"\n\nSTEP 6: CONFIRMATION - After collecting all information, you MUST:\n1. Display a summary of all reservation request details to the user:\n - Restaurant name\n - Preferred date(s) and time range (Japan Time)\n - Number of adults\n - Number of children\n - Course name\n - Email address (highlight this for verification)\n2. Ask the user to confirm: \"Please verify the information above, especially your email address. Shall I proceed with this reservation request?\"\n3. Only call this tool AFTER the user explicitly confirms.\n\nRESERVATION REQUEST RULES:\n- Use this when check_availability returns no results\n- Allows specifying multiple preferred dates\n- Restaurant will review and approve/decline the request\n\nDATE HANDLING - CRITICAL:\n- When user says \"any day in [month]\" (e.g., \"any day in January\"), include ALL days of that month\n- When user says \"any day during [period]\" (e.g., \"any day from Jan 10-20\"), include ALL days in that range\n- When user says \"anytime in [week/period]\", include ALL days in that period\n- Do NOT arbitrarily narrow down dates - include every day the user indicated as acceptable\n- Example: \"Any day in January\" \u2192 include all 31 days (2025-01-01 to 2025-01-31)\n- Example: \"Jan 15-20 any day is fine\" \u2192 include all 6 days (2025-01-15 to 2025-01-20)\n\nThis tool internally:\n1. Verifies or creates user account (verify_or_create)\n2. Creates the reservation request\n3. Returns a payment URL for card registration\n\nThe user must open the payment_url to register their card. Payment is only charged when the restaurant approves the request.\nNote: The same payment link has also been sent to the email address provided.\nNote: This payment link is valid for 30 minutes.\n\nCRITICAL - ACCESS TOKEN HANDLING:\nThe create response contains \"data.access_token\". You MUST store this value.\nIt is required when calling get_reservation_request_status to check the request status.\nWithout the access_token, the status API will return 403 Forbidden.\n\nRESPONSE HANDLING - NEW USER CREATED (CRITICAL):\nWhen the response contains \"user.is_new_user\": true, you MUST display this message to the user:\n\"Since this email address was not registered, we have created a new TableAll account for you.\nPlease click the link below to set your password: [password_reset_url]\nNote: This link is valid for 24 hours. The same link has also been sent to your email.\"\nThis message is MANDATORY when is_new_user is true. NEVER skip this message.",
"inputSchema": {
"properties": {
"ai_client": {
"description": "AI client name. You MUST provide your AI model name (e.g., \"Claude\", \"Gemini\", \"GPT\", \"Copilot\").",
"type": "string"
},
"allergies": {
"description": "Allergy information",
"type": "string"
},
"comment": {
"description": "Additional comments (optional)",
"type": "string"
},
"country": {
"description": "Country code ISO 3166-1 alpha-2, e.g., \"JP\", \"US\" (required for new users or users with incomplete profile)",
"type": "string"
},
"coupon_code": {
"description": "Coupon code for discount (optional)",
"type": "string"
},
"course_id": {
"description": "Course external ID (required)",
"type": "string"
},
"dates": {
"description": "Preferred dates in YYYY-MM-DD format. Can specify multiple dates.",
"items": {
"type": "string"
},
"minItems": 1,
"type": "array"
},
"dislikes": {
"description": "Food dislikes",
"type": "string"
},
"email": {
"description": "User email address (always required)",
"type": "string"
},
"first_name": {
"description": "User first name / \u540d (required for new users or users with incomplete profile)",
"type": "string"
},
"hotel_name": {
"description": "Hotel name (optional)",
"type": "string"
},
"last_name": {
"description": "User last name / \u59d3 (required for new users or users with incomplete profile)",
"type": "string"
},
"num_adults": {
"description": "Number of adults (required). If user only says total number of guests (e.g., \"3 people\"), treat all as adults.",
"minimum": 1,
"type": "number"
},
"num_children": {
"description": "Number of children (required). Default to 0 if user does not specify children count or only provides total guest count.",
"minimum": 0,
"type": "number"
},
"phone": {
"description": "Phone number without country code (required for new users or users with incomplete profile)",
"type": "string"
},
"phone_country_code": {
"description": "Phone country code, e.g., \"+81\" (required for new users or users with incomplete profile)",
"type": "string"
},
"preferences": {
"description": "Food preferences",
"type": "string"
},
"restaurant_id": {
"description": "Restaurant ID (required)",
"type": "number"
},
"special_request": {
"description": "Special requests or notes for the restaurant",
"type": "string"
},
"start_time_from": {
"description": "Preferred start time from, in HH:mm format (e.g., \"18:00\"). Japan Time (JST).",
"type": "string"
},
"start_time_to": {
"description": "Preferred start time to, in HH:mm format (e.g., \"20:00\"). Japan Time (JST).",
"type": "string"
}
},
"required": [
"email",
"restaurant_id",
"course_id",
"num_adults",
"num_children",
"dates",
"start_time_from",
"start_time_to",
"ai_client"
],
"type": "object"
},
"name": "create_reservation_request"
},
{
"annotations": {
"openWorldHint": false,
"readOnlyHint": true
},
"description": "Check the status of a reservation request by session ID.\n\nRequires the access_token that was returned in the create_reservation_request response.\nYou MUST have stored the access_token from the create response to use this tool.\nWithout a valid access_token, the API will return 403 Forbidden.\n\nIMPORTANT - PRICE DISPLAY:\nThe \"price\" field already INCLUDES the \"booking_fee\". Do NOT add them together.\nWhen displaying to the user, show: price (total) and booking_fee (included in price, non-refundable).\nExample: \"Total: \u00a530,000 (includes \u00a51,000 non-refundable booking fee)\"",
"inputSchema": {
"properties": {
"access_token": {
"description": "Access token returned from create_reservation_request response (data.access_token). Required for authorization.",
"type": "string"
},
"session_id": {
"description": "Reservation request session ID returned from create_reservation_request",
"type": "string"
}
},
"required": [
"session_id",
"access_token"
],
"type": "object"
},
"name": "get_reservation_request_status"
}
]
}
},
"bad_protocol_status_code": 200,
"delete_error": null,
"delete_status_code": null,
"expired_session_error": null,
"expired_session_status_code": null,
"issues": [
"missing_session_id",
"missing_protocol_header",
"bad_protocol_not_rejected"
],
"last_event_id_visible": false,
"protocol_header_present": false,
"requested_protocol_version": "2024-11-05",
"session_id_present": false,
"transport": "sse"
}
},
"remote_url": "https://mcp.tableall.com/sse",
"server_card_payload": null,
"server_identifier": "com.tableall/mcp"
}
Known versions
1.0.0
Validation history
7 day score delta
+0.0
30 day score delta
+1.1
Recent healthy ratio
80%
Freshness
594.2h
| Timestamp | Status | Score | Latency | Tools |
|---|---|---|---|---|
| Apr 09, 2026 08:55:13 AM UTC | Degraded | 77.0 | 4880.3 ms | 11 |
| Apr 09, 2026 12:54:57 AM UTC | Degraded | 77.5 | 4738.9 ms | 11 |
| Apr 08, 2026 12:51:38 AM UTC | Healthy | 75.9 | 4434.6 ms | 11 |
| Apr 07, 2026 12:46:48 AM UTC | Healthy | 75.9 | 4542.5 ms | 11 |
| Apr 06, 2026 12:43:34 AM UTC | Healthy | 75.9 | 4441.4 ms | 11 |
| Apr 05, 2026 12:41:34 AM UTC | Healthy | 75.9 | 4503.7 ms | 11 |
| Apr 04, 2026 12:40:10 AM UTC | Healthy | 75.9 | 4397.1 ms | 11 |
| Apr 03, 2026 12:35:24 AM UTC | Healthy | 75.9 | 4548.2 ms | 11 |
Validation timeline
| Validated | Summary | Score | Protocol | Auth mode | Tools | High-risk tools | Changes |
|---|---|---|---|---|---|---|---|
| Apr 09, 2026 08:55:13 AM UTC | Degraded | 77.0 | 2024-11-05 | oauth_supported | 11 | 2 | none |
| Apr 09, 2026 12:54:57 AM UTC | Degraded | 77.5 | 2024-11-05 | oauth_supported | 11 | 2 | summary_changed auth_mode_changed |
| Apr 08, 2026 12:51:38 AM UTC | Healthy | 75.9 | 2024-11-05 | public | 11 | 2 | none |
| Apr 07, 2026 12:46:48 AM UTC | Healthy | 75.9 | 2024-11-05 | public | 11 | 2 | none |
| Apr 06, 2026 12:43:34 AM UTC | Healthy | 75.9 | 2024-11-05 | public | 11 | 2 | none |
| Apr 05, 2026 12:41:34 AM UTC | Healthy | 75.9 | 2024-11-05 | public | 11 | 2 | none |
| Apr 04, 2026 12:40:10 AM UTC | Healthy | 75.9 | 2024-11-05 | public | 11 | 2 | none |
| Apr 03, 2026 12:35:24 AM UTC | Healthy | 75.9 | 2024-11-05 | public | 11 | 2 | none |
| Apr 02, 2026 12:22:26 AM UTC | Healthy | 75.4 | 2024-11-05 | public | 11 | 2 | none |
| Mar 31, 2026 11:54:37 PM UTC | Healthy | 75.4 | 2024-11-05 | public | 12 | 2 | none |
| Mar 30, 2026 11:41:55 PM UTC | Healthy | 75.4 | 2024-11-05 | public | 12 | 2 | none |
| Mar 29, 2026 11:24:46 PM UTC | Healthy | 75.4 | 2024-11-05 | public | 12 | 2 | none |
Recent validation runs
| Started | Status | Summary | Latency | Checks |
|---|---|---|---|---|
| Apr 09, 2026 08:55:08 AM UTC | Completed | Degraded | 4880.3 ms | action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe |
| Apr 09, 2026 12:54:52 AM UTC | Completed | Degraded | 4738.9 ms | action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe |
| Apr 08, 2026 12:51:33 AM UTC | Completed | Healthy | 4434.6 ms | action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe |
| Apr 07, 2026 12:46:43 AM UTC | Completed | Healthy | 4542.5 ms | action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe |
| Apr 06, 2026 12:43:30 AM UTC | Completed | Healthy | 4441.4 ms | action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe |
| Apr 05, 2026 12:41:30 AM UTC | Completed | Healthy | 4503.7 ms | action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe |
| Apr 04, 2026 12:40:06 AM UTC | Completed | Healthy | 4397.1 ms | action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe |
| Apr 03, 2026 12:35:19 AM UTC | Completed | Healthy | 4548.2 ms | action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe |
| Apr 02, 2026 12:22:21 AM UTC | Completed | Healthy | 4565.3 ms | action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe |
| Mar 31, 2026 11:54:32 PM UTC | Completed | Healthy | 4530.6 ms | action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe |