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

tw-crypto-data

https://tw-crypto-api.panda198271.workers.dev

Registry code: c886e60b8e6e6997

api record

台灣加密貨幣資料：165 涉詐網址比對、金管會合規業者名單、海外所得最低稅負試算、USDT 兌新台幣溢價紀錄。資料為繁體中文。

endpoint
https://tw-crypto-api.panda198271.workers.dev/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 tw-crypto-data live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is tw-crypto-data free to use?
Yes — the hub reached it with no key and no payment.
What tools does tw-crypto-data have?
4 tools: estimate_overseas_crypto_tax, list_registered_vasps, check_scam_domain, get_usdt_twd_premium.
Is tw-crypto-data 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 99.7%· all time 99.7%

latency
199ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 358 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
topic
crypto & onchain
used for
  • check if a url is a listed scam site
  • list registered crypto exchanges in taiwan
  • estimate taiwan tax on overseas crypto
  • get usdt to twd premium
takes → gives
text, data → data
tools
4 reads
_ 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 4 tools
2 open 2 never probed 2 of 4 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.

  • check_scam_domain reads open 17h ago

    比對台灣內政部警政署 165 公布之「遭停止解析涉詐網站」名單，判斷網址或網域是否被列入。查無不代表安全。

    mcp-tool

    {
  "type": "object",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "網址或網域，例如 https://example.com/login"
    }
  }
}
    arguments 12 lines
  • get_usdt_twd_premium reads open 17h ago

    取得 USDT 在台灣交易所（BitoPro、MAX）的新台幣價格，相對國際美元兌新台幣中價的最新溢價百分比與每日歷史紀錄。

    mcp-tool

    {
  "type": "object",
  "properties": {
    "days": {
      "type": "number",
      "description": "要回傳的歷史天數，預設 30，最多 730"
    }
  }
}
    arguments 9 lines
  • estimate_overseas_crypto_tax reads unknown never probed

    試算台灣個人海外所得（含海外交易所虛擬貨幣獲利）之最低稅負制基本稅額與應補繳金額（新台幣）。

    mcp-tool

    {
  "type": "object",
  "required": [
    "overseas_income",
    "net_income",
    "regular_tax"
  ],
  "properties": {
    "net_income": {
      "type": "number",
      "description": "綜合所得淨額（NT$）"
    },
    "other_items": {
      "type": "number",
      "description": "其他應計入基本所得額項目（NT$），預設 0"
    },
    "regular_tax": {
      "type": "number",
      "description": "一般所得稅應納稅額（NT$）"
    },
    "overseas_income": {
      "type": "number",
      "description": "全戶海外所得（NT$）"
    }
  }
}
    arguments 26 lines
  • list_registered_vasps reads unknown never probed

    列出台灣金管會公告完成洗錢防制登記的虛擬資產服務業者（公司、統編、品牌、服務類型），以及主要交易平台手續費。

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 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 c886e60b8e6e6997.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/c886e60b8e6e6997/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/c886e60b8e6e6997/badge.svg)](https://brick.blue/agent/c886e60b8e6e6997?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
80%

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.