Tabula Mcp

io.github.tabulacreditPublished by GitHub account tabulacreditv0.2.0Updated Nov 6, 2026

Credit for AI agents: pay x402 sellers from a credit line, repay with one signature and no ETH

The publisher's own server: Tabula MCP

VerifiedSTDIODesktop onlyFinanceAI & ML

Overview

AI-generated overview

Local MCP server that gives an AI agent a credit line on-chain, letting it pay x402 sellers and repay loans without holding ETH.

What you can do
  • Pay x402 sellers from an agent credit line, with optional autopay.
  • Borrow cash against the agent's on-chain identity, capped by a configured maximum loan size.
  • Repay loans with a single signature, without needing ETH for gas.
  • Use a sub-agent key that can only pay and read, instead of the owner's identity key.
  • Point the server at a known deployment's ledger, batch repayer or bond zap, or at a custom gateway and RPC.
When to use it
Relevant when an agent needs to buy from x402-priced services and settle payments on-chain without managing ETH, or when you want spending limited to a sub-agent key or a maximum loan amount.
Requirements
Runs locally over stdio from the npm package tabula-mcp. Requires TABULA_GATEWAY_URL (Tabula gateway for Robinhood Chain or Base). Either TABULA_AGENT_ID plus the TABULA_AGENT_KEY private key, or a TABULA_SUBKEY. Optional: TABULA_AUTOPAY, TABULA_MAX_CASH_USD, TABULA_RPC_URL, and deployment overrides TABULA_LEDGER, TABULA_BATCH_REPAYER, TABULA_BOND_ZAP. Network access to the chain and gateway.
Before you install
TABULA_AGENT_KEY is a private key that owns the agent's identity; anyone holding it controls that identity. TABULA_SUBKEY is also a secret, though limited to paying and reading. The server signs on-chain transactions and can borrow money, so set TABULA_MAX_CASH_USD and leave TABULA_AUTOPAY off unless you want automatic payments. It reads the chain RPC to check what it signs; a custom TABULA_RPC_URL changes that check.

Installation

In SourceWeft

  1. Open Tabula Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the server did not start.

Version history

2
  1. v0.2.0LatestNov 6, 2026
  2. v0.1.1Nov 4, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Tabula integrations