Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Tokenbooks - crypto and fiat accounting and payments

REMOTE · API.TOKENBOOKS.IO

Crypto and fiat on one double-entry ledger: sync wallets, reconcile, cost basis, audit-ready close.

0 this week 81 Trust /100

Last scanned (20 hours ago)

Scores higher than 79% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability78
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 7153 tokens (~193/item across 37 items; 37 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management98
  • Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 1 additions. See how to fix → Fail
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 38 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 0
    • “get_filter_options” reworded the description of “pageSize” cosmetic
    • “get_filter_options” reworded the description of “pageToken” cosmetic
    • “get_filter_options” reworded the description of “search” cosmetic
    • “get_filter_options” reworded the description of “selected” cosmetic

    4 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.

  • 17 Nov 26 0
    • “get_filter_options” reworded the description of “pageSize” cosmetic
    • “get_filter_options” reworded the description of “pageToken” cosmetic
    • “get_filter_options” reworded the description of “search” cosmetic
    • “get_filter_options” reworded the description of “selected” cosmetic

    4 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.

  • 13 Nov 26 0
    • “get_filter_options” added an optional parameter “isSpam” cosmetic
    • “get_filter_options” reworded the description of “pageSize” cosmetic
    • “get_filter_options” reworded the description of “pageToken” cosmetic
    • “get_filter_options” reworded the description of “search” cosmetic
    • “get_filter_options” reworded the description of “selected” cosmetic

    5 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.

  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 4 Nov 26 0
    • Tool “get_server_info” rewrote its description, which is the text the model reads security
    • Tool “list_journal_line_assignment_options” rewrote its description, which is the text the model reads security
  • 3 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “add_wallet” rewrote its description, which is the text the model reads security
    • Tool “create_portfolio” rewrote its description, which is the text the model reads security
    • Tool “edit_accounting_rules” rewrote its description, which is the text the model reads security
    • Tool “get_asset_position” rewrote its description, which is the text the model reads security
    • Tool “get_help” rewrote its description, which is the text the model reads security
    • Tool “get_request_status” rewrote its description, which is the text the model reads security
    • Tool “get_server_info” rewrote its description, which is the text the model reads security
    • Tool “list_journal_line_assignment_options” rewrote its description, which is the text the model reads security
    • Tool “list_portfolio_transactions” rewrote its description, which is the text the model reads security
    • Tool “request_report_export” rewrote its description, which is the text the model reads security
    • Tool “simulate_fiat_quote” rewrote its description, which is the text the model reads security
    • New tool “create_workspace” functional
  • 31 Oct 26 0
    • Stability: pass → fail ▼ security
    • A breaking change shipped without a version bump: still 0.1.1 ▼ security
    • “edit_transaction” changed the type of “memo”: string → string|null ▼ functional
    • MCP protocol: Implements a current MCP spec version (2026-07-28). functional
    • MCP protocol version: 2025-11-25 → 2026-07-28 functional
  • 22 Oct 26 0
    • Stability: fail → pass ▲ security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://api.tokenbooks.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.tokenbooks.io CN=YE1,O=Let's Encrypt,C=US 28 Sept 2026 27 Dec 2026 ECDSA 256 ECDSA-SHA384 6f635e577658c724d60472a6183bf245bbf
SANs: api.tokenbooks.io
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.tokenbooks.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
tokenbooks.io. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy no-referrer

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.tokenbooks.io/mcp Verified 200
http (plaintext) http://api.tokenbooks.io/mcp HTTPS enforced 301 https://api.tokenbooks.io:443/mcp
MCP tools · 37 exposed · ~6,774 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
split_transactions ~210

Destructively move selected whole existing operation handles unchanged out of one accounting transaction into a new classified transaction; use this only when the needed economic legs already exist as operation handles. It cannot divide one transfer amount into new economic legs: repair sync normalization or use a supported persisted replacement lifecycle for a missing leg. Preview the grouping first, then track the queued requestId.

NameTypeReqDescription
operationTypestringyesAccounting operation type for the new transaction
operationsarrayyesWhole existing operation handles to move unchanged into a new transaction; do not use this to divide one normalized transfer amount into new economic legs
portfolioRefstringyesPortfolio exact name or slug
reasonstring–Optional immutable root reason. Nonempty bytes are preserved exactly; use ptx:<uuid> for transaction references.
subTypestring–Optional operation sub-type
transactionIdstringyesSource transaction to split operations out of
workspaceRefstringyesWorkspace exact name or slug
NameTypeReqDescription
errorobject––
requestIdstring––
statusstringyes–
successboolean––
transactionIdstringyes–

No examples provided.

Install

How do I install the Tokenbooks - crypto and fiat accounting and payments MCP server?

Tokenbooks - crypto and fiat accounting and payments is a hosted endpoint at https://api.tokenbooks.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.tokenbooks.io

# add to Claude Code
claude mcp add --transport http io-tokenbooks-tokenbooks 'https://api.tokenbooks.io/mcp'
Common questions

What is the Tokenbooks - crypto and fiat accounting and payments MCP server?

Tokenbooks - crypto and fiat accounting and payments is an MCP server listed in the public MCP registry as io.tokenbooks/tokenbooks. Crypto and fiat on one double-entry ledger: sync wallets, reconcile, cost basis, audit-ready close. This page covers its hosted endpoint (https://api.tokenbooks.io/mcp).

Is the Tokenbooks - crypto and fiat accounting and payments MCP server safe to use?

Tokenbooks - crypto and fiat accounting and payments scores 81 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Tokenbooks - crypto and fiat accounting and payments MCP server expose?

Tokenbooks - crypto and fiat accounting and payments exposes 37 tools: get_server_info, get_accounting_reference, list_workspaces, list_portfolios, get_portfolio, and 32 more. Their descriptions and schemas cost roughly 6,774 tokens of context every time the server is loaded.

Does the Tokenbooks - crypto and fiat accounting and payments MCP server require authentication?

No. We connected to Tokenbooks - crypto and fiat accounting and payments without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Tokenbooks - crypto and fiat accounting and payments MCP server still maintained?

Tokenbooks - crypto and fiat accounting and payments is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Tokenbooks - crypto and fiat accounting and payments MCP server?

VerifyMCP ran 13 checks on Tokenbooks - crypto and fiat accounting and payments, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.