Souvenir MCP server
finance.souvenir/coinssouvenir.financestreamable-httpv1.3.0Scanned
Souvenir prize coins on Solana: search coins and rounds, launch and trade coins, claim wins.
25 tools: 5 can delete or cancel things, 14 change things and 6 only read.
- Reads private data · 0
- Reads text others write · 11
- Can send data out · 2
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
5 tools here can delete or cancel things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Souvenir MCP server can do
The Souvenir MCP server is published by souvenir.finance, a domain the MCP Registry verified. It has 25 tools. It can delete or cancel things (5 tools: send_transaction, claim_sol, revoke_coin_key, set_coin_mode and 1 more) and create or change data (14 tools: sign_in_challenge, sign_in, launch_options, prepare_launch and 10 more). 6 tools only read.
11 tools bring in text other people can write (get_round, prepare_launch, submit_launch and 8 more); 2 tools can send data out of your system (send_transaction and create_coin_key).
The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 13, 2026, version 1.3.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
25 tools
Deletes or cancels 5Claude Code: deny
award_prizeA coin in prizes mode: gives winner an item, bought now from the coin's open pot at its fresh price plus a round's margin, as a round of the coin's: { round }.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it A coin in prizes mode: gives winner an item, bought now from the coin's open pot at its fresh price plus a round's margin, as a round of the coin's: { round }. item is an id from search_prizes. The same idempotencyKey again answers the same round, whatever changed since. Refused when the pot is short, the item can't be bought now, or the winner is one of the coin's pools, Souvenir's wallets or its creator. Takes a coin key from create_coin_key as coinKey or as the request's Authorization: Bearer ck_live_… header; it works for every coin its wallet created. Refused with "The coin API's keys and writes are not open yet." while they are not open.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
claim_solTakes a won prize's SOL instead of the prize now, as the prizes page does, through the site's own route for that kind of prize: its share of the prize's worth (my_wins solOffer: 75…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Takes a won prize's SOL instead of the prize now, as the prizes page does, through the site's own route for that kind of prize: its share of the prize's worth (my_wins solOffer: 75% for a skin or a case, 66% for most others, 60% for a store's piece), or an xStocks prize's full worth. Paid to your wallet within minutes. Final: the prize can't be claimed after. Only while the win waits for you and only where the site offers it; hold to claim applies (your wallet must still hold 90% of the coins that counted for the win). Answers { ok } (and bps, the share). Takes the token from sign_in (sign_in_challenge with your wallet's address, sign its message with the wallet, sign_in), as token or as the request's Authorization: Bearer header. Refused with "Wins through the API are not open yet." while they are not open to your wallet, as launching is.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
revoke_coin_keyEnds one of your coin keys now, as the coin page's Developers dialog does: { ok }.No findings
Why it is in this group
- The name "revoke_coin_key" says "revoke": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Ends one of your coin keys now, as the coin page's Developers dialog does: { ok }. It is refused from then on and its webhook stops; it can't be made live again. id is the key's id, as create_coin_key answered it (GET /api/v2/me/coinkeys lists your keys with their ids). Works whatever the coin API's switch, so a leaked key can always be ended. 404 for an id that is not one of your live keys. Takes the token from sign_in, as token or as the request's Authorization: Bearer header.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
send_transactionSends a transaction your wallet signed (base64, every signature in place) to Solana, as the site sends what a wallet signs: { signature }.Reads text others writeCan send data outNo findings
Why it is in this group
- The name "send_transaction" says "send": a word for sending, and what is sent cannot be taken back.
- The description says "can't be undone".
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe name "send_transaction" says "send": it sends or publishes something to other people.
Description, as the server wrote it Sends a transaction your wallet signed (base64, every signature in place) to Solana, as the site sends what a wallet signs: { signature }. Only one Souvenir built for you in the last few minutes (build_trade, or prepare_launch's devSwap), signed as it was built; any other is refused (not_built): send it through a Solana RPC. A trade can't be undone once it lands. With no answer from the network in time it may still land: its signature is answered the same. Trading a coin, in order: (1) quote_trade to see what you would get; (2) build_trade with your wallet's address; (3) sign the transaction it answers with your wallet; (4) send_transaction, or send it yourself through any Solana RPC. No sign-in: your wallet's signature is the approval, and Souvenir never needs its private key. The same fees and limits as the coin's page on souvenir.finance. An agent helping a person, which can't sign with their wallet, uses request_trade instead and gives them the link to approve it with their own wallet.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
set_coin_modeYour coin's mode from its next round (the round filling keeps its own): full (its rounds draw its prize), draws (each round pays drawSol in SOL to its winner) or prizes (you give p…No findings
Why it is in this group
- The name "set_coin_mode" says "set": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Your coin's mode from its next round (the round filling keeps its own): full (its rounds draw its prize), draws (each round pays drawSol in SOL to its winner) or prizes (you give prizes from its pot with award_prize; only a coin nobody but you holds can switch to it, has_holders otherwise). Answers the coin, as get_coin does. Takes a coin key from create_coin_key as coinKey or as the request's Authorization: Bearer ck_live_… header; it works for every coin its wallet created. Refused with "The coin API's keys and writes are not open yet." while they are not open.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
Changes things 14Claude Code: ask
build_tradeThe trade's transaction for your wallet to sign, as the coin's page builds it: { transaction, out, minOut }, the transaction base64 (unsigned, version 0, paid by your wallet).Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it The trade's transaction for your wallet to sign, as the coin's page builds it: { transaction, out, minOut }, the transaction base64 (unsigned, version 0, paid by your wallet). It changes nothing until your wallet signs it and it is sent. Trading a coin, in order: (1) quote_trade to see what you would get; (2) build_trade with your wallet's address; (3) sign the transaction it answers with your wallet; (4) send_transaction, or send it yourself through any Solana RPC. No sign-in: your wallet's signature is the approval, and Souvenir never needs its private key. The same fees and limits as the coin's page on souvenir.finance. An agent helping a person, which can't sign with their wallet, uses request_trade instead and gives them the link to approve it with their own wallet.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
create_coin_keyA coin key for the coins your wallet created, as the coin page's Developers dialog makes one: { key, id, webhookSecret, view }.Can send data outNo findings
Why it is in this group
- The name "create_coin_key" says "create": a word for a change.
What it can reach
- outboundThe input takes a URL (input.webhookUrl): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it A coin key for the coins your wallet created, as the coin page's Developers dialog makes one: { key, id, webhookSecret, view }. The key (ck_live_…) and the webhook secret are shown this once: keep them. It works for set_coin_mode and award_prize and the coin API (souvenir.finance/api/v2/openapi.json), on every coin the wallet created. At most 5 live keys a wallet; revoke one with revoke_coin_key (or DELETE /api/v2/me/coinkeys/{id}, or on the coin's page). Only a coin's creator makes keys. Takes the token from sign_in, as token or as the request's Authorization: Bearer header. Refused with "Coin keys are not open yet." while the coin API's keys are not open.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
launch_optionsWhat launching takes now for your wallet, as the site's launch form reads it: allowed and its reason, venues (meteora: Souvenir's own curve; pump: pump.fun), feeLevels and shareLev…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it What launching takes now for your wallet, as the site's launch form reads it: allowed and its reason, venues (meteora: Souvenir's own curve; pump: pump.fun), feeLevels and shareLevels in basis points, defaults, tickets (the ticket rules), holdHours, which prize kinds are open, basket, pump (pump.fun's fees; on BTC pairs its feeLevels, and shield and devBuy: whether the launch shield and a dev buy are open to you) and more. Takes the token from sign_in, as token or as the request's Authorization: Bearer header. Refused with "Launching through the API is not open yet." while it is not open to your wallet. Launching a coin, in order: (1) sign_in_challenge with your wallet's address, sign its message with that wallet, then sign_in for a token; (2) launch_options, and search_prizes for the prize; (3) prepare_launch; (4) sign the transaction it answers with your wallet, without sending it, and give it to submit_launch; (5) launch_status until it answers confirmed: a pump.fun launch first answers split with a second transaction, which you sign (or sign and send) and give to submit_split, then launch_status again. Your wallet pays and signs everything: Souvenir never needs or asks for its private key.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
launch_statusWhere your launch stands, as the site's page follows it: { status, mint } with status pending (ask again in a few seconds), split (a pump.fun launch landed: transaction is the seco…Reads text others write1 finding
Why it is in this group
- The name "launch_status" says "status": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "launch_status" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"openWorldHint":true}; The name "launch_status" says "status": a word for reading.
Description, as the server wrote it Where your launch stands, as the site's page follows it: { status, mint } with status pending (ask again in a few seconds), split (a pump.fun launch landed: transaction is the second approval, the split of its creator fee, for your wallet to sign; then submit_split), confirmed (the coin is on Souvenir) or failed (with reason). Takes the token from sign_in, as token or as the request's Authorization: Bearer header. Refused with "Launching through the API is not open yet." while it is not open to your wallet. Launching a coin, in order: (1) sign_in_challenge with your wallet's address, sign its message with that wallet, then sign_in for a token; (2) launch_options, and search_prizes for the prize; (3) prepare_launch; (4) sign the transaction it answers with your wallet, without sending it, and give it to submit_launch; (5) launch_status until it answers confirmed: a pump.fun launch first answers split with a second transaction, which you sign (or sign and send) and give to submit_split, then launch_status again. Your wallet pays and signs everything: Souvenir never needs or asks for its private key.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: true
my_winsYour wallet's wins, as the site's prizes page reads them: { wins, link, evmAddress }, the newest first.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Your wallet's wins, as the site's prizes page reads them: { wins, link, evmAddress }, the newest first. Each win: mint, symbol, number (its round), skin (the prize), state (drawn: waiting for you; buying, sent, delivered; owed_sol, paid_sol; forfeited), stateText, linkDeadline (claim by then), keep (the coins you must still hold to claim, raw units), and its kind's details (goods, gift, stars, trip, stock, nft, evm, offer, pack). solOffer, when not null, is what claim_sol pays: bps of its worth, and lamports. An xStocks prize (stock) not claimed yet can be taken at its full worth in SOL. Every other claim (a shipping address, a gift card's code, a Steam trade link, a hotel) is on souvenir.finance/prizes. Takes the token from sign_in (sign_in_challenge with your wallet's address, sign its message with the wallet, sign_in), as token or as the request's Authorization: Bearer header. Refused with "Wins through the API are not open yet." while they are not open to your wallet, as launching is.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
prepare_launchPrepares your launch, as the site's launch form does (the same checks, fees and rules): stores the picture and the coin's metadata and answers { mint, transaction, summary }, the t…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Prepares your launch, as the site's launch form does (the same checks, fees and rules): stores the picture and the coin's metadata and answers { mint, transaction, summary }, the transaction base64 for your wallet to sign (a pump.fun launch adds venue and transactions, the same one in a list). Sign it with your wallet without sending it and give it to submit_launch within the hour. The picture is imageUrl: an https address on a public host, fetched once, held to the site's picture rules (png, jpg, gif or webp, at most 4 MB). A coin with a prize names one: skin (an id from search_prizes), case, or basket (2 to 10 ids). With a dev buy your wallet's WBTC does not cover, it answers devSwap instead: sign its transaction and send it (send_transaction, or any Solana RPC), then prepare_launch again with devBuySats as given. Takes the token from sign_in, as token or as the request's Authorization: Bearer header. Refused with "Launching through the API is not open yet." while it is not open to your wallet. Launching a coin, in order: (1) sign_in_challenge with your wallet's address, sign its message with that wallet, then sign_in for a token; (2) launch_options, and search_prizes for the prize; (3) prepare_launch; (4) sign the transaction it answers with your wallet, without sending it, and give it to submit_launch; (5) launch_status until it answers confirmed: a pump.fun launch first answers split with a second transaction, which you sign (or sign and send) and give to submit_split, then launch_status again. Your wallet pays and signs everything: Souvenir never needs or asks for its private key.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: true
quote_tradeWhat a buy or a sell of a Souvenir coin gives now, as the coin's page quotes it: { out, minOut, feeLamports, partial, venue }.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it What a buy or a sell of a Souvenir coin gives now, as the coin's page quotes it: { out, minOut, feeLamports, partial, venue }. out and minOut are the coin's raw units for a buy, lamports for a sell; minOut is the least you get at slippageBps. feeLamports is the trading fee (null on a pump.fun coin, where pump.fun takes it); partial, a buy larger than the curve has left (spent and refund say how much goes in). Trading a coin, in order: (1) quote_trade to see what you would get; (2) build_trade with your wallet's address; (3) sign the transaction it answers with your wallet; (4) send_transaction, or send it yourself through any Solana RPC. No sign-in: your wallet's signature is the approval, and Souvenir never needs its private key. The same fees and limits as the coin's page on souvenir.finance. An agent helping a person, which can't sign with their wallet, uses request_trade instead and gives them the link to approve it with their own wallet.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
recent_winsThe latest wins on Souvenir, newest first, as the site's Recent winners lists them: { wins }, each with mint, symbol, coinImage, skin (the prize), skinImage, winner, winnerShort, r…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it The latest wins on Souvenir, newest first, as the site's Recent winners lists them: { wins }, each with mint, symbol, coinImage, skin (the prize), skinImage, winner, winnerShort, round, at, state, ordered, claimRule, lastCall, solLamports (a last call's SOL), offer and worthUsd. Wins of adult (NSFW) prizes are left out, as on the site, unless nsfw is true: from the latest 200, so a page may hold fewer than limit.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
request_tradeFor an agent helping a person who holds their own wallet: a link (url) for them to open, see this trade with a fresh quote, and approve it with their own wallet on souvenir.finance…No findings
Why it is in this group
- The name "request_trade" says "request": a word for a change.
Description, as the server wrote it For an agent helping a person who holds their own wallet: a link (url) for them to open, see this trade with a fresh quote, and approve it with their own wallet on souvenir.finance. Answers { id, url, state, expiresAt, side, amount, slippageBps, coin, quote }: quote is what the trade gives now (out, minOut, feeLamports, partial, venue), and the page quotes again when it is opened. Show the person the url and say what the trade is (buy or sell, the coin, the amount). Nothing happens until they approve it in their wallet: Souvenir and you never sign for them. The link lasts an hour, makes at most one trade, and asks for at most 10% slippage (slippageBps 10 to 1000, 300 by default). Then read how it ended with trade_request.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
sign_inThe signed challenge: { token, wallet, expiresAt }, a token for an hour (then sign in again) that the launch tools take as token, or that the request sends as Authorization: Bearer…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it The signed challenge: { token, wallet, expiresAt }, a token for an hour (then sign in again) that the launch tools take as token, or that the request sends as Authorization: Bearer <token>. Launching a coin, in order: (1) sign_in_challenge with your wallet's address, sign its message with that wallet, then sign_in for a token; (2) launch_options, and search_prizes for the prize; (3) prepare_launch; (4) sign the transaction it answers with your wallet, without sending it, and give it to submit_launch; (5) launch_status until it answers confirmed: a pump.fun launch first answers split with a second transaction, which you sign (or sign and send) and give to submit_split, then launch_status again. Your wallet pays and signs everything: Souvenir never needs or asks for its private key.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
sign_in_challengeThe first step of launching: { id, message, expiresAt } for your Solana wallet.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it The first step of launching: { id, message, expiresAt } for your Solana wallet. Sign message (its UTF-8 bytes) with the wallet's ed25519 key and give id and the signature (base64) to sign_in within 5 minutes. Signing it authorizes no transaction or transfer. Launching a coin, in order: (1) sign_in_challenge with your wallet's address, sign its message with that wallet, then sign_in for a token; (2) launch_options, and search_prizes for the prize; (3) prepare_launch; (4) sign the transaction it answers with your wallet, without sending it, and give it to submit_launch; (5) launch_status until it answers confirmed: a pump.fun launch first answers split with a second transaction, which you sign (or sign and send) and give to submit_split, then launch_status again. Your wallet pays and signs everything: Souvenir never needs or asks for its private key.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
submit_launchYour wallet's signed launch: Souvenir checks it is the prepared one (your wallet may only add its compute budget or guard instructions), adds the coin's own signature and sends it.Reads text others writeNo findings
Why it is in this group
- The name "submit_launch" says "submit": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Your wallet's signed launch: Souvenir checks it is the prepared one (your wallet may only add its compute budget or guard instructions), adds the coin's own signature and sends it. Answers { signature }. Then launch_status. Takes the token from sign_in, as token or as the request's Authorization: Bearer header. Refused with "Launching through the API is not open yet." while it is not open to your wallet. Launching a coin, in order: (1) sign_in_challenge with your wallet's address, sign its message with that wallet, then sign_in for a token; (2) launch_options, and search_prizes for the prize; (3) prepare_launch; (4) sign the transaction it answers with your wallet, without sending it, and give it to submit_launch; (5) launch_status until it answers confirmed: a pump.fun launch first answers split with a second transaction, which you sign (or sign and send) and give to submit_split, then launch_status again. Your wallet pays and signs everything: Souvenir never needs or asks for its private key.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: true
submit_splitThe split launch_status handed over, approved by your wallet: either the signature of the transaction your wallet signed and sent itself, or the signed transaction (base64) for Sou…Reads text others writeNo findings
Why it is in this group
- The name "submit_split" says "submit": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it The split launch_status handed over, approved by your wallet: either the signature of the transaction your wallet signed and sent itself, or the signed transaction (base64) for Souvenir to send. Answers { signature }. Then launch_status until confirmed. Takes the token from sign_in, as token or as the request's Authorization: Bearer header. Refused with "Launching through the API is not open yet." while it is not open to your wallet. Launching a coin, in order: (1) sign_in_challenge with your wallet's address, sign its message with that wallet, then sign_in for a token; (2) launch_options, and search_prizes for the prize; (3) prepare_launch; (4) sign the transaction it answers with your wallet, without sending it, and give it to submit_launch; (5) launch_status until it answers confirmed: a pump.fun launch first answers split with a second transaction, which you sign (or sign and send) and give to submit_split, then launch_status again. Your wallet pays and signs everything: Souvenir never needs or asks for its private key.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: true
trade_requestHow an approval link from request_trade stands: { id, url, state, expiresAt, side, amount, slippageBps, coin, wallet, signature, out }.1 finding
Why it is in this group
- The name "trade_request" says "request": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "trade_request" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "trade_request" says "request": a word for a change.
Description, as the server wrote it How an approval link from request_trade stands: { id, url, state, expiresAt, side, amount, slippageBps, coin, wallet, signature, out }. state: open (waiting for the person), sent (they approved and the trade is on its way to Solana), confirmed (it landed: signature is the transaction, wallet the one that traded), failed (it landed and failed on chain), dropped (the network dropped it, so it never landed), declined (they declined it), expired (an hour passed with no approval) or stopped (the approval stopped partway, so Souvenir can't tell whether the trade went out: the person should check their wallet before asking for a new link). A link that ended never comes back: ask for a new one. wallet and out are given once the trade was sent; out is what the trade was built to give (coins for a buy, lamports for a sell); the exact amount is on chain under signature. Read it every few seconds while it is open or sent.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
Only reads 6Show 6 read-only tools
get_coinOne coin by its mint address, as search_coins lists it: mint, symbol, name, image, venue (pump, meteora or bags), origin (launched on Souvenir or brought), mode (full: its rounds d…No findings
Why it is in this group
- The name "get_coin" says "get": a word for reading.
Description, as the server wrote it One coin by its mint address, as search_coins lists it: mint, symbol, name, image, venue (pump, meteora or bags), origin (launched on Souvenir or brought), mode (full: its rounds draw an item; draws: they pay drawSol in SOL; prizes: its creator awards prizes), potSol (the open pot), prize (full mode: id, image, priceUsd), round (the latest unfinished one: number, state, targetSol, potSol), holders (at the latest snapshot) and links. A coin that is not on Souvenir is not found.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
get_holdersA coin's holders now, as its page shows them: { slot, total, streak, holdHours, holders }, the 50 with the most draw tickets: owner, amount (the coins held now, raw units), tickets…Reads text others writeNo findings
Why it is in this group
- The name "get_holders" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "ticket": it reads issues, which other people can write.
Description, as the server wrote it A coin's holders now, as its page shows them: { slot, total, streak, holdHours, holders }, the 50 with the most draw tickets: owner, amount (the coins held now, raw units), tickets, multiplier (1 to 2 with holding streaks, to 3 with staked coins), odds (of its next draw, 0 to 1) and locked (staked coins, raw) when there are any. Its pools, Souvenir's own wallets and the coin's creator are left out: they never win its draws. total is every ticket counted.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
get_roundOne round in full: { round } with its mode, target and pot, its state in words (stateText), and its proof: the holder snapshot's slot, the ticket total, the Merkle root, the drand …Reads text others writeNo findings
Why it is in this group
- The name "get_round" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "ticket": it reads issues, which other people can write.
Description, as the server wrote it One round in full: { round } with its mode, target and pot, its state in words (stateText), and its proof: the holder snapshot's slot, the ticket total, the Merkle root, the drand round and randomness, and the winning ticket (SHA-256 of the randomness, as a number, modulo the total). A prize the creator awarded has proof { awardedBy: "creator" }; a round not drawn yet has none.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
get_roundsA coin's rounds, newest first, 50 a page.No findings
Why it is in this group
- The name "get_rounds" says "get": a word for reading.
Description, as the server wrote it A coin's rounds, newest first, 50 a page. Answers { rounds, next }; each round: number, state, prize, winner, drawnAt, deliveredAt, paidSol (SOL paid to the winner, else null). For older rounds, pass next back as cursor; it is null on the last page.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
search_coinsLists coins on Souvenir, searched and sorted.No findings
Why it is in this group
- The name "search_coins" says "search": a word for reading.
Description, as the server wrote it Lists coins on Souvenir, searched and sorted. Answers { coins, nextCursor }. Each coin: mint, symbol, name, image, venue (pump, meteora or bags), origin (launched on Souvenir or brought), mode (full: its rounds draw an item; draws: they pay drawSol in SOL; prizes: its creator awards prizes), potSol (the open pot), prize (full mode: id, image, priceUsd), round (the latest unfinished one: number, state, targetSol, potSol), holders (at the latest snapshot) and links. For the next page, pass nextCursor back as cursor; it is null on the last page. Coins whose prize is adult (NSFW) are left out, as on the site, unless nsfw is true.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
search_prizesPrizes a coin can be launched with now, from Souvenir's catalogue: { prizes, total, next }.No findings
Why it is in this group
- The name "search_prizes" says "search": a word for reading.
Description, as the server wrote it Prizes a coin can be launched with now, from Souvenir's catalogue: { prizes, total, next }. Each prize: id (what prepare_launch takes as skin), title, kind, priceUsd, from (true: a family priced from its smallest, which id names), image, and store, sizes or note when it has them. For the next page, pass next back as offset; it is null on the last page. No sign-in needed. CS2 skins are not listed here: a launch names one by its market name, such as "AK-47 | Redline (Field-Tested)". Launching a coin, in order: (1) sign_in_challenge with your wallet's address, sign its message with that wallet, then sign_in for a token; (2) launch_options, and search_prizes for the prize; (3) prepare_launch; (4) sign the transaction it answers with your wallet, without sending it, and give it to submit_launch; (5) launch_status until it answers confirmed: a pump.fun launch first answers split with a second transaction, which you sign (or sign and send) and give to submit_split, then launch_status again. Your wallet pays and signs everything: Souvenir never needs or asks for its private key.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write11
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out2
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 17, 2026, 15:21 UTC, unchanged since Nov 17, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 20
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 20 tools that change things (5 destructive, 15 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://souvenir.finance/mcp: tools/list returned 26 tools to an anonymous client, including send_transaction (destructive), claim_sol (destructive), revoke_coin_key (destructive), set_coin_mode (destructive), award_prize (destructive) and 15 more
Posture changes
- Nov 17, 2026
- Tools that change things, listed without credentials: 17 to 20
Findings
Matches of fixed checks, with the text they matched.
- Warnlaunch_status
The server marks "launch_status" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"openWorldHint":true}; The name "launch_status" says "status": a word for reading.
- Warntrade_request
The server marks "trade_request" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "trade_request" says "request": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Tools that change things, listed without credentials: 17 -> 20.View diff
- Tools that change things, listed without credentials: 17 to 20
Tools2 added, 5 changed.+2 added~5 changedView diff
- Added:request_tradeChanges things
- Added:trade_requestChanges things
- Changed:build_tradeChanges thingsdescription
- Changed:prepare_launchChanges thingsinputSchema
- Changed:quote_tradeChanges thingsdescription
- Changed:send_transactionDeletes or cancelsdescription
- Changed:set_coin_modeDeletes or cancelsdescription
Tools19 added.+19 addedView diff
- Added:award_prizeDeletes or cancels
- Added:build_tradeChanges things
- Added:claim_solDeletes or cancels
- Added:create_coin_keyChanges things
- Added:get_holdersOnly reads
- Added:launch_optionsChanges things
- Added:launch_statusChanges things
- Added:my_winsChanges things
- Added:prepare_launchChanges things
- Added:quote_tradeChanges things
- Added:recent_winsChanges things
- Added:revoke_coin_keyDeletes or cancels
- Added:search_prizesOnly reads
- Added:send_transactionDeletes or cancels
- Added:set_coin_modeDeletes or cancels
- Added:sign_inChanges things
- Added:sign_in_challengeChanges things
- Added:submit_launchChanges things
- Added:submit_splitChanges things
Install
Pinned to version 1.3.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http coins https://souvenir.finance/mcpclaude mcp add --transport http coins https://souvenir.finance/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__coins__search_coins",
"mcp__coins__get_coin",
"mcp__coins__get_rounds",
"mcp__coins__get_round",
"mcp__coins__search_prizes",
"mcp__coins__get_holders"
],
"ask": [
"mcp__coins__sign_in_challenge",
"mcp__coins__sign_in",
"mcp__coins__launch_options",
"mcp__coins__prepare_launch",
"mcp__coins__submit_launch",
"mcp__coins__launch_status",
"mcp__coins__submit_split",
"mcp__coins__quote_trade",
"mcp__coins__build_trade",
"mcp__coins__request_trade",
"mcp__coins__trade_request",
"mcp__coins__my_wins",
"mcp__coins__recent_wins",
"mcp__coins__create_coin_key"
],
"deny": [
"mcp__coins__send_transaction",
"mcp__coins__claim_sol",
"mcp__coins__revoke_coin_key",
"mcp__coins__set_coin_mode",
"mcp__coins__award_prize"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as coins. Review it before you use it.
Capability tags behind 12 rules
- mcp__coins__get_round untrusted-input
- mcp__coins__prepare_launch untrusted-input
- mcp__coins__submit_launch untrusted-input
- mcp__coins__launch_status untrusted-input
- mcp__coins__submit_split untrusted-input
- mcp__coins__quote_trade untrusted-input
- mcp__coins__build_trade untrusted-input
- mcp__coins__send_transaction untrusted-input, outbound
- mcp__coins__claim_sol untrusted-input
- mcp__coins__get_holders untrusted-input
- mcp__coins__create_coin_key outbound
- mcp__coins__award_prize untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/finance.souvenir/coins/verify?hash=484ffbaaae74088209dca5910d62dbe24033779996f1a2356ee7e7dc45e28d17" | jq -e '.changed == false'Pinned hash 484ffbaaae74, from Nov 13, 2026, 19:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/finance.souvenir/coins/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/finance.souvenir/coins)Source: MCP Registry. Synced Nov 13, 2026, 19:17 UTC.
Souvenir MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Souvenir MCP server safe?
- No scan can promise that. What its definitions show: 25 tools, 19 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Souvenir MCP server delete data?
- Yes. 5 tools can delete, cancel or revoke something: send_transaction, claim_sol, revoke_coin_key, set_coin_mode and award_prize.
Can the Souvenir MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Souvenir MCP server have?
- 25 tools: 5 destructive, 14 write, 6 read. send_transaction, claim_sol, revoke_coin_key, set_coin_mode, award_prize, sign_in_challenge, sign_in, launch_options and 17 more.
Does the Souvenir MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Souvenir MCP server send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): send_transaction and create_coin_key.
Has the Souvenir MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 13, 2026. Every change is on this page and in its Atom feed.