mcpbeat

Bity MCP Server

io.github.mcp-dir/bity-mcp
answering

Bity is answering right now. Last checked 2 min ago. It exposes 14 tools. Last commit 11 Jun 2026.

Bity crypto bank (Bitybank / Bitypreço), account balance per coin, market data (ticker, order book,

Uptime history 40 hours of history · worst hour 75%
40 hours agonow
98.9%
Uptime 24h
91 of 92 checks
14
Tools
read from the server
612 ms
Response time
average over 24h
0
Stars
last commit 11 Jun 2026

Connect this server

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

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

Available tools 14

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

bity
bity_executed_orders
Histórico de ordens já executadas da conta. `market` opcional pra filtrar por par.
bity_get_balance
Saldo da conta: disponível e bloqueado por moeda (ex.: BTC, BTC_locked, BRL, BRL_locked). O saldo total de cada moeda é disponível + bloqueado.
bity_list_accounts
Lista as contas Bity conectadas a este install — id, label.
bity_open_orders
Lista as ordens em aberto (pendentes) da conta. `market` opcional pra filtrar por par.
bity_order_status
Status de uma ordem específica pelo seu id. Bulk support: accepts order_ids for batched execution.
bity_orderbook
Livro de ofertas (bids/asks) de um par. Público.
bity_ticker
Ticker 24h de um par (último preço, melhor compra/venda, volume). Público, não exige saldo.
bity_trades
Negociações recentes (trades públicos) de um par. Público.
authenticate
authenticate
MCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header `Authorization: Bearer <token>` for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "<jwt>" } after the user pastes, or with no args to get the link.
connect
connect
Returns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.
marketplace
marketplace
The official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin.
report
report_bug
Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.
show
show_version
Show the current MCP platform and adapter versions.
toolkit
toolkit_info
Returns the current toolkit state: installed MCPs, their connection status, and how many catalog tools each exposes.

Endpoints

URLTransportStateLatencyChecked
https://api.mcp.ai/p_bity streamable-http answering 675 ms 2 min ago

Bity — questions

Answers built from our own checks of this server.

What can Bity do?
It exposes 14 tools, read directly from the server on our last check. Among them: authenticate, bity_executed_orders, bity_get_balance, bity_list_accounts, bity_open_orders, bity_orderbook and 8 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 Bity working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 92 checks got a reply (98.9%), average response time 612 ms. The bar chart above shows every period we have measured.
How do I connect Bity?
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 Bity need an API key?
No. Bity completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 14 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Bity?
It answers our handshake in 612 ms on average, which is faster than 15% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Bity open source?
Yes — it is published under the MIT licence and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.