_ registry / mcp streamable-http · checked 1h ago

cryptopeildatum

https://cryptopeildatum.nl

Registry code: 4bf1a7a60e522d29

api record

Crypto prices in EUR on the Dutch box 3 reference date (1 January 00:00 Dutch time) per exchange platform: Bitvavo, Coinbase, Kraken, Binance, Bitstamp and Crypto.com. Read-only, no account, nothing stored. Use search_coins when unsure of a ticker. Answers contain Dutch page URLs on cryptopeildatum.nl. Indication only, not tax advice.

endpoint
https://cryptopeildatum.nl/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is cryptopeildatum live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is cryptopeildatum free to use?
Yes — the hub reached it with no key and no payment.
What tools does cryptopeildatum have?
7 tools: compare_platforms, search_coins, get_reference_price, value_portfolio, price_history, estimate_box3, explain_box3.
Is cryptopeildatum safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
164ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 7 tools
1 open 6 never probed 1 of 7 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • explain_box3 open 1h ago

    Fixed, factual explanation (Dutch and English) of how crypto is valued for Dutch box 3: reference moment, which price to use, own wallets, actual return. With a link to the Belastingdienst. No amounts that change per year.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • compare_platforms unknown 1h ago

    All six platforms side by side for one coin on 1 January 00:00 Dutch time of the given year, with missing platforms marked and the spread between lowest and highest price.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "coin",
    "year"
  ],
  "properties": {
    "coin": {
      "type": "string",
      "maxLength": 80,
      "minLength": 1,
      "description": "Coin ticker, name or slug, case-insensitive, e.g. \"BTC\", \"bitcoin\", \"eth\", \"ripple\"."
    },
    "year": {
      "type": "integer",
      "maximum": 2100,
      "minimum": 2000,
      "description": "Reference year: prices on 1 January of this year (for the tax return over that year). Available: 2014–2026."
    }
  }
}
    arguments 22 lines
  • search_coins unknown never probed

    Find coins by ticker, name or slug; tolerant of case and partial input ("eth", "bitc", "ripple"). Returns ticker, name, slug, platforms with a price in the latest year and the coin page URL.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "maxLength": 80,
      "minLength": 1,
      "description": "Search text: ticker, (part of a) name or slug."
    }
  }
}
    arguments 15 lines
  • get_reference_price unknown never probed

    Price in EUR of one coin on 1 January 00:00 Dutch time (31 December 23:00 UTC) of the given year, per exchange platform. Omit platform to get all platforms. Includes candleTime and kind ("open" of that hour, or "close" of the last earlier hour) and the URL of the coin page.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "coin",
    "year"
  ],
  "properties": {
    "coin": {
      "type": "string",
      "maxLength": 80,
      "minLength": 1,
      "description": "Coin ticker, name or slug, case-insensitive, e.g. \"BTC\", \"bitcoin\", \"eth\", \"ripple\"."
    },
    "year": {
      "type": "integer",
      "maximum": 2100,
      "minimum": 2000,
      "description": "Reference year: prices on 1 January of this year (for the tax return over that year). Available: 2014–2026."
    },
    "platform": {
      "enum": [
        "bitvavo",
        "coinbase",
        "kraken",
        "binance",
        "bitstamp",
        "cryptocom"
      ],
      "type": "string",
      "description": "Exchange platform where the coins were held."
    }
  }
}
    arguments 34 lines
  • value_portfolio unknown never probed

    Value in EUR of a list of holdings on 1 January 00:00 Dutch time of the given year, using each holding's platform price. Returns value per line and the total. Lines without a price are marked missing and not counted. Also returns a link to the calculator. Nothing is stored.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "holdings",
    "year"
  ],
  "properties": {
    "year": {
      "type": "integer",
      "maximum": 2100,
      "minimum": 2000,
      "description": "Reference year: prices on 1 January of this year (for the tax return over that year). Available: 2014–2026."
    },
    "holdings": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "coin",
          "amount",
          "platform"
        ],
        "properties": {
          "coin": {
            "type": "string",
            "maxLength": 80,
            "minLength": 1,
            "description": "Coin ticker, name or slug, case-insensitive, e.g. \"BTC\", \"bitcoin\", \"eth\", \"ripple\"."
          },
          "amount": {
            "type": "number",
            "description": "Number of coins held on the reference date, e.g. 0.5.",
            "exclusiveMinimum": 0
          },
          "platform": {
            "enum": [
              "bitvavo",
              "coinbase",
              "kraken",
              "binance",
              "bitstamp",
              "cryptocom"
            ],
            "type": "string",
            "description": "Exchange platform where the coins were held."
          }
        }
      },
      "maxItems": 200,
      "minItems": 1,
      "description": "Holdings, one line per coin and platform. The same coin may appear on several platforms."
    }
  }
}
    arguments 55 lines
  • price_history unknown never probed

    Every reference-date price (1 January 00:00 Dutch time) of one coin since the first year with data, per platform, with the percentage change versus the previous year on the same platform.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "coin"
  ],
  "properties": {
    "coin": {
      "type": "string",
      "maxLength": 80,
      "minLength": 1,
      "description": "Coin ticker, name or slug, case-insensitive, e.g. \"BTC\", \"bitcoin\", \"eth\", \"ripple\"."
    }
  }
}
    arguments 15 lines
  • estimate_box3 unknown 1h ago

    Indication of Dutch box 3 tax on crypto only, for tax years 2025 and 2026: tax-free allowance (doubled with a fiscal partner) → base → fixed deemed return for "other assets" → tax at the box 3 rate. Give either cryptoValueEur (value on 1 January) or holdings (valued at the reference-date prices, like value_portfolio). Other assets, debts and savings are NOT included. Figures from belastingdienst.nl, sources in the answer. Indication only, not tax advice. Nothing is stored.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "year"
  ],
  "properties": {
    "year": {
      "type": "integer",
      "maximum": 2100,
      "minimum": 2000,
      "description": "Tax year; the value is taken on 1 January of this year."
    },
    "partner": {
      "type": "boolean",
      "description": "true if the person has a fiscal partner for the whole year (doubles the tax-free allowance). Default false."
    },
    "holdings": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "coin",
          "amount",
          "platform"
        ],
        "properties": {
          "coin": {
            "type": "string",
            "maxLength": 80,
            "minLength": 1,
            "description": "Coin ticker, name or slug, case-insensitive, e.g. \"BTC\", \"bitcoin\", \"eth\", \"ripple\"."
          },
          "amount": {
            "type": "number",
            "description": "Number of coins held on the reference date.",
            "exclusiveMinimum": 0
          },
          "platform": {
            "enum": [
              "bitvavo",
              "coinbase",
              "kraken",
              "binance",
              "bitstamp",
              "cryptocom"
            ],
            "type": "string",
            "description": "Exchange platform where the coins were held."
          }
        }
      },
      "maxItems": 200,
      "minItems": 1,
      "description": "Holdings to value first, one line per coin and platform. Use this or cryptoValueEur."
    },
    "cryptoValueEur": {
      "type": "number",
      "minimum": 0,
      "description": "Total value of the crypto in EUR on 1 January of the tax year. Use this or holdings."
    }
  }
}
    arguments 63 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 4bf1a7a60e522d29.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/4bf1a7a60e522d29/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/4bf1a7a60e522d29/badge.svg)](https://brick.blue/agent/4bf1a7a60e522d29?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.