ADEXTO MCP server
Commit Oct 7, 2026Enables AI agents to launch, buy, stake, and claim bonding-curve token markets across multiple blockchain networks using their own keys.
Also known as 0xcuy/adexto
- Stars
- 2
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 1.1.0
- Last commit
- Oct 7, 2026
- License
- —
What is ADEXTO MCP?
ADEXTO enables AI agents to launch, buy, stake, and claim bonding-curve token markets across multiple blockchain networks using their own keys.
Summary generated from the project's README
About ADEXTO MCP server
AI agents can manage bonding-curve token markets across multiple blockchain networks using this infrastructure. The system allows agents to launch, buy, stake, and claim markets on networks including Monad, Arbitrum One, Robinhood Chain, Base, 0G, and Arc. By using the MCP server with their own private keys, agents can interact with 14 specific tools to automate market creation and participation without needing a human intermediary.
Agents that open a market through the prepare_launch and register_launch workflow can earn a fixed share of every trade. The protocol uses ERC-8004 identity binding to ensure that only the owner of an agent ID can deploy a market for that identity. Because the terms are fixed in bytecode with no admin keys, the fee structures and treasury settings cannot be changed by any central authority. This setup enables an autonomous agent economy where markets are bound to on-chain identities and can be acquired by other agents using USDC on Base via the x402 gateway.
What you can do with it
- 1Automated market deploymentAn AI agent can prepare and register a new bonding-curve token market using its own identity.
- 2Cross-chain token acquisitionAn agent can purchase tokens on one chain by paying with USDC on the Base network.
- 3Autonomous revenue collectionThe creator of a market can claim their fixed share of trading fees in the native asset of the chain.
Written from the project's README. Every use case is checked against a quote from it.
How to install ADEXTO MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall ADEXTO MCP in Claude Code
$ claude mcp add --transport http adexto https://adexto.xyz/api/mcpInstall ADEXTO MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"adexto": {
"url": "https://adexto.xyz/api/mcp"
}
}
}Install ADEXTO MCP in VS Code
.vscode/mcp.json
{
"servers": {
"adexto": {
"type": "http",
"url": "https://adexto.xyz/api/mcp"
}
}
}Install ADEXTO MCP in VS Code CLI
$ code --add-mcp '{"name":"adexto","type":"http","url":"https://adexto.xyz/api/mcp"}'Install ADEXTO MCP in Codex
$ codex mcp add adexto --url https://adexto.xyz/api/mcpInstall ADEXTO MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.adexto] url = "https://adexto.xyz/api/mcp"
Install ADEXTO MCP in Gemini CLI
$ gemini mcp add -s user --transport http adexto https://adexto.xyz/api/mcpInstall ADEXTO MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"adexto": {
"url": "https://adexto.xyz/api/mcp",
"type": "http"
}
}
}Automated checks
Ran Nov 15, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachable0xcuy/adexto is public and reachablegithub.com/0xcuy/adexto ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)No licenseFinding
- Commit or release in the last yearLast commit or release 2026-10-07github.com/0xcuy/adexto ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeinitialize answered with protocol 2025-06-18 in 705 msPass
README
View on GitHubThe loop
| What happens | Read it on chain | |
|---|---|---|
| Open | An agent calls deployTrinity with its ERC-8004 agentId, and the factory refuses unless ownerOf(agentId) is the caller. Nothing is deposited: the token opens inside a bonding curve against a virtual reserve, with 100% of supply in the curve. |
agentIdOf(token), AgentBound |
| Earn | The launching address is the curve's immutable creator and takes a fixed share of every trade, claimable in the chain's native asset. |
creatorOwed(), claimCreatorFees() |
| Get bought | Another agent finds the market over MCP, receives an HTTP 402 quote, and pays USDC on Base by signing an EIP-3009 authorization with its own wallet. The token is delivered on the market's chain before the payment settles. | buy_token at adexto.xyz/api/mcp |
| Verify | Fees, treasury and supply are readable before anyone trades, and there is no owner, proxy, pause or withdraw function. | totalFeeBps(), protocolTreasury() |
Launchpads are built for people clicking buttons. An agent needs a market it can open without asking anyone, terms it can check without trusting anyone, and buyers who can pay it without a bridge. It opens one with a direct contract call, or over MCP: prepare_launch returns the unsigned transaction, the agent signs and sends it with its own key, and register_launch lists the market.
Live on six mainnets
One factory, byte-identical on every chain (21,806 bytes, an exact match on Sourcify on all six), and every new launch goes through it.
The 12 listed markets, read from chain on 2026-10-04 (SAi Arc on 2026-10-06). The same ticker on two chains names two separate markets, with separate supply and price.
| Market | Chain | Generation · trader pays | ERC-8004 agent | Contracts |
|---|---|---|---|---|
| $PARCEL Parcel Market | Monad | 0.11.0 · 0.40% |
10251 |
token · curve |
| $SAI SAi Monad | Monad | v1 · 1.00% | 10275 |
token · curve |
| $LOOP Loop | Monad | v1 · 1.00% | 10276 |
token · curve |
| $WOMBO Wombo | Arbitrum One | 0.11.0 · 0.40% |
none | token · curve |
| $SAI SAi Arbitrum | Arbitrum One | v1 · 1.00% | 1566 |
token · curve |
| $LOOP Loop | Arbitrum One | v1 · 1.00% | 1578 |
token · curve |
| $SAI SAi Robin | Robinhood Chain | v1 · 1.00% | 6525 |
token · curve |
| $SAI SAi Arc | Arc | v1 · 1.00% | 1421 |
token · curve |
| $BLOOP Bloop | Base | 0.11.0 · 0.40% |
none | token · curve |
| $ADEXTO ADEXTO | 0G | 0.11.0 · 0.40% |
none (why) | token · curve |
| $ADT ADEXTO Protocol | 0G | 0.11.0 · 0.40% |
none | token · curve |
| $ZEEBO Zeebo | 0G | 0.11.0 · 0.40% |
none | token · curve |
"Trader pays" is the curve's own totalFeeBps(): 40 on every 0.11.0 curve and 100 on every v1 curve. Factory, stake and hub addresses for every chain are in Mainnet deployments.
| Repository | What lives there |
|---|---|
0xcuy/adexto (this one) |
contracts, tests, the web app, the MCP server's source, the x402 gateway and the indexers |
0xcuy/adexto-mcp |
MCP connection guides, the tool reference, and an agent kit that signs with your own key |
0xcuy/adexto-arbitrum |
the Arbitrum One engineering |
0xcuy/adexto-monad |
the Monad engineering |
0xcuy/adexto-arc |
the Arc engineering: what is different on Arc, the go-live log, a read-only probe, and the demo video |
Architecture
Three ways in, one set of contracts. People use the web app with their own wallet, AI agents use the MCP server with their own key, and any HTTP client can buy over x402 with USDC on Base. Every launch, stake and claim is signed by the user's own key: the web app and the MCP server prepare those transactions and never hold that key. The x402 gateway buys on the market's chain with its own relayer key and the payer as recipient, and only after that delivery does it submit the payer's USDC authorization on Base.
[!NOTE] What we run, and what we don't. The web app and the MCP server (Next.js, this repo), the x402 gateway (a Cloudflare Worker in
cloudflare-worker/) and the market index are ours, off-chain. On chain nothing has an owner: no factory, curve, token or stake contract has an admin key. The ERC-8004 Identity Registry, USDC, 0G DA, the 0G Compute router and the indexers belong to third parties.
Start here
Explorer lists every market on every chain, and /creator shows what any address has earned. To run it yourself, see Local development.
Connect an agent
claude mcp add --transport http adexto https://adexto.xyz/api/mcp
{ "mcpServers": { "adexto": { "url": "https://adexto.xyz/api/mcp" } } }
Fourteen tools: discover and quote markets, buy with USDC on Base, read trade history and stakes, ask a market's agent, and launch, stake and claim with your own key. Guides for other clients and the agent kit are in 0xcuy/adexto-mcp.
Buy over x402
curl -i 'https://x402.adexto.xyz/v1/x402/buy/loop?chain=143'
Sign the EIP-3009 authorization it describes and send the request again. The curve on the market's own chain delivers to your address, and only then is the payment settled. Reference: adexto.xyz/x402 and the OpenAPI document.
What arrives with a market
A launchpad hands a creator a token and a page. Here one transaction opens a working venue, whether an agent or a person sends it, and all of this arrives with it. None of it is a roadmap item, and none of it needs a listing or an application.
[!NOTE] What is not here: no autonomous trading bot runs a market on a creator's behalf. ERC-8004 identity binding is real and checked on-chain at launch, but it is opt-in, and it records an identity rather than starting a strategy.
How the market works
The token opens inside a bonding curve against a virtual reserve. There is nothing to seed, so a launch costs gas and nothing else. 100% of supply enters the curve, so the creator holds no allocation to sell. Income arrives instead as a share of every swap, taken from inside the fee the trader already pays: on the studio's standard preset a trade costs 1.00%, and 0.70% of it goes to the creator.
The curve is the permanent venue. There is no graduation step and no migration into an external pool, which is where most launchpad exploits have happened. There is no withdrawal function anywhere in the curve, so nobody, including us, can drain a market.
That is a statement about the protocol, not a restriction on the token. A v1 AdextoToken limits every receiving wallet to 1% of supply only while block.timestamp < launchTime + 180 (the six 0.11.0 tokens capped single transfers for their first 5 blocks). After that, _update adds no condition at all, and there is no blacklist, no pause, no Ownable and no permanent transfer hook. It is a plain ERC-20, so anyone can list it on any external AMM without our permission, and we could not stop it. The guarantee is narrower than "one market": we never migrate, and nobody can withdraw the curve's reserves.
The reason is the launch model, and it is checkable in the contracts rather than a matter of taste.
| this curve | a standard liquidity pool | |
|---|---|---|
| Capital to open a market | none: the native side starts entirely virtual, and deployTrinity is not payable, so it cannot accept a deposit |
real liquidity must be deposited by someone |
| Creator's token position | none: the whole supply is minted to the factory and loaded into the curve in the same transaction, and the factory then requires its own balance to be zero before the launch can succeed | the creator must hold tokens to pair with liquidity |
| Can reserves be pulled out | no: there is no withdraw, rescue, sweep, drain or emergency function anywhere, no owner and no onlyOwner; native leaves only as a seller's payout or as a fee claim to an immutable address, the creator's on every curve plus the protocol's on 0.11.0 and v1 curves |
yes, and correctly so: a provider may withdraw at any time |
| Migration step | none: the curve is the permanent venue | the usual launchpad pattern graduates a curve into a pool, and that step is where much of the historical exploit surface lives |
| Creator fee | a share of every swap accrues on-chain inside the total the trader pays (0.70% of 1.00% on the studio's standard preset), so paying the creator costs the trader nothing extra | fees accrue to liquidity providers; paying a creator needs custom hook support the venue may not offer |
| Code paths across our six chains | one, byte-identical | whatever venue happens to exist per chain |
Row three carries the weight. A liquidity provider being able to withdraw is not a flaw, it is what an AMM is for, but it means the venue can be pulled out from under the people holding the token, and "we won't" is only a promise. Here the guarantee is the absence of code that could do it.
ADEXTO MCP questions
How do I add ADEXTO MCP to Claude Code?
Run claude mcp add --transport http adexto https://adexto.xyz/api/mcp in your terminal. Add --scope user to make it available in every project.
How do I add ADEXTO MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
How do AI agents interact with the protocol?
AI agents use the MCP server with their own key to perform actions like preparing launches and buying tokens.
Can the protocol administrators change the payment terms?
No, the terms are fixed in bytecode and there is no admin key, meaning nobody can change what an agent is paid.
Which chains support ADEXTO?
The protocol is live on Monad, Arbitrum One, Robinhood Chain, Base, 0G, and Arc.
How does the x402 gateway handle payments?
The gateway buys on the market's chain and only after delivery does it submit the payer's USDC authorization on Base.