Misaka (@Misaka_Prog) header
Misaka (@Misaka_Prog) profile picture

The MCP gateway that gives any AI careful hands on chain. 26 tools, 10 networks, Solana included. Reads free, your wallet signs.

Joined November 2026
Photo by Misaka (@Misaka_Prog)Photo by Misaka (@Misaka_Prog)Photo by Misaka (@Misaka_Prog)Photo by Misaka (@Misaka_Prog)Photo by Misaka (@Misaka_Prog)Photo by Misaka (@Misaka_Prog)Photo by Misaka (@Misaka_Prog)Photo by Misaka (@Misaka_Prog)Photo by Misaka (@Misaka_Prog)Photo by Misaka (@Misaka_Prog)
Demo : How works Misaka Prog. An AI asks for a SOL → USDC swap. The gateway quotes it on Jupiter, replays the exact transaction on live chain state, shows the balances before and after, flags what you should know, and hands it to your wallet unsigned. That is every action on Misaka Prog. misaka.life CA: 8rhMpKF6anKBeX9Hd4PuB8HQ8uNkV8HtNEKKWEMXo4pR
8
5
2
21
1,380
Update, week two. Where things stand. Live: 26 tools on ten networks, readable by any MCP client at 120 calls a minute, no account. Live: holder sessions. One signature, a tier read from your balance, more room. Live: the console on misaka.life takes a wallet, and the docs have a Holders section with the quotas. Published this week: the architecture, the signing model, the tier table, what a Prog and a watch look like, a real call and its real answer. Next on the board: the store that turns watches and Progs on. misaka.life CA: 8rhMpKF6anKBeX9Hd4PuB8HQ8uNkV8HtNEKKWEMXo4pR
2
5
56
Logs are the chain's own account of what happened. Raw, they are topics and data; decoded, they are sentences. get_events and get_transaction name the event, resolve the addresses, apply the token's decimals, and label spenders you should recognise, like Permit2. "Approval for an unlimited amount" is readable at a glance. 0xfff…fff is not.
3
5
79
A contract address is a wall of hex until something reads it for you. contract_info pulls the verified source, the ABI, the proxy behind the proxy, the owner, the functions that can pause or mint. Your AI reads that before you interact, and tells you in a paragraph what you would otherwise discover afterwards.
3
5
78
An MCP tool is a schema before it is a function. Each of the 26 tools declares its fields, their types and what they mean, so the model fills in a chain, an address and an amount instead of guessing at an API. Required fields are enforced, enums are closed, amounts are human units the gateway converts. The field that does not exist is the private key.
2
62
There is no users table. A holder session is a signed string your client carries in a header: who you are, which tier, until when, and an HMAC that makes it tamper-proof. The gateway can check it without looking anything up. Lose it, sign again. Sell your tokens, the next session reflects it. Stateless on purpose: nothing to breach, nothing to migrate.
3
57
Most "AI wallet" products ask you to hand over a key so the agent can act. Then the key sits on a server, and the server becomes the target. Misaka Prog keeps no key, so breaking into it yields nothing. Every transaction it prepares is unsigned until your own wallet signs it, on your device, after you have seen the simulation.
1
5
65
Before any swap is offered for signing, the gateway runs it against the chain as it is right now and reads every account it touches. You see the balances before and after, the route, the price impact, the fee, and anything odd, like a wrapped SOL account being closed along the way. If the numbers are not what you expected, you have not signed anything yet.
3
2
5
97
Good morning everyone, we still building and some updates come next days. "What is this wallet worth?" "Is it safe to send here?" "Swap one SOL to USDC." That is the whole interface. Your AI turns the sentence into a tool call, the gateway turns the call into reads, simulations and prepared transactions on ten networks, and the answer comes back in words. No SDK to learn, no RPC URL to paste, no ABI to find.
1
6
107
An AI that waits is an AI that costs. Polling a price with a language model means paying for every look. A Prog is the gateway doing the looking on a schedule, and calling your attention only when a step prepares something to sign. The model is back in the loop at the one moment it is useful.
3
4
178
Eight sentences the gateway can put in front of you. Each is attached to the prepared transaction it concerns, so an AI that shows you the transaction shows you the warning. The last one is not a warning so much as a wall: a simulation that reverts produces no signing link at all.
1
2
161
Eighteen programs the gateway knows by name. Jupiter, Raydium, Orca, Meteora, Pump.fun and PumpSwap, Phoenix, OpenBook, Magic Eden, Tensor, Marinade, Metaplex, the token programs. A history entry says "swapped on Raydium CLMM", not an address you would have to look up. Programs that publish an Anchor IDL get their instructions named as well.
4
4
181
Eight sentences the gateway can put in front of you. Each is attached to the prepared transaction it concerns, so an AI that shows you the transaction shows you the warning. The last one is not a warning so much as a wall: a simulation that reverts produces no signing link at all.
1
3
128
A real request and its real answer, unedited except for the shortening. The calldata is an approve. The spender decodes to Permit2, the amount to the maximum a uint256 can hold. Your AI gets that back in one round trip and can tell you: this approval is unlimited. No key, no wallet, no sign-up for a read like this.
1
92
What a Prog looks like, step by step. Read the SOL price. If it is under 120, prepare a swap of 2 SOL to USDC and deliver the signing link. Otherwise stop and write the run down. The value from step 1 flows into step 2 by name. Four steps here, six at most, each one an ordinary gateway tool.
1
79
Connecting a wallet costs one signature and moves nothing. The gateway hands you a short message with the time in it, your wallet signs it, the gateway checks the signature and reads your balance. There is no password to set and none to leak. The session lasts a day, then you sign again. CA: 8rhMpKF6anKBeX9Hd4PuB8HQ8uNkV8HtNEKKWEMXo4pR
1
1
3
101
The whole tier table, in one image. Reads are free at 120 a minute for anyone. Holding 10k $MISAKA opens watches and one Prog; 100k opens ten watches and five Progs every five minutes; 1M opens thirty and twenty, every minute. The tier comes from a signed message and a balance read on chain. Sell, and the next session reads the new balance.
1
2
84
Five steps, one dashed line. Prepare, simulate, review happen on the gateway. Sign and broadcast happen in your wallet. The dashed line between them is the whole security model: nothing crosses it except an unsigned transaction and a simulation you have already seen.
2
6
110
Three pieces, drawn once. Your AI client on the left, the gateway in the middle, ten networks on the right. The client speaks MCP, the gateway speaks to public nodes, Sourcify, DefiLlama, DexScreener and Jupiter, and gives back one schema whatever the network. The thing to notice is what is missing: there is no box for keys.
3
69
Update, one week after launch. · $MISAKA is live on Solana; the contract address sits under the hero on misaka.life and links to Solscan. · 26 tools now, up from 19: decoded history, pools, Jupiter swaps, close empty accounts, connect, watch, prog. · Holder tiers: sign one message, get a session, get more room. No account. · The console takes a wallet now, so holder calls can be tried from the browser. · Docs have a Holders section with the tiers and the quotas. Next on the board: the store that turns watches and Progs on. misaka.life CA: 8rhMpKF6anKBeX9Hd4PuB8HQ8uNkV8HtNEKKWEMXo4pR
1
2
4
139
The name comes from the thing we wanted to exist: a routine your AI writes once, that keeps running without the AI having to be awake. Read a price, compare, prepare a trade, deliver a signing link. Every run recorded. The routine is the product; the token is how holders get to run more of them.
1
69