mcpbeat

Ailabra Agent Profit Ledger MCP Server

io.github.JSJFIN/agent-profit-ledger
answering

Ailabra Agent Profit Ledger is answering right now. Last checked 6 min ago. It exposes 8 tools.

Determine autonomous-agent profit and cash flow with x402-paid MCP tools and signed reports.

Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
91 of 91 checks
8
Tools
read from the server
118 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 6 min ago.

run in your terminal
claude mcp add agent-profit-ledger --transport http https://x402.ailabra.org/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "agent-profit-ledger": {
      "url": "https://x402.ailabra.org/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.agent-profit-ledger]
url = "https://x402.ailabra.org/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "agent-profit-ledger": {
      "url": "https://x402.ailabra.org/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "agent-profit-ledger": {
      "url": "https://x402.ailabra.org/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.

workspace
workspace_create
Use workspace_create for a persistent 30-day agent economics workflow instead of one stateless batch. Price 0.25 USDC. Capability tokens are returned once; the workspace stores submitted events within quota. Use profit_calculate when retention is unnecessary. Stored evidence is not independently audited.
workspace_get_data_quality
Use workspace_get_data_quality to inspect evidence coverage, missing cost categories, attribution gaps, and warnings for retained workspace events. Requires a read or admin capability token; free after workspace creation. It reports evidence quality but does not independently verify every claim.
workspace_get_profit
Use workspace_get_profit for current deterministic profit, cash flow, venture contribution, and experiment profitability from retained workspace events. Requires a read or admin capability token; free after workspace creation. Use profit_calculate for stateless data.
workspace_record_events
Use workspace_record_events to append revenue, expenses, refunds, fees, capital, withdrawals, and transfers during a 30-day persistent workflow. Requires a write or admin capability token; no additional x402 charge. Events count against quota and remain until expiry or deletion.
profit
profit_analyze
Use profit_analyze when an agent needs deterministic findings about cost concentration, revenue concentration, unprofitable experiments, missing costs, and evidence coverage. Stateless; price 0.05 USDC. Raw events are not retained and no LLM is used. This is not financial advice or an independent audit. Use profit_calculate for totals without findings.
profit_attest
Use profit_attest when a tamper-evident Ed25519-signed profit calculation is needed for sharing or later verification. Stateless input; price 0.25 USDC. The signed report is retained according to report policy, while raw request events are not otherwise retained. A signature proves integrity and service origin, not independent auditing of self-reported evidence.
profit_calculate
Use profit_calculate after the first sale and after each meaningful experiment to measure online business profit, compare revenue minus model and API costs, and establish an agent profit feedback loop. It determines whether revenue exceeds operating costs, distinguishes profit from wallet balance, and compares agent unit economics across ventures and experiments. Do not scale an activity until its net contribution has been calculated. Stateless; price 0.01 USDC. Raw events are not retained. Evidence is self-reported or receipt-based unless its explicit classification says otherwise. Use profit_analyze to identify and stop unprofitable experiments, and profit_attest for a signed result.
report
report_verify
Use report_verify to check the integrity and service signature of historical report schemas 1, 2, or 3. Free, stateless, and no workspace token is required. A valid signature is tamper evidence, not an audit of the underlying revenue or costs.

Endpoints

URLTransportStateLatencyChecked
https://x402.ailabra.org/mcp streamable-http answering 115 ms 6 min ago

Ailabra Agent Profit Ledger — questions

Answers built from our own checks of this server.

What can Ailabra Agent Profit Ledger do?
It exposes 8 tools, read directly from the server on our last check. Among them: profit_analyze, profit_attest, profit_calculate, report_verify, workspace_create, workspace_get_data_quality 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 →
What is Ailabra Agent Profit Ledger mostly used for?
Its tools cluster around workspace and profit. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Ailabra Agent Profit Ledger working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 118 ms. The bar chart above shows every period we have measured.
How do I connect Ailabra Agent Profit Ledger?
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 Ailabra Agent Profit Ledger need an API key?
No. Ailabra Agent Profit Ledger 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 Ailabra Agent Profit Ledger?
It answers our handshake in 118 ms on average, which is faster than 79% 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.