
paired.exchange
io.github.nirholasv0.1.0Updated Sep 30, 2026
Launch coins quoted in tokenized stocks on Robinhood Chain; the user signs at a launch link.
Overview
Lets an assistant browse tokenized-stock markets, price trades, and prepare coin launches that the user signs in their own wallet.
- What it does
- A bridge to a hosted service for launching coins paired with tokenized stocks. Tools include plan_launch, which validates a coin and returns a launch link; launch_status, which reports whether a planned launch was signed; list_markets and list_coins for browsing; get_coin for price, curve and raise data; quote_trade for pricing buys and sells; and claimable_fees and fee_schedule for creator fees and live fee rates. The assistant can browse, price and plan, but cannot sign.
- When to use it
- Use it when you want an assistant to explore tokenized-stock markets, price a trade, or draft a coin launch and hand you a link to review and sign yourself. It is not for unattended or automated launches, since signing always happens in your own wallet.
- Requirements
- Either a remote MCP endpoint URL or the local npm package run over stdio with npx. The bridge accepts a PAIRED_MCP_URL environment variable to point at a different deployment; no authentication is declared. A wallet is needed only when you open the launch link and sign.
Installation
In SourceWeft
- Open paired.exchange in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"paired": {
"type": "http",
"url": "https://paired.exchange/mcp"
}
}
}README
clink-mcp
Launch coins paired with tokenized stocks on Robinhood Chain from any MCP client. This is a stdio bridge to the hosted clink.fun MCP server: tools are discovered from the server at startup, so the package never falls behind the live tool set.
The assistant can browse markets and coins, price trades and plan a launch.
It cannot sign. plan_launch returns a link; you open it, connect your own
wallet, review, and sign. Nothing is deployed or spent until you do.
Use it
Clients that take a remote URL (Claude on the web and desktop via Settings, Connectors, Add custom connector; Claude Code) do not need this package:
Clients that start servers over stdio:
CLINK_MCP_URL points the bridge at a different deployment.
Tools
Example
Launch a coin called Chip Dip, ticker CHIPS, 70% NVDA and 30% AMD, with this logo: https://example.com/chips.png
The assistant calls plan_launch, shows the summary and the link, and after
you sign, launch_status returns the coin address.
Source: packages/mcp/README.md at commit 822bd26
Tools
0Version history
1- v0.1.0LatestSep 30, 2026