Skip to content

papertax MCP server

io.github.AwakeWeb3/papertaxAwakeWeb3streamable-httpv0.17.0Scanned

Hyperliquid tax reports and Koinly/CTC exports for agents

6 tools: 4 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 4 write, 2 read.
  • Reads private data · 1
  • Reads text others write · 5
  • Can send data out · 0
  • 2 findings

Sign-in required, no OAuth metadata. Remote posture

Anlyon alternative

4 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the papertax MCP server can do

The papertax MCP server is published by the GitHub account AwakeWeb3. It has 6 tools. It can create or change data (4 tools: get_ledger_events, export_tax_file, create_verified_pnl and buy_report), but cannot delete data. 2 tools only read.

1 tool reads private data (get_ledger_events); 5 tools bring in text other people can write (get_tax_summary, get_ledger_events, export_tax_file and 2 more).

The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.

Its tools changed once since Anlyon Radar first saw them.

Last scanned Oct 26, 2026, version 0.17.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Changes things 4Claude Code: ask
  • buy_reportBuy the full report for one wallet and tax year ($29 up to 500 events, $59 up to 5,000, $99 above; upgrades charge the difference).Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Buy the full report for one wallet and tax year ($29 up to 500 events, $59 up to 5,000, $99 above; upgrades charge the difference). method "card" charges the account owner's saved card: needs Authorization: Bearer ptx_… and the owner's opt-in; set max_price_cents to cap it. method "usdc" returns a quote: send exactly that USDC amount on HyperEVM (chain 999) to the given address, then call again with quote_id and tx_hash. (x402 clients can instead pay in USDC on Base or Solana at GET https://papertax.xyz/api/buy?address=…&year=….) Returns an unlock_token and export links. This spends money: confirm with the user first.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • create_verified_pnlRead a wallet's results for one tax year from the chain and return a public, signed link (https://papertax.xyz/v/…) with a share image, for posting on X or anywhere else.Reads text others write1 finding

    Why it is in this group

    • The name "create_verified_pnl" says "create": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "create_verified_pnl" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "create_verified_pnl" says "create": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Read a wallet's results for one tax year from the chain and return a public, signed link (https://papertax.xyz/v/…) with a share image, for posting on X or anywhere else. Free, and nothing is stored. Dollar amounts are included only when amounts is true. With private true (the default) the wallet address is left out of the link and the page; with private false the page shows it, so check with the user first. It proves what the wallet did, not who owns it.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • export_tax_fileKoinly universal CSV, Crypto Tax Calculator advanced CSV, Cryptact custom file (JST, priced in yen by Cryptact), plain-text accountant summary, or the audit pack (audit = JSON with…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Koinly universal CSV, Crypto Tax Calculator advanced CSV, Cryptact custom file (JST, priced in yen by Cryptact), plain-text accountant summary, or the audit pack (audit = JSON with every figure tied to its transaction hash, a rules version and a data fingerprint; auditpdf = the printable PDF). Live wallets need paid access (API key or paid report). Large files are cut short with a download link.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_ledger_eventsIndividual ledger rows with default tax classification: perp opens, closes, liquidations and funding (main account and subaccounts); spot and HIP-4 outcome buys and sells; vault de…Reads private dataReads text others write1 finding

    Why it is in this group

    • The name "get_ledger_events" says "get": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • private-dataThe description's first sentence says "vault": it reads secrets.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "review": it reads comments, which other people can write.

    Findings

    • Warn

      The server marks "get_ledger_events" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "get_ledger_events" says "get": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Individual ledger rows with default tax classification: perp opens, closes, liquidations and funding (main account and subaccounts); spot and HIP-4 outcome buys and sells; vault deposits and withdrawals; staking rewards; HyperEVM swaps, protocol deposits, loans and liquidity positions; transfers; papertrade mints and staking; anything unrecognised, flagged for review. Filter by event type or venue. Without paid access, live wallets return the first 10 rows.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 2Show 2 read-only tools
  • explain_tax_treatmentpapertax's default treatment notes for Australia, the US, the UK, Canada, New Zealand, Japan or Spain, optionally for one event type.No findings

    Why it is in this group

    • The name "explain_tax_treatment" says "explain": a word for reading.
    Description, as the server wrote it
    papertax's default treatment notes for Australia, the US, the UK, Canada, New Zealand, Japan or Spain, optionally for one event type. Not tax advice.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_tax_summaryFree.Reads text others writeNo findings

    Why it is in this group

    • The name "get_tax_summary" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Free. Per-venue realised gains and losses, fees, funding, liquidations, open positions and items needing review for one wallet and tax year (subaccounts included automatically), plus trading analytics (fee and funding drag, liquidation review, net after costs by market and month). For live wallets, report gives the event count, the full report's price for this caller, whether they already have access, and how to buy it.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write5
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, no OAuth metadata

Looked at Nov 20, 2026, 18:56 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
503
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: initialize answered HTTP 503.

Posture changes

  1. Nov 13, 2026
    • HTTP status of an anonymous initialize: 200 to 503
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 4 to 0
    • Protocol version: 2025-06-18 to none

Findings

Matches of fixed checks, with the text they matched.

2 warn
  • The server marks "get_ledger_events" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "get_ledger_events" says "get": a word for reading.

    What this check looks for
  • The server marks "create_verified_pnl" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "create_verified_pnl" says "create": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 503; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 4 -> 0 (and 1 more).View diff
    • HTTP status of an anonymous initialize: 200 to 503
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 4 to 0
    • Protocol version: 2025-06-18 to none
  2. Tools5 removed, 4 changed.−5 removed~4 changedView diff
    • Removed:get_games
    • Removed:get_papertrade_positions
    • Removed:get_papertrade_results
    • Removed:get_top_traders
    • Removed:preview_papertrade_close
    • Changed:explain_tax_treatmentOnly readsinputSchema
    • Changed:export_tax_fileChanges thingsinputSchema
    • Changed:get_ledger_eventsChanges thingsdescriptioninputSchema
    • Changed:get_tax_summaryOnly readsdescriptioninputSchema

Install

Pinned to version 0.17.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http papertax https://papertax.xyz/mcp
claude mcp add --transport http papertax https://papertax.xyz/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__papertax__get_tax_summary",
      "mcp__papertax__explain_tax_treatment"
    ],
    "ask": [
      "mcp__papertax__get_ledger_events",
      "mcp__papertax__export_tax_file",
      "mcp__papertax__create_verified_pnl",
      "mcp__papertax__buy_report"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as papertax. Review it before you use it.

Capability tags behind 5 rules
  • mcp__papertax__get_tax_summary untrusted-input
  • mcp__papertax__get_ledger_events private-data, untrusted-input
  • mcp__papertax__export_tax_file untrusted-input
  • mcp__papertax__create_verified_pnl untrusted-input
  • mcp__papertax__buy_report untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.AwakeWeb3/papertax/verify?hash=cfcf5ccd8fc94993636bc8335b402de565128f770b293d8c1e0fcae7643cdc10" | jq -e '.changed == false'

Pinned hash cfcf5ccd8fc9, from Oct 26, 2026, 09:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.AwakeWeb3/papertax/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.AwakeWeb3/papertax
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.AwakeWeb3/papertax.svg)](https://radar.anlyon.com/servers/io.github.AwakeWeb3/papertax)

Source: MCP Registry. Synced Oct 26, 2026, 09:17 UTC.

papertax MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the papertax MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 4 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the papertax MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the papertax MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the papertax MCP server have?

6 tools: 4 write, 2 read. get_ledger_events, export_tax_file, create_verified_pnl, buy_report, get_tax_summary and explain_tax_treatment.

Does the papertax MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the papertax MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the papertax MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Oct 26, 2026. Every change is on this page and in its Atom feed.