bitledger.app

app.bitledgerPublished by bitledger.appOfficial publisherv1.0.0Updated Oct 25, 2026

Crypto tax ledger for Switzerland, Germany and Austria: review, tax figures, source of funds.

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

A remote crypto tax ledger for Switzerland, Germany and Austria that lets an assistant review transactions, tax figures and source of funds.

What you can do
Review crypto transactions and holdings in a tax ledger context for Switzerland, Germany and Austria. Retrieve tax figures calculated for those jurisdictions. Examine source-of-funds information tied to the ledger. No individual tools are listed, so exact operations are not documented.
When to use it
Useful when you need an assistant to look at crypto tax positions, figures or source-of-funds records for Swiss, German or Austrian tax purposes, rather than general portfolio tracking.
Requirements
A remote MCP endpoint reached over streamable HTTP at the provider's API host. OAuth authentication is required. No environment variables or headers are declared.
Before you install
It handles financial and tax data, so treat ledger contents as sensitive. OAuth grants the server access to your account. Tax figures are informational and should be checked before filing; no write, payment or third-party data-sharing behavior is documented.

Installation

In SourceWeft

  1. Open bitledger.app in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.bitledger%2Fbitledger/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "bitledger-app": {
      "type": "http",
      "url": "https://api.bitledger.app/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 25, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.