mcp-registry/io.github.hellobooksaiagents/hellobooks-mcp · v1.5.0
As of 2026-10-23 23:30 UTC, the Hellobooksaiagents Hellobooks MCP server is up with a Glimind reliability score of 87/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 5 minutes.
AI agents for bookkeeping, reconciliation, and financial close for SMBs.
Claude Code
claude mcp add --transport http hellobooksaiagents-hellobooks-mcp-server https://agents.hellobooks.ai/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"hellobooksaiagents-hellobooks-mcp-server": {
"type": "http",
"url": "https://agents.hellobooks.ai/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
29 of 29 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
2 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
1 parameter(s) across 1 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
In the last 30 days: 0 tool(s) removed and 5 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.hellobooksaiagents%2Fhellobooks-mcp/fixes
{
"name": "analyze_balance_sheet",
"description": "Take a Balance Sheet CSV export from QuickBooks Online, Xero, Zoho Books, or Wave (source auto-detected) and run three checks: (1) bs.equation_broken — the fundamental accounting equation Assets = Liabilities + Equity does not hold (every downstream ratio analysis is invalid until fixed); (2) bs.negative_asset — Cash / AR / Inventory line items with negative balances (reconciliation error signal); (3) bs.negative_equity — Total Equity < 0 (insolvency signal). Input is raw CSV text of a Balance S",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"csvText"
],
"properties": {
"csvText": {
"type": "string",
"maxLength": 5242880,
"minLength": 1,
"description": "Raw CSV text of a Balance Sheet report. Works with QuickBooks Online (Reports → Balance Sheet), Xero (Reports → Balance Sheet), Zoho Books (Reports → Balance Sheet), and Wave (Reports → Balance Sheet). Statement should include Total Assets, Total Liabilities, and Total Equity rows. Source is auto-detected from section name signatures."
},
"fileName": {
"type": "string",
"maxLength": 200,
"description": "Optional filename for the share-page label."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "analyze_journal_variance",
"description": "Compare two periods of journal-entry data (QBO or Xero — source auto-detected from headers) and flag accounts whose movement deviates materially between periods. Aggregates lines per account into a net total for each period, then surfaces accounts where the period-over-period change crosses a materiality threshold (≥5% relative AND ≥$100 absolute; severity high at ≥50%, medium at ≥20%, low at ≥5%). Inputs are two CSV exports — periodACsv (earlier period) and periodBCsv (later period). Optional p",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"periodACsv",
"periodBCsv"
],
"properties": {
"periodACsv": {
"type": "string",
"maxLength": 5242880,
"minLength": 1,
"description": "Raw CSV text of the EARLIER period's journal-entry export (QBO Journal Entries or Xero Manual Journals). Source is auto-detected from the headers."
},
"periodBCsv": {
"type": "string",
"maxLength": 5242880,
"minLength": 1,
"description": "Raw CSV text of the LATER period's journal-entry export. Source is auto-detected from the headers (must match periodACsv)."
},
"periodALabel": {
"type": "string",
"maxLength": 80,
"description": "Optional human label for the earlier period — e.g. \"Q1 FY2024\". Used in flag messages."
},
"periodBLabel": {
"type": "string",
"maxLength": 80,
"description": "Optional human label for the later period — e.g. \"Q2 FY2024\"."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "analyze_profit_loss",
"description": "Take a Profit & Loss / Income Statement CSV export from QuickBooks Online, Xero, Zoho Books, or Wave (source auto-detected from section names) and run three checks: (1) pnl.subtotal_mismatch — each \"Total Section\" subtotal equals the sum of its preceding line items (catches missing or duplicated rows); (2) pnl.negative_expense — flags expense-section line items with negative amounts (usually sign-flips or refunds posted to the wrong side); (3) pnl.margin_red_flag — gross-profit margin < 5% or > ",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"csvText"
],
"properties": {
"csvText": {
"type": "string",
"maxLength": 5242880,
"minLength": 1,
"description": "Raw CSV text of a Profit & Loss / Income Statement report. Works with QuickBooks Online (Reports → Profit and Loss), Xero (Reports → Profit and Loss), Zoho Books (Reports → Profit & Loss), and Wave (Reports → Profit & Loss). Source is auto-detected from section names. Statement should include section headers, line items, \"Total X\" subtotals, and a Net Income / Net Profit row at the bottom."
},
"fileName": {
"type": "string",
"maxLength": 200,
"description": "Optional filename for the share-page label."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.hellobooksaiagents/hellobooks-mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.hellobooksaiagents/hellobooks-mcp"}) over MCP.
list_plans ~573 tokenslist_articles ~560 tokenslist_credit_packs ~544 tokenshow_munimji_helps ~473 tokensanalyze_journal_variance ~398 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.hellobooksaiagents%2Fhellobooks-mcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.hellobooksaiagents%2Fhellobooks-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.hellobooksaiagents%2Fhellobooks-mcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.hellobooksaiagents%2Fhellobooks-mcp.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.hellobooksaiagents%2Fhellobooks-mcp?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:b4cefe48936b9cd3…, first seen 2026-10-17, included at leaf 10861 of 55,221. Version history · verify what your client received.
Compare: most reliable finance servers · most reliable accounting servers · most reliable knowledge servers · most reliable data servers · most reliable search servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-23 23:30 UTC, the Hellobooksaiagents Hellobooks MCP server is up with a Glimind reliability score of 87/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 5 minutes.
Hellobooksaiagents Hellobooks MCP server advertises 29 tools, including analyze_balance_sheet, analyze_journal_variance, analyze_profit_loss, analyze_qbo_journal_anomalies, analyze_qbo_journal_cleanup.
Point your MCP client at this streamable-http endpoint: https://agents.hellobooks.ai/mcp
Glimind scanned all 29 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.