We publish the tools we build for HiddenSwap as open source, on our GitHub account github.com/hiddenswap. Anyone can use them, read the code and suggest changes. Code is under the MIT license and data under CC BY 4.0.
HiddenSwap MCP
github.com/hiddenswap/hiddenswap-mcp
Connects AI assistants such as Claude, Cursor and VS Code to HiddenSwap through the Model Context Protocol. An assistant can find coins, get a live swap estimate, check whether two coins can be swapped and follow an order by its ID. It is read-only: it never starts a swap and never asks for an address. When someone wants to swap, it hands over a link to the swap page.
- Remote server: https://hiddenswap.com/mcp, with no install and no API key.
- In Claude Code:
claude mcp add --transport http hiddenswap https://hiddenswap.com/mcp - The repository also has setup examples for other assistants, a bridge for assistants that only run local servers, and a small command-line tool:
npx -y github:hiddenswap/hiddenswap-mcp quote btc xmr 0.1
Crypto address checker
github.com/hiddenswap/crypto-address
A TypeScript library that checks the format and checksum of a crypto address offline, with no network calls. It covers Bitcoin (including Taproot), Litecoin, Ethereum and every EVM chain, Tron, Monero (standard addresses, subaddresses and integrated addresses) and Solana. For Zcash it reads transparent, Sapling and TEX addresses, and it opens unified addresses to list the receivers inside them.
It also reads payment links such as bitcoin:, monero: and zcash:, and compares two addresses to catch a look-alike that shares the first and last characters of the real one. Its Zcash payment request parser follows every rule of ZIP 321 and passes all 51 cases of the shared ZIP 321 test set used by the Rust, Swift and Kotlin libraries. It is also tested against the official Zcash address vectors and published Bitcoin and Ethereum examples.
It checks format and checksum only. It cannot tell who controls an address. You can try it on our crypto address checker, which runs it in your browser.
Stablecoin contract addresses
github.com/hiddenswap/token-contracts
An open list of the official USDT and USDC contract addresses on 18 networks, as JSON: 28 entries, from Ethereum, Tron, Solana and TON to BNB Smart Chain, Polygon, Arbitrum and Base. Each entry has its decimals, whether the token is issued by Tether or Circle or bridged by a third party, whether it is still active, and the date it was last checked. Every address was checked on the issuer’s own page (or the bridge documentation for bridged tokens) and on the chain itself. Sending tokens under the wrong contract or network is one of the most common ways to lose them, so the list is meant to be copied into wallets, apps and guides.
Memo and destination tag rules
github.com/hiddenswap/memo-tags
Which crypto networks need a memo, destination tag or comment when you deposit to an exchange or a swap service, what each network calls the field, which values it accepts, and what happens when it is left out. It covers 32 networks, from XRP, Stellar, TON and the Cosmos chains to Bitcoin, Ethereum and Solana, which need none. Every entry links the network’s own documentation, specification or source code. It comes with a small JavaScript library that tells whether a network needs a memo and checks a memo value. The same rules are on our memo and destination tag page.
Monero address test vectors
github.com/hiddenswap/monero-address-vectors
A public-domain JSON file of Monero addresses for testing address parsers in any language: 75 valid standard addresses, subaddresses and integrated addresses on mainnet, testnet and stagenet, with the keys and payment IDs inside them, and 19 invalid ones labelled with the reason they must be refused. Every valid address is derived from published test keys, and the generator refuses to run unless it reproduces the addresses in Monero’s own functional tests. Writing them turned up a check most validators skip: an address whose checksum is right but whose keys are not valid curve points, which Monero wallets refuse.
Monero FCMP++ tracker
hiddenswap.com/monero-fcmp-upgrade
Open data on Monero’s FCMP++ upgrade: whether it is live, the planned schedule and its sources, what changes for wallets and merchants, and which of 42 wallets, libraries, explorers, payment tools and hardware wallets support it. Every status needs a dated primary source; without one a project stays at “no statement”. The data is published as JSON under CC BY 4.0.
Using and contributing
- Each repository has its own README with examples and tests.
- Report a problem or suggest a change with an issue on GitHub.
- If you reuse the contract list or the memo rules, the CC BY 4.0 license asks you to credit HiddenSwap with a link to this page.