原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

tidex6 — private payments on Solana

作者:koshak01版本 2.18.0i★ 1i在你的电脑上运行官方网站 ↗
注册名称io.github.koshak01/tidex6-mcp-local

安装方法

What it does

Private USDC/USDT payments on Solana: hidden amounts, unlinkable, optional auditor.

  • Connects 在你的电脑上运行
  • Account or key No key needed
  • Category 加密货币与区块链

为什么排在这里

列表按使用分(满分 100)排序,由以下部分组成

热度4/80GitHub 星标或每周下载量:较大的计 60,较小的计 20
新鲜度12/1230 天内有发布或代码更新得满分
仍在响应0/8上次检查时云端端点有响应
使用分16/100

质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)

安装

选择你使用的 AI 应用,然后复制设置。

通过 3/3 项检查 · 在你的电脑上运行

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

Claude 暂时无法连接 tidex6 — private payments on Solana

开发者尚未在 MCP 注册表中填写安装方式

ChatGPT 暂时无法连接 tidex6 — private payments on Solana

开发者尚未在 MCP 注册表中填写安装方式

你可以改用这些方式

B · 加密货币与区块链 类中能连接 ChatGPT 的其他服务器

从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的

Claude Code 暂时无法连接 tidex6 — private payments on Solana

开发者尚未在 MCP 注册表中填写安装方式

Cursor 暂时无法连接 tidex6 — private payments on Solana

开发者尚未在 MCP 注册表中填写安装方式

VS Code 暂时无法连接 tidex6 — private payments on Solana

开发者尚未在 MCP 注册表中填写安装方式

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 tidex6 — private payments on Solana 的人💬 讨论 →

一览

每周下载量i
不在 npm/PyPI 上
许可证i
Apache-2.0
连接方式
在你的电脑上运行
最新版本i
2.18.0
发布到注册中心i
2026年8月6日
代码最后更新i
2026年10月30日
作者
koshak01
软件包
cargo: tidex6-mcp-local
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

在你的电脑上运行,适用于

GooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

全部应用及其优缺点 →

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 koshak01 验证,该账户拥有此仓库

  • ✓ 通过

    仍在维护

    代码最后更新于20天前

  • ✓ 通过

    有许可证

    使用 Apache-2.0

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

已公开的漏洞(OSV.dev)

未检查:只能检查标明版本的 npm 和 PyPI 包

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/koshak01-tidex6-mcp-local.svg)](https://mcp.popnx.com/en/servers/koshak01-tidex6-mcp-local)

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

与“加密货币与区块链”中的其他服务器比较i

  • 星标数多于此分类中其他 1759 个服务器的 84%
  • 发布到注册中心的时间比此分类中其他 1759 个服务器的 30% 更新
  • 基础检查结果等于或优于此分类中其他 1759 个服务器的 99%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

tidex6 — private payments on Solana 安全吗?

它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于20天前,最新版本(2.18.0)于3个月前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Rust。

有什么可以替代它?

同一分类中有:DexSQL, PayRam, DexPaprika, Alchemy MCP Server, X402 List MCP

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

DexSQL

SQL for Android APK and DEX files: classes, methods, strings, references and smali.

作者:LSPosed正在增长★ 32032天前更新

在你的电脑上运行✓ lsposed.org

PayRam

Install, configure, operate and integrate self-hosted PayRam crypto payment gateways.

作者:PayRam正在增长★ 15843天前更新

在云端运行✓ 服务方 · payram.com

DexPaprika

DEX and on-chain data: liquidity pools, token prices, swaps, and trading volume.

作者:coinpaprika正在增长★ 1206天前更新

在云端运行✓ 服务方 · dexpaprika.com

X402 List MCP

Find and vet x402 payment APIs before your agent pays one: uptime, price, on-chain volume.

作者:mcccsm起步阶段↓ 80/周★ 1840天前更新

电脑或云端✓ 服务方 · x402-list.com
与相似项目对比
本项
tidex6 — private payments on Solana
DexSQLPayRamDexPaprikaAlchemy MCP ServerX402 List MCP
运行位置需要安装在电脑上需要安装在电脑上在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装云端或安装在电脑上都可以
需要密钥否否否否否否
可在 Claude 中按 + 添加否否否否否否
基础检查3/32/33/44/44/45/5
许可证Apache-2.0NOASSERTION–MITMITMIT
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

tidex6

I grant access, not permission.

Private stablecoin payments with disclosure by consent — one Rust codebase, live on Solana mainnet, on Arc and on EVM chains.


tidex6 is a Rust-native, open-source framework that lets Solana developers add full transaction privacy to their Anchor programs through a small SDK surface. Transactions are private by default — sender, receiver, and amount are hidden. Privacy comes in two layers: a Groth16 shielded pool hides the *link* between sender and receiver, and a Token-2022 Confidential Transfers layer (wUSDC / wUSDT hidden-amount pools, live on mainnet and devnet) hides the *amount* itself. Users can optionally share a viewing key with someone they trust (an accountant, an auditor, a family member) to selectively disclose history, on their own terms.

Status: full MVP product stack live on Solana mainnet. The privacy-core verifier program at CSDD31Zmm3pRMHAMB8c3TBqsj9mbmH2rXBzV7jrsJhcd is OtterSec-verified and immutable (upgrade authority renounced). The full feature stack — deposit, ZK withdraw (Groth16 WithdrawCircuit<20> verified via alt_bn128 syscalls), per-nullifier double-spend PDA, recipient-binding front-run protection, unlinkable withdraw via reference relayer at relayer.tidex6.com, opaque hex notes + post-quantum ML-KEM-768 encrypted memos in a dedicated on-chain account, stealth payments (the recipient is never handed the note — they scan the chain with their own ML-KEM secret) and per-deposit revoke, client-side proof generation in the browser via WebAssembly (tidex6-prover-wasm, ~1.7 s per proof, secret never leaves the user's tab), user-facing tidex6 CLI, tidex6-client SDK, web app at tidex6.com, the flagship examples/private-payroll three-binary demo, and a third-party CPI integration example (tidex6-tip-jar, ~30 lines of Rust to add privacy to any Anchor program — deployed and OtterSec-verified on mainnet at 5WohQRRzC31SkFMSWgEqJC9p2KvNhGkQbzUSsNUi9b9x in April 2026, demo deployment since closed) — all validated end-to-end on mainnet. MVP shipped for the Colosseum Frontier hackathon (2026-05-11); development continues — since then the hidden-amount pools (Token-2022 Confidential Transfers, wUSDC AYTRKmF8VBdqRWGZr9c6Mx582SRm2tbUEwMesFMhcPcU and wUSDT QGPYpwyMnWhJUPGieXyJU5jhAkKsKuU7iGN53VCWPz2), a configurable per-operation fee paid on top by the sender and collected privately as a stealth note (ADR-016), and the live public trusted-setup ceremony at ceremony.tidex6.com (ADR-017) have shipped.

DEVELOPMENT ONLY. Pre-audit, single-contributor trusted setup, hackathon-grade trust assumptions. Verifier upgrade-authority has been renounced with solana program set-upgrade-authority --final — the program is immutable. Do not use to secure real funds. A public multi-party trusted-setup ceremony is live at ceremony.tidex6.com (publicly verifiable transcript, see CEREMONY.md); the on-chain VK is replaced only when the ceremony finalizes and a fresh immutable verifier ships. See docs/release/security.md.


The same circuit off Solana — Arc and the EVM chains

Solana is where this started and where the deepest integration lives, but the proof system is not tied to it. The same Groth16 circuit and the same verifying key run unchanged on EVM chains through a Solidity verifier and a Solidity Poseidon (contracts/), against a hidden-amount pool where the value sits inside the commitment rather than next to it. One rail, not one protocol per chain.

Arc — Circle's chain, where the loop closes. The contracts needed no modification: Arc's BN254 precompiles (0x05–0x08) were checked live before deploying. Six contracts on chain 5042, deployed 18 September 2026:

contractaddress
HiddenPool (sealed amounts)0x28fbB1500875EaEbe303D195C1a3721BBed8AF5f
Pool (fixed denomination)0x8eb05Cb1b5E46e58C8ca91E3A3738CF534c1E74f
Groth16 Verifier0x2c94135FB49840a0D6e0985AB1A6c48EE6c140d6
HiddenWithdrawVerifier0x6fF8E8393F0dD9D2592332e9f9adC3232FC41786
HiddenTransferVerifier0xca4fECF177dBb1025CC64B3D3618AdfA2f44D7AD
Reader-key Registry0x6F6F07e14E8381D13D01f99867985D8c7D23E914

The same addresses exist on Arc Testnet (chain 5042002) — same deployer, same nonces — and testnet is the place to put hands on it: faucet at faucet.circle.com, flow identical to mainnet.

What makes Arc more than another deployment target: gas there is USDC, the same token the pools move and the same token the fee is charged in. Everywhere else, a service paying its own running costs out of its own revenue has to convert one asset into another — on Solana the fee is swapped to SOL through an aggregator when the operator's balance falls under a threshold (crates/tidex6-ct-lab/src/gas.rs). On Arc there is nothing to convert: fee in USDC, gas in USDC, no swap, no price risk, no third party. On the remaining EVM chains that loop is still open — fee in USDC, gas in ETH or HYPE — and closing it is the next piece of work.

How the fee works and what it costs, including the parts that do not work yet, is written out in docs/release/BUSINESS.md.

Arbitrum — where the contracts are Rust rather than Solidity. The same pool is compiled to WASM and runs on Stylus (stylus/), on two chains: Arbitrum Sepolia and Robinhood Chain, an Orbit chain whose token is a tokenized stock. Every contract is a reproducible Docker build and cargo stylus verify passes on both networks, constructor included.

contractArbitrum SepoliaRobinhood Chain
hidden-pool (USDC / TSLA)0xe4c1f2bc121800b8e56ff11dced9a62d6ce3b3830xf4029451b6988d32ed1a9de847bf3250e83a87fe
hidden-pool (USDG)0x27ee24bea73088095b2898b3098e2b60405152750x73f68e1e4d02557e6cefd0292ffac13da5d18490
hidden-withdraw-verifier0xe00eca003e40bb3f2df30c5b7111c73cff9d0b000x6f6c5b8e4b2f637aa7c7c47eb90c73bc18c5008d
hidden-transfer-verifier0x5024f1348dccb7f612cf0f5dc08de81b99c3fbb80xeb8cfac5351089d9436fc9fc3a40c93f1aa282f4
poseidon0x3454f4bb9b3bb20344bbb3cb43d6fb743a1c1d680xe9182c3b0cdf5bfb8871ac162fa28a501a3cfa82

Three tokens move through these pools, and the point is that the pool does not care which: USDC, TSLA — a tokenized stock, so a salary or an invoice can be paid in equity without publishing what anyone is paid — and USDG, Paxos's dollar, added 22 September 2026 on both chains. A second token is a second pool sharing the first one's verifiers: the proof is about the tree and the nullifier and carries no signal about which token is inside.

Poseidon is what makes this worth doing in Rust: a depth-20 tree walk hashes twenty times per deposit, and in Solidity one hash costs around 63 000 gas (measured on our own deployment). On Stylus the constraint moves elsewhere — a contract must fit 24 KB after brotli, and Poseidon's 195 round constants do not compress — which is why the hash is a separate contract the pool calls. stylus/README.md has the sizes, the deployment gas and the reasoning.

The EVM, Arbitrum and Arc deployments carry the same caveat as Solana, and

one more: the verifying key comes from the ceremony still in progress, so

these pools are for review and testing, not for real money.


What works, what does not yet, and what we chose not to do

Judges and integrators ask these three questions anyway; the answers are better written down by us than discovered.

Works — and can be run by anyone:

  • Private stablecoin payments on Solana mainnet in wUSDC and wUSDT: the Groth16 pool hides who paid whom, Token-2022 Confidential Transfers hide the amount. The verifier is immutable (upgrade authority renounced).
  • The hidden-amount pool on Arbitrum Sepolia, Robinhood Chain, Base Sepolia, HyperEVM testnet, Arc testnet and Arc mainnet: send, receive and audit from the browser at tidex6.com; the relayer pays the gas, so the recipient's wallet never appears as the one that asked for the money.
  • USDG on Robinhood Chain: a full payment and withdrawal run live on 23 September 2026, fee note included.
  • USDG on Solana devnet through our confidential wrapper (wUSDG, pool GwZ55BcsK39KBmT3oh6jcWQpVm7EpC7p8rFNVWFUvN5U): a full send and receive run on 24 September 2026, and its fee note collected by the treasury robot.
  • The treasury: every payment's 1% fee is a separate note sealed to the treasury; robots on our server collect those notes on the EVM chains and on Solana, and top up the relayer's gas from the treasury. Which fees reached it, balances and every robot transaction are public at tidex6.com/treasury.
  • 51 contract tests (Foundry) run in CI on every push.

Does not work yet:

  • Deposit amounts on the EVM pools are public. Amounts inside the pool (join-split) are hidden; hiding them on the way in is the confidential token that comes next.
  • The verifying key is still a development key until the public ceremony at ceremony.tidex6.com closes. The pools are for review and testing.
  • USDG on Arbitrum Sepolia is deployed but not run end to end: the Paxos testnet faucet stopped paying out on that chain on 22 September 2026, so there is no test USDG to pay with.
  • No swap of fees into gas on the EVM testnets: there is no liquidity to swap against. On Arc none is needed — gas is USDC, the same money the fees arrive in.
  • USDG on Solana is on devnet only. The wUSDG wrapper and its pool (GwZ55BcsK39KBmT3oh6jcWQpVm7EpC7p8rFNVWFUvN5U) run on devnet since 23 September 2026; mainnet follows when there is demand for it — the deployment is the same, only paid for.
  • Solana fee amounts on the treasury page are as sealed in the note. On the EVM pools the amount is checked against the note's commitment; the Solana confidential pool's commitment does not carry the amount, so a note sealed to the treasury key could claim more than it holds. It could never be collected for more — only displayed.
  • On Solana the wrapper is custodial: the underlying USDC/USDT sits in a vault under the operator's key, and the operator sees the send side. A wrapper program with PDA authority is the next step.

Chosen not to do, and why:

  • No wallet screening yet. Nothing checks a wallet against sanctions lists or known-hack databases before it enables payments. The check belongs at Enable, where a wallet first registers; the method — an on-chain oracle where the chain has one, outside databases elsewhere — is not decided. It is not in the pool contracts, because deployed pools cannot be changed, and a check in the browser alone can be walked around.
  • The Solana verifier cannot be upgraded — by us either. New rules mean a new program at a new address that people choose to move to; nobody can change the rules under money already deposited.
  • Poseidon is a separate contract on Stylus. Its 195 round constants do not compress under the 24 KB brotli limit.
  • The Stylus pools have no `token()` getter. The relayer keeps each pool's token address in its ow

只显示了开头部分;其余内容请在仓库中阅读