fivebarMCP
Privacy · updated November 3, 2026

What we keep: almost nothing.

This page says what Fivebar's MCP server, website, Fivebar Wallet and skills collect, keep and share, as they work today. When that changes, this page changes first.

The MCP server

When an agent calls https://fivebar.xyz/mcp, the server uses what's in the call (a tool name and its arguments, such as a token address, an amount or a wallet address) to answer it, and then keeps none of it. In detail:

Who else sees a call

To answer, some tools pass parts of the call to the service that has the answer. They see the request coming from Fivebar's server, not from you, but its content can include a wallet address:

Ask Tick

The chat on the home page sends what you type to /tick on Fivebar's server, which asks a language model to answer it using the same read-only tools as the MCP server.

Email updates

You can sign up for Fivebar news, product updates and offers. It's opt-in only: the box is never ticked for you, and buying credits or using Tick never signs you up.

The website

What we publish

The x402 Index and the Agent Board are built from public blockchain data: wallet addresses, payments between them, ERC-8004 agent IDs and names, and which wallet first funded which. We don't collect this from you; anyone can read it on-chain. We don't attach real-world names to wallets.

The Fivebar Wallet

The Fivebar Wallet (the fivebar npm package) runs on your computer. It creates your agent's wallet there and saves the key encrypted on that computer; the key is never sent anywhere, Fivebar included. It calls Fivebar's MCP to build swaps and reads public data like any other client. Swaps and payments it signs are on-chain transactions, public like every other.

Skills

The fivebar-trading skill is instructions only. It runs no code and collects nothing; the calls it leads an agent to make are covered above.

Questions

Message @fivebar_xyz on X.