# BagOS (npm · bagos-mcp-server) MCP server for Bags on Solana: token analytics, trade quotes, and gated write operations. - Trust score: 80/100 (high trust) - Change this week: −1 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-09-20 ## Components - npm · `bagos-mcp-server`: 80/100 (this document), [markdown](https://verifymcp.io/servers/edycutjong-bagos/bagos-mcp-server.md), [page](https://verifymcp.io/servers/edycutjong-bagos/bagos-mcp-server) ## Channel facts - Registry: `npm` - Package: `bagos-mcp-server` - Version: `2.6.0` - Transport: `stdio` ## Trust breakdown How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-09-20. - **Supply Chain Security**: 89/100 - No malware found by supply-chain analysis. - CVE check failed: a known high-severity CVE affects axios 1.11.0, reached via @bagsfm/bags-sdk > axios. A fixed version is available. - No install/post-install scripts declared. - Dependency health was assessed across the 400 of 437 dependencies we could resolve, so this covers what we could see, not the whole tree. - **Provenance & Transparency**: 48/100 - Source repository is publicly reachable at the declared URL. - Build provenance is cryptographically sound, but it attests a different repository to the one declared in the registry. Most often the declared URL is simply stale. - Clear OSI-approved license (MIT). - Actively maintained (last published 35 days ago). - Publishes a security disclosure policy (SECURITY.md). - **Schema Quality & AI Usability**: 80/100 - AI-judged instruction clarity (excellent). - Tool/resource definitions use about 1193 tokens (~85/item across 14 items; 14 tools + 0 resources), lean. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 93/100 - Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 100/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 100% of tool parameters carry a description. - **Tool Safety**: 75/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "bags_execute_trade" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. - An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. ## Install ### How do I install the BagOS MCP server? BagOS runs locally as an npm package, launched with npx -y bagos-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation. ### Claude ```bash claude mcp add edycutjong-bagos -- npx -y bagos-mcp-server ``` ### Cursor ```json { "mcpServers": { "edycutjong-bagos": { "command": "npx", "args": [ "-y", "bagos-mcp-server" ] } } } ``` ### VS Code ```json { "servers": { "edycutjong-bagos": { "command": "npx", "args": [ "-y", "bagos-mcp-server" ] } } } ``` ### Codex ```bash codex mcp add edycutjong-bagos -- npx -y bagos-mcp-server ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "edycutjong-bagos": { "type": "local", "command": [ "npx", "-y", "bagos-mcp-server" ], "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add edycutjong-bagos --command npx --arg -y --arg bagos-mcp-server ``` ### Hermes ```yaml mcp_servers: edycutjong-bagos: command: "npx" args: ["-y", "bagos-mcp-server"] ``` ### Netclaw ```json { "McpServers": { "edycutjong-bagos": { "Transport": "stdio", "Command": "npx", "Arguments": [ "-y", "bagos-mcp-server" ] } } } ``` ### Vellum ```bash assistant mcp add edycutjong-bagos -t stdio -c npx -a -y bagos-mcp-server ``` ### Other ```json { "mcpServers": { "edycutjong-bagos": { "command": "npx", "args": [ "-y", "bagos-mcp-server" ] } } } ``` ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-09-20 (score 80, 0) - [security regression] GHSA-5p4m-2wfm-xmqj affects this package: high - [security regression] CVE-2025-58754 affects this package: high - [security regression] CVE-2026-42040 affects this package: high - [security regression] CVE-2026-42043 affects this package: high - [security regression] CVE-2026-41907 affects this package: high - [security regression] CVE-2026-44496 affects this package: high - [security regression] CVE-2026-42037 affects this package: high - [security regression] CVE-2026-42042 affects this package: high - [security regression] CVE-2026-67312 affects this package: high - [security regression] CVE-2026-27903 affects this package: high - [security regression] CVE-2026-25639 affects this package: high - [security regression] CVE-2026-44488 affects this package: high - [security regression] CVE-2026-27904 affects this package: high - [security regression] GHSA-5c6j-r48x-rmvq affects this package: high - [security regression] CVE-2026-42039 affects this package: high - [security regression] CVE-2026-67316 affects this package: high - [security regression] CVE-2026-40175 affects this package: high - [security regression] CVE-2026-42041 affects this package: high - [security regression] CVE-2026-67213 affects this package: high - [security regression] CVE-2026-67313 affects this package: high - [security regression] CVE-2026-67319 affects this package: high - [security regression] CVE-2026-73086 affects this package: high - [security regression] CVE-2026-42038 affects this package: high - [security regression] GHSA-g7r4-m6w7-qqqr affects this package: high - [security regression] CVE-2026-42033 affects this package: high - [security regression] CVE-2024-55565 affects this package: high - [security regression] CVE-2026-34043 affects this package: high - [security regression] CVE-2026-24001 affects this package: high - [security regression] CVE-2026-84375 affects this package: high - [security regression] CVE-2026-42036 affects this package: high - [security regression] CVE-2026-63376 affects this package: high - [security regression] CVE-2026-26996 affects this package: high - [security regression] CVE-2026-44486 affects this package: high - [security regression] CVE-2026-42035 affects this package: high - [security regression] CVE-2025-64718 affects this package: high - [security regression] CVE-2026-59869 affects this package: high - [security regression] CVE-2026-67317 affects this package: high - [security regression] CVE-2026-42034 affects this package: high - [security regression] CVE-2026-44494 affects this package: high - [security regression] CVE-2026-42044 affects this package: high - [security regression] CVE-2026-12143 affects this package: high - [security regression] CVE-2026-42264 affects this package: high - [security regression] CVE-2026-53550 affects this package: high - [security regression] CVE-2026-44495 affects this package: high - [security regression] CVE-2025-62718 affects this package: high - [security regression] CVE-2026-71429 affects this package: high - [security regression] CVE-2026-67214 affects this package: high - [security regression] CVE-2026-77465 affects this package: high - [security regression] CVE-2026-44487 affects this package: high - [security regression] CVE-2026-44490 affects this package: high - [security regression] CVE-2024-11831 affects this package: high ### 2026-09-19 (score 80, +1) - [security regression] CVE-2026-44494 affects this package: high - [security regression] CVE-2025-58754 affects this package: high - [security regression] CVE-2026-42040 affects this package: high - [security regression] CVE-2026-42043 affects this package: high - [security regression] CVE-2026-41907 affects this package: high - [security regression] CVE-2026-44496 affects this package: high - [security regression] CVE-2026-42037 affects this package: high - [security regression] CVE-2026-42042 affects this package: high - [security regression] CVE-2026-67312 affects this package: high - [security regression] CVE-2026-27903 affects this package: high - [security regression] CVE-2026-25639 affects this package: high - [security regression] CVE-2026-44488 affects this package: high - [security regression] CVE-2026-27904 affects this package: high - [security regression] GHSA-5c6j-r48x-rmvq affects this package: high - [security regression] CVE-2026-42039 affects this package: high - [security regression] CVE-2026-67316 affects this package: high - [security regression] CVE-2026-40175 affects this package: high - [security regression] CVE-2026-42041 affects this package: high - [security regression] CVE-2026-67213 affects this package: high - [security regression] CVE-2026-67313 affects this package: high - [security regression] CVE-2026-67319 affects this package: high - [security regression] CVE-2026-73086 affects this package: high - [security regression] CVE-2026-42038 affects this package: high - [security regression] GHSA-g7r4-m6w7-qqqr affects this package: high - [security regression] CVE-2026-42033 affects this package: high - [security regression] CVE-2024-55565 affects this package: high - [security regression] CVE-2026-34043 affects this package: high - [security regression] CVE-2026-24001 affects this package: high - [security regression] CVE-2026-84375 affects this package: high - [security regression] CVE-2026-42036 affects this package: high - [security regression] CVE-2026-63376 affects this package: high - [security regression] CVE-2026-26996 affects this package: high - [security regression] CVE-2026-44486 affects this package: high - [security regression] CVE-2026-42035 affects this package: high - [security regression] CVE-2025-64718 affects this package: high - [security regression] CVE-2026-59869 affects this package: high - [security regression] CVE-2026-67317 affects this package: high - [security regression] CVE-2026-42034 affects this package: high - [security regression] CVE-2026-42044 affects this package: high - [security regression] CVE-2026-12143 affects this package: high - [security regression] CVE-2026-42264 affects this package: high - [security regression] CVE-2026-53550 affects this package: high - [security regression] CVE-2026-44495 affects this package: high - [security regression] CVE-2025-62718 affects this package: high - [security regression] CVE-2026-71429 affects this package: high - [security regression] CVE-2026-67214 affects this package: high - [security regression] CVE-2026-77465 affects this package: high - [security regression] CVE-2026-44487 affects this package: high - [security regression] CVE-2026-44490 affects this package: high - [security regression] CVE-2024-11831 affects this package: high - [security regression] GHSA-5p4m-2wfm-xmqj affects this package: high ### 2026-09-18 (score 79, 0) - [security regression] CVE-2025-58754 affects this package: high - [security regression] CVE-2026-42040 affects this package: high - [security regression] CVE-2026-42043 affects this package: high - [security regression] CVE-2026-41907 affects this package: high - [security regression] CVE-2026-44496 affects this package: high - [security regression] CVE-2026-42037 affects this package: high - [security regression] CVE-2026-42042 affects this package: high - [security regression] CVE-2026-67312 affects this package: high - [security regression] CVE-2026-27903 affects this package: high - [security regression] CVE-2026-25639 affects this package: high - [security regression] CVE-2026-44488 affects this package: high - [security regression] CVE-2026-27904 affects this package: high - [security regression] GHSA-5c6j-r48x-rmvq affects this package: high - [security regression] CVE-2026-42039 affects this package: high - [security regression] CVE-2026-67316 affects this package: high - [security regression] CVE-2026-40175 affects this package: high - [security regression] CVE-2026-42041 affects this package: high - [security regression] CVE-2026-67213 affects this package: high - [security regression] CVE-2026-67313 affects this package: high - [security regression] CVE-2026-67319 affects this package: high - [security regression] CVE-2026-73086 affects this package: high - [security regression] CVE-2026-42038 affects this package: high - [security regression] GHSA-g7r4-m6w7-qqqr affects this package: high - [security regression] CVE-2026-42033 affects this package: high - [security regression] CVE-2024-55565 affects this package: high - [security regression] CVE-2026-34043 affects this package: high - [security regression] CVE-2026-24001 affects this package: high - [security regression] CVE-2026-84375 affects this package: high - [security regression] CVE-2026-42036 affects this package: high - [security regression] CVE-2026-63376 affects this package: high - [security regression] CVE-2026-26996 affects this package: high - [security regression] CVE-2026-44486 affects this package: high - [security regression] CVE-2026-42035 affects this package: high - [security regression] CVE-2024-11831 affects this package: high - [security regression] CVE-2025-64718 affects this package: high - [security regression] CVE-2026-59869 affects this package: high - [security regression] CVE-2026-67317 affects this package: high - [security regression] CVE-2026-42034 affects this package: high - [security regression] CVE-2026-44494 affects this package: high - [security regression] CVE-2026-42044 affects this package: high - [security regression] CVE-2026-12143 affects this package: high - [security regression] CVE-2026-42264 affects this package: high - [security regression] CVE-2026-53550 affects this package: high - [security regression] CVE-2026-44495 affects this package: high - [security regression] CVE-2025-62718 affects this package: high - [security regression] CVE-2026-71429 affects this package: high - [security regression] CVE-2026-67214 affects this package: high - [security regression] CVE-2026-77465 affects this package: high - [security regression] CVE-2026-44487 affects this package: high - [security regression] CVE-2026-44490 affects this package: high - [security regression] GHSA-5p4m-2wfm-xmqj affects this package: high ### 2026-09-17 (score 79, +1) We did not load change detail this far back for this component, so this day may have recorded more than is shown. - [security regression] CVE-2026-67213 affects this package: high - [security regression] CVE-2024-11831 affects this package: high - [security regression] CVE-2026-44490 affects this package: high - [security regression] CVE-2026-44487 affects this package: high - [security regression] CVE-2026-77465 affects this package: high - [security regression] CVE-2026-67214 affects this package: high - [security regression] CVE-2026-71429 affects this package: high - [security regression] CVE-2025-62718 affects this package: high - [security regression] CVE-2026-44495 affects this package: high - [security regression] CVE-2026-53550 affects this package: high - [security regression] CVE-2026-42264 affects this package: high - [security regression] CVE-2026-12143 affects this package: high - [security regression] CVE-2026-42044 affects this package: high - [security regression] CVE-2026-44494 affects this package: high - [security regression] CVE-2026-42034 affects this package: high - [security regression] CVE-2026-67317 affects this package: high - [security regression] CVE-2026-59869 affects this package: high - [security regression] CVE-2025-64718 affects this package: high - [security regression] CVE-2026-42035 affects this package: high - [security regression] CVE-2026-44486 affects this package: high - [security regression] CVE-2026-26996 affects this package: high - [security regression] CVE-2026-63376 affects this package: high - [security regression] CVE-2026-42036 affects this package: high - [security regression] CVE-2026-84375 affects this package: high - [security regression] CVE-2026-24001 affects this package: high - [security regression] CVE-2026-34043 affects this package: high - [security regression] CVE-2024-55565 affects this package: high - [security regression] CVE-2026-42033 affects this package: high - [security regression] GHSA-g7r4-m6w7-qqqr affects this package: high - [security regression] CVE-2026-42038 affects this package: high - [security regression] CVE-2026-73086 affects this package: high - [security regression] CVE-2026-67319 affects this package: high - [security regression] CVE-2026-67313 affects this package: high - [security regression] CVE-2026-42041 affects this package: high - [security regression] CVE-2026-40175 affects this package: high - [security regression] CVE-2026-67316 affects this package: high - [security regression] CVE-2026-42039 affects this package: high - [security regression] GHSA-5c6j-r48x-rmvq affects this package: high - [security regression] CVE-2026-27904 affects this package: high - [security regression] CVE-2026-44488 affects this package: high - [security regression] CVE-2026-25639 affects this package: high - [security regression] CVE-2026-27903 affects this package: high - [security regression] CVE-2026-67312 affects this package: high - [security regression] CVE-2026-42042 affects this package: high - [security regression] CVE-2026-42037 affects this package: high ### 2026-09-16 (score 78, −3) We did not load change detail this far back for this component, so this day may have recorded more than is shown. ### 2026-09-13 (score 81, +1) We did not load change detail this far back for this component, so this day may have recorded more than is shown. ### 2026-09-11 (score 80, +1) We did not load change detail this far back for this component, so this day may have recorded more than is shown. ### 2026-09-09 (score 79, +1) We did not load change detail this far back for this component, so this day may have recorded more than is shown. ## MCP tools (14) ### `bags_authenticate` (~60 tokens) Authenticate with Bags API utilizing the V2 signature challenge flow. Automatically loads local wallet. Input parameters: - `privateKeyPath` (string): Optional path to the wallet keypair. Defaults to ~/.config/bags/keypair.json or BAGS_KEYPAIR_PATH env var. ### `bags_claim_fees` (~100 tokens) GATED WRITE: Claim pending creator/LP fees for the given token mints. Requires $BOS. Two-step: the first call previews and returns a confirmation token; call again with it to sign and submit. Returns confirmed on-chain signatures. Input parameters: - `confirm` (string): Confirmation token from the preview call. Omit on the first call. - `tokenMints` (array, required): Token mint addresses to claim fees for (max 10). ### `bags_execute_trade` (~225 tokens) GATED WRITE: Swap tokens on Bags pools. Requires $BOS. Two-step: the first call returns a preview and a confirmation token; call again with that token to sign and submit. Returns a confirmed on-chain signature. SOL mint: So11111111111111111111111111111111111111112. Input parameters: - `amount` (number): Amount of the input token, human-readable (e.g. 0.1 SOL). Default: 0.1 - `confirm` (string): Confirmation token from the preview call. Omit on the first call. - `inputMint` (string): Input token mint. Defaults to SOL: So11111111111111111111111111111111111111112 - `outputMint` (string): Output token mint. Defaults to BOS: EkJuyYyD3to61CHVPJn6wHb7xANxvqApnVJ4o2SdBAGS - `slippageBps` (integer): Allowed slippage in basis points. Default 300 (3%). ### `bags_get_claimable_fees` (~51 tokens) Query all claimable creator/LP fees for a wallet. Free read-only tier. Input parameters: - `walletAddress` (string): Wallet address to check. Defaults to the local keypair wallet if omitted. ### `bags_get_creators` (~53 tokens) Query top creators by lifetime fees on Bags. Free read-only tier. Input parameters: - `limit` (number): Amount of creators to return (default 10) - `offset` (number): Pagination offset (default 0) ### `bags_get_partner_stats` (~38 tokens) View partner referral earnings for the configured wallet. Free read-only tier. Input parameters: - `partnerId` (string, required): The partner's public key address ### `bags_get_token_analytics` (~45 tokens) Get pool info, claim stats, and bonding curve progress for a token. Free read-only tier. Input parameters: - `tokenMint` (string, required): The token mint address to analyze ### `bags_get_token_claim_events` (~94 tokens) Get the fee-claim audit trail for a token: who claimed, how much, when, and the transaction signature. Paginated via limit/offset. Free read-only tier. Input parameters: - `limit` (integer): Maximum number of events to return (default 100) - `offset` (integer): Pagination offset (default 0) - `tokenMint` (string, required): The token mint address to get claim events for ### `bags_get_token_claim_stats` (~56 tokens) Get per-creator claim totals for a token: each fee-share creator with their royalty split and total claimed amount. Free read-only tier. Input parameters: - `tokenMint` (string, required): The token mint address to get claim stats for ### `bags_get_token_creators` (~59 tokens) Get the royalty split for a token: every creator sharing its fees, their wallet, social provider, and share in basis points. Free read-only tier. Input parameters: - `tokenMint` (string, required): The token mint address to look up creators for ### `bags_get_trade_quote` (~207 tokens) Get a swap quote to trade SOL and any Bags ecosystem token. Free read-only tier. SOL mint: So11111111111111111111111111111111111111112. Default BOS token mint: EkJuyYyD3to61CHVPJn6wHb7xANxvqApnVJ4o2SdBAGS. Input parameters: - `amount` (number, required): Amount of input token to swap in human-readable units (e.g., 0.1 for 0.1 SOL). - `inputMint` (string): Input token mint address. Defaults to SOL: So11111111111111111111111111111111111111112 - `outputMint` (string): Output token mint address. Defaults to BOS: EkJuyYyD3to61CHVPJn6wHb7xANxvqApnVJ4o2SdBAGS - `side` (string, required): Is this a buy or sell action? ### `bags_heartbeat` (~29 tokens) Periodic health check combining basic node status with an earnings/balance summary. Free read-only tier. ### `bags_prepare_token_metadata` (~105 tokens) GATED: Create token info and metadata on Bags, returning the reserved mint address and metadata URL. Requires $BOS. This PREPARES a launch — it does not launch the token and does not send an on-chain transaction. Input parameters: - `description` (string, required): Description for the token - `imageUrl` (string): URL of the token image - `name` (string, required): The full name of the new token - `symbol` (string, required): The ticker symbol ### `bags_resolve_launch_wallet` (~71 tokens) Resolve a social handle (twitter, tiktok, kick, or github) to its Bags fee-share launch wallet. Free read-only tier. Input parameters: - `provider` (string, required): The social platform the username belongs to - `username` (string, required): The username to resolve (a leading @ is stripped automatically) ## Diagnostics Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/edycutjong-bagos/bagos-mcp-server#diagnostics ## Score history - 2026-09-20: 80 - 2026-09-19: 80 - 2026-09-18: 79 - 2026-09-17: 79 - 2026-09-16: 78 - 2026-09-15: 81 - 2026-09-14: 81 - 2026-09-13: 81 - 2026-09-12: 80 - 2026-09-11: 80 - 2026-09-10: 79 - 2026-09-09: 79 - 2026-09-08: 78 - 2026-09-07: 78 - 2026-09-06: 77 - 2026-09-05: 77 - 2026-09-04: 77 - 2026-09-03: 76 - 2026-09-02: 76 - 2026-09-01: 75 - 2026-08-31: 75 - 2026-08-30: 74 - 2026-08-29: 74 - 2026-08-28: 73 - 2026-08-27: 73 - 2026-08-26: 72 - 2026-08-25: 72 - 2026-08-24: 72 - 2026-08-23: 71 - 2026-08-22: 71 ## Common questions ### What is the BagOS MCP server? BagOS is an MCP server listed in the public MCP registry as io.github.edycutjong/bagos. MCP server for Bags on Solana: token analytics, trade quotes, and gated write operations. This page covers its npm package (bagos-mcp-server). ### Is the BagOS MCP server safe to use? BagOS scores 80 out of 100 on VerifyMCP. We recorded 52 known advisories against it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm. ### What tools does the BagOS MCP server expose? BagOS exposes 14 tools: bags_authenticate, bags_claim_fees, bags_execute_trade, bags_get_claimable_fees, bags_get_creators, and 9 more. Their descriptions and schemas cost roughly 1,193 tokens of context every time the server is loaded. ### Is the BagOS MCP server still maintained? BagOS is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced. ### What licence is the BagOS MCP server under? BagOS declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls. ## Links - npm package: https://www.npmjs.com/package/bagos-mcp-server - Socket report: https://socket.dev/npm/package/bagos-mcp-server - Repository: https://github.com/edycutjong/bagos - Changelog RSS feed: https://verifymcp.io/servers/edycutjong-bagos/bagos-mcp-server.xml - Changelog JSON feed: https://verifymcp.io/servers/edycutjong-bagos/bagos-mcp-server.json - HTML version of this page: https://verifymcp.io/servers/edycutjong-bagos/bagos-mcp-server