Skip to content

Bitstore exchange MCP server

pro.bitstore/exchangebitstore.prostreamable-httpv1.0.0Scanned

Crypto and fiat exchange rates, limits and ready exchange links on bitstore.pro.

5 tools: 1 change things and 4 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Bitstore exchange MCP server can do

The Bitstore exchange MCP server is published by bitstore.pro, a domain the MCP Registry verified. It has 5 tools. It can create or change data (1 tool: about_exchange), but cannot delete data. 4 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 9, 2026, version 1.0.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.

5 tools

Changes things 1Claude Code: ask
  • about_exchangeThe exchange itself: the site, terms, support, and the independent monitors and review sites listing it (its rating and reviews are there).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    The exchange itself: the site, terms, support, and the independent monitors and review sites listing it (its rating and reviews are there).

    Annotations the server declares

    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
Only reads 4Show 4 read-only tools
  • get_quoteA quote for an exchange and the link to make it on the site.No findings

    Why it is in this group

    • The name "get_quote" says "get": a word for reading.
    Description, as the server wrote it
    A quote for an exchange and the link to make it on the site. `give` and `receive` are method codes; `amount` is what the client gives (amount_side="give") or wants to receive (amount_side="receive"). Returns both amounts, the rate, the limits, the requisites the site will ask for and `exchange_link`: the site's exchange form with all this filled in, where the person enters the e-mail and requisites and creates the bid.

    Annotations the server declares

    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • get_reservesHow much of each currency the exchange can pay out now (by currency, then method).No findings

    Why it is in this group

    • The name "get_reserves" says "get": a word for reading.
    Description, as the server wrote it
    How much of each currency the exchange can pay out now (by currency, then method).

    Annotations the server declares

    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • list_pay_methodsPay methods of the exchange: what the client can give (pay with) and receive.No findings

    Why it is in this group

    • The name "list_pay_methods" says "list": a word for reading.
    Description, as the server wrote it
    Pay methods of the exchange: what the client can give (pay with) and receive. Each method has a `code` used by the other tools. `search` filters by name, currency, code or network (e.g. "USDT", "Monobank", "TRC20").

    Annotations the server declares

    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • list_receive_optionsWhat the client can receive for the method they give (by its `code`).No findings

    Why it is in this group

    • The name "list_receive_options" says "list": a word for reading.
    Description, as the server wrote it
    What the client can receive for the method they give (by its `code`).

    Annotations the server declares

    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: 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 private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
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.

Tools listed without sign-in

Looked at Nov 16, 2026, 14:23 UTC, unchanged since Oct 25, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
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
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://bitstore.pro/mcp: tools/list returned 5 tools to an anonymous client, including about_exchange (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

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

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

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

claude mcp add --transport http exchange https://bitstore.pro/mcp
claude mcp add --transport http exchange https://bitstore.pro/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__exchange__list_pay_methods",
      "mcp__exchange__list_receive_options",
      "mcp__exchange__get_quote",
      "mcp__exchange__get_reserves"
    ],
    "ask": [
      "mcp__exchange__about_exchange"
    ],
    "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 exchange. Review it before you use it.

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/pro.bitstore/exchange/verify?hash=be245cae3a45779403332869c93994d6445d2b424dd21b939442cbf3312c5e01" | jq -e '.changed == false'

Pinned hash be245cae3a45, from Nov 9, 2026, 02:18 UTC.

Watch

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

https://radar.anlyon.com/servers/pro.bitstore/exchange/changes.xml

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

Badge

Anlyon Radar badge for pro.bitstore/exchange
[![Anlyon Radar](https://radar.anlyon.com/badge/pro.bitstore/exchange.svg)](https://radar.anlyon.com/servers/pro.bitstore/exchange)

Source: MCP Registry. Synced Oct 24, 2026, 20:20 UTC.

Bitstore exchange MCP server: questions and answers

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

Is the Bitstore exchange MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 1 of which can change, send or delete something, and 0 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 Bitstore exchange MCP server delete data?

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

Can the Bitstore exchange 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 Bitstore exchange MCP server have?

5 tools: 1 write, 4 read. about_exchange, list_pay_methods, list_receive_options, get_quote and get_reserves.

Does the Bitstore exchange MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Bitstore exchange MCP server send data to outside services?

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

Has the Bitstore exchange MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 9, 2026.