mcpbeat

Tabular Recipe MCP Server

com.tabularrecipe/tabular-recipe
answering

Tabular Recipe is answering right now. Last checked 1 min ago. It exposes 8 tools.

Turn any recipe into a compact process table — every ingredient and step at a glance.

Uptime history 41 hours of history
41 hours agonow
100.0%
Uptime 24h
92 of 92 checks
8
Tools
read from the server
128 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

run in your terminal
claude mcp add tabular-recipe --transport http https://api.tabularrecipe.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "tabular-recipe": {
      "url": "https://api.tabularrecipe.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.tabular-recipe]
url = "https://api.tabularrecipe.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "tabular-recipe": {
      "url": "https://api.tabularrecipe.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "tabular-recipe": {
      "url": "https://api.tabularrecipe.com/mcp"
    }
  }
}

Available tools 8

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

checkout
checkout_status
Check whether an agent-created Stripe checkout is pending, paid, claimed, or expired. Requires its sessionId and secret claimToken, but no API key.
create_checkout
Create a Stripe-hosted checkout for a credit bundle without an API key. Returns a checkout URL and a secret one-time claim token. A human approves payment in Stripe; never expose or put the claim token in a URL.
claim
claim_checkout
Exchange a paid agent checkout plus its secret claim token for a new API key. The key is returned once; store it immediately.
convert
convert_recipe
Parse recipe prose and render the validated graph as self-contained HTML in one call. Costs credits; fetch /v1/pricing first.
parse
parse_recipe
Parse recipe prose into a validated rgf/0-draft operation graph. Costs credits; fetch /v1/pricing first.
render
render_recipe
Validate and render an rgf/0-draft document as escaped, self-contained HTML. Free; spends no model credits.
styles
list_styles
List every available visual theme with its name, description, color swatches, and depth ramp. Free; spends no model credits.
usage
get_usage
Read the calling key's current credit balance, today's allowance state, and aggregated usage. Free; use before a paid batch.

Endpoints

URLTransportStateLatencyChecked
https://api.tabularrecipe.com/mcp streamable-http answering 152 ms 1 min ago

Tabular Recipe — questions

Answers built from our own checks of this server.

What can Tabular Recipe do?
It exposes 8 tools, read directly from the server on our last check. Among them: checkout_status, claim_checkout, convert_recipe, create_checkout, get_usage, list_styles and 2 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Tabular Recipe working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 128 ms. The bar chart above shows every period we have measured.
How do I connect Tabular Recipe?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Tabular Recipe need an API key?
No. Tabular Recipe completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 8 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Tabular Recipe?
It answers our handshake in 128 ms on average, which is faster than 78% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.