BlazarForce Polygon MCP server
io.github.cannergtfo-commits/blazarforce-polygoncannergtfo-commitsstreamable-httpv0.3.0Scanned
Read-only Polygon MCP: swap quotes, venue comparison, BZB price, staking, and unsigned tx builders.
30 tools: 4 do something that can't be undone, 22 change things and 4 only read.
- Reads private data · 0
- Reads text others write · 26
- Can send data out · 4
- 9 findings
Tools listed without sign-in. Remote posture
With Anlyon
4 tools here do something that can't be undone. 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 BlazarForce Polygon MCP server can do
The BlazarForce Polygon MCP server is published by the GitHub account cannergtfo-commits. It has 30 tools. It can do things that cannot be undone, such as sending, paying or publishing (blazar_build_swap, blazar_build_nft_transfer, blazar_decode_tx and blazar_simulate_tx) and create or change data (22 tools: blazar_overview, blazar_quote, blazar_check_limit, blazar_plan_twap and 18 more), but cannot delete data. 4 tools only read.
26 tools bring in text other people can write (blazar_overview, blazar_quote, blazar_compare_venues and 23 more); 4 tools can send data out of your system (blazar_build_swap, blazar_build_nft_transfer, blazar_decode_tx and 1 more).
The fixed checks matched 9 findings (annotation-conflict and base64-blob). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 18, 2026, version 0.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.
30 tools
Can't be undone 4Claude Code: ask
blazar_build_nft_transferBuild an UNSIGNED safeTransferFrom for a BlazarForce NFT after checking ownership, with a simulation and warnings (irreversible, contract recipient, burn address).Reads text others writeCan send data out1 finding
Why it is in this group
- The name "blazar_build_nft_transfer" says "transfer": a word for a change that another call does not undo.
- The description says "irreversible".
- The input addresses people (input.to): what it sends cannot be taken back.
- 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.
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Findings
- Warn
The server marks "blazar_build_nft_transfer" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "blazar_build_nft_transfer" says "transfer": a word for a change that another call does not undo.
Description, as the server wrote it Build an UNSIGNED safeTransferFrom for a BlazarForce NFT after checking ownership, with a simulation and warnings (irreversible, contract recipient, burn address). the plugin's signer refuses NFT txs; sign with your own wallet.
Annotations the server declares
- title: Build NFT transfer (unsigned)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
blazar_build_swapOne call to get everything needed to swap through BlazarFeeRouter: ordered txs[] (exact approve if needed, then swap), a plain-English summary per tx, an eth_call simulation of the…Reads text others writeCan send data out1 finding
Why it is in this group
- The input addresses people (input.recipient): what it sends cannot be taken back.
- 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.
- outboundThe input takes a destination (input.recipient): what the tool writes goes there.
Findings
- Warn
The server marks "blazar_build_swap" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The input addresses people (input.recipient): what it sends cannot be taken back.
Description, as the server wrote it One call to get everything needed to swap through BlazarFeeRouter: ordered txs[] (exact approve if needed, then swap), a plain-English summary per tx, an eth_call simulation of the swap (as if the approve were mined), the quote used, guards (minAmountOut, 3-minute deadline) and warnings[]. Use this instead of blazar_quote + blazar_decode_tx + blazar_simulate_tx. Only swaps built here (through BlazarFeeRouter) earn BZB trading rewards. Returns UNSIGNED txs; nothing is sent.
Annotations the server declares
- title: Build swap: approve + swap txs, simulated
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
blazar_decode_txDecode calldata for a tx to a BlazarForce contract or an ERC-20 approve, e.g.Can send data out1 finding
Why it is in this group
- The input addresses people (input.to): what it sends cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Findings
- Warn
The server marks "blazar_decode_tx" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.
Description, as the server wrote it Decode calldata for a tx to a BlazarForce contract or an ERC-20 approve, e.g. one from another tool or agent, so you can check it before signing. Builds already include summaries, so this is for txs from other sources.
Annotations the server declares
- title: Decode a tx before signing
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
blazar_simulate_txDry-run any Polygon tx with eth_call + estimateGas from `from` (POL balance overridden, token balances real).Reads text others writeCan send data out1 finding
Why it is in this group
- The input addresses people (input.to): what it sends cannot be taken back.
- 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.
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Findings
- Warn
The server marks "blazar_simulate_tx" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.
Description, as the server wrote it Dry-run any Polygon tx with eth_call + estimateGas from `from` (POL balance overridden, token balances real). Returns ok, gas, or an error code with a hint. Use for txs from other sources; builds already simulate.
Annotations the server declares
- title: Simulate any tx (read-only)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Changes things 22Claude Code: ask
blazar_build_claimOne call to claim a posted BZB trading reward: the claim tx with a summary (amount and day), a simulation, and NOTHING_TO_CLAIM if the amount is 0.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 One call to claim a posted BZB trading reward: the claim tx with a summary (amount and day), a simulation, and NOTHING_TO_CLAIM if the amount is 0. Returns an UNSIGNED tx.
Annotations the server declares
- title: Build trading-reward claim
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
blazar_build_deployOne call to build an UNSIGNED contract-creation tx for a template, with named parameters per template, the predicted address, a simulation (eth_call creation) and verification sett…Reads text others write1 finding
Why it is in this group
- The name "blazar_build_deploy" says "deploy": a word for a change.
- 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.
Findings
- Warn
The server marks "blazar_build_deploy" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "blazar_build_deploy" says "deploy": a word for a change.
Description, as the server wrote it One call to build an UNSIGNED contract-creation tx for a template, with named parameters per template, the predicted address, a simulation (eth_call creation) and verification settings. Never deploys. Use for launching an agent token or a staking pool on Polygon.
Annotations the server declares
- title: Build deploy tx (ERC-20 or staking pool)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
blazar_build_nft_approveBuild an UNSIGNED approve(tokenId) or setApprovalForAll (or a revoke with approved=false) for a BlazarForce NFT, with warnings for unknown operators and approve-all.Reads text others write1 finding
Why it is in this group
- The name "blazar_build_nft_approve" says "approve": a word for a change.
- 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.
Findings
- Warn
The server marks "blazar_build_nft_approve" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "blazar_build_nft_approve" says "approve": a word for a change.
Description, as the server wrote it Build an UNSIGNED approve(tokenId) or setApprovalForAll (or a revoke with approved=false) for a BlazarForce NFT, with warnings for unknown operators and approve-all. the plugin's signer refuses NFT txs.
Annotations the server declares
- title: Build NFT approve / revoke (unsigned)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
blazar_build_stakeOne call for BZB staking: ordered txs[] (exact approve if needed, then stake / withdraw / claim / exit), a summary per tx, a simulation, and warnings (e.g.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 One call for BZB staking: ordered txs[] (exact approve if needed, then stake / withdraw / claim / exit), a summary per tx, a simulation, and warnings (e.g. REWARDS_ENDED, NOTHING_TO_CLAIM). No lock, no fee. Returns UNSIGNED txs.
Annotations the server declares
- title: Build stake / withdraw / claim / exit
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
blazar_build_staking_v2One call for staking v2: ordered txs[] for stake (exact approve + stake), withdraw, claimAll, claimMany (defaults to only tokens with rewards), exit or emergencyWithdraw, each with…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 One call for staking v2: ordered txs[] for stake (exact approve + stake), withdraw, claimAll, claimMany (defaults to only tokens with rewards), exit or emergencyWithdraw, each with a summary, a simulation, warnings, and a gas limit. withdraw / exit / emergencyWithdraw / claimAll carry gas = max(estimateGas x 1.25, 1.1M) because a cold exit can use ~885k. Returns UNSIGNED txs.
Annotations the server declares
- title: Build staking v2: stake / withdraw / claim / exit (gas-padded)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
blazar_check_limitOff-chain limit-order check for a bot: is the executable BlazarFeeRouter price for this size (after fees and impact) at or above limitPrice (tokenOut per 1 tokenIn)?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 Off-chain limit-order check for a bot: is the executable BlazarFeeRouter price for this size (after fees and impact) at or above limitPrice (tokenOut per 1 tokenIn)? Returns triggered, gapBps and the exact blazar_build_swap args to use. Never sends anything.
Annotations the server declares
- title: Limit-order check (dry run)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
blazar_contractsBlazarForce contract addresses on Polygon (router, factory, fee router, staking, daily rewards, oracle, BZB) plus the pair init code hash.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 BlazarForce contract addresses on Polygon (router, factory, fee router, staking, daily rewards, oracle, BZB) plus the pair init code hash. Use when you need an address or ABI link; blazar_overview already includes these.
Annotations the server declares
- title: Contract addresses
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
blazar_daily_claimableHow much BZB one address can claim for one posted trading-reward day.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 How much BZB one address can claim for one posted trading-reward day. Read-only. Get dayId from blazar_daily_rewards.postedDays.
Annotations the server declares
- title: Claimable trading reward
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
blazar_daily_rewardsBZB daily trading-rewards status for swaps through BlazarFeeRouter: today's dayId, recently posted days with totals and claim deadlines, daily cap, contract balance, and scoring ru…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 BZB daily trading-rewards status for swaps through BlazarFeeRouter: today's dayId, recently posted days with totals and claim deadlines, daily cap, contract balance, and scoring rules. Use it to find a dayId before blazar_daily_claimable or blazar_build_claim.
Annotations the server declares
- title: Trading rewards: status and posted days
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
blazar_deploy_templatesList the contract templates this plugin can build deploy txs for: a fixed-supply ERC-20 (no owner, no tax) and a Synthetix-style staking pool.1 finding
Why it is in this group
- The name "blazar_deploy_templates" says "deploy": 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 "blazar_deploy_templates" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "blazar_deploy_templates" says "deploy": a word for a change.
Description, as the server wrote it List the contract templates this plugin can build deploy txs for: a fixed-supply ERC-20 (no owner, no tax) and a Synthetix-style staking pool. Unaudited. Use before blazar_build_deploy.
Annotations the server declares
- title: Contract templates
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
blazar_earn_strategiesEarning options on BlazarForce ranked from live onchain reads only (no projections): BZB staking, BlazarSwap LP positions with reserves, trading rewards, and the BZB cross-venue sp…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 Earning options on BlazarForce ranked from live onchain reads only (no projections): BZB staking, BlazarSwap LP positions with reserves, trading rewards, and the BZB cross-venue spread. alerts[] at the top flags ended rewards and thin liquidity. Use when the user asks how to earn with BZB or POL here.
Annotations the server declares
- title: Ways to earn with BZB / POL (live reads)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
blazar_nft_collectionsBlazarForce NFT collections on Polygon (Sleepy Validators, Night Market Stubs, Crystal Moths): live name, supply, holder count, top holders, interfaces, sample token URI, site-stat…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 BlazarForce NFT collections on Polygon (Sleepy Validators, Night Market Stubs, Crystal Moths): live name, supply, holder count, top holders, interfaces, sample token URI, site-stated ask, marketplace links. Read-only.
Annotations the server declares
- title: BlazarForce NFT collections
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
blazar_nft_holderWho owns a BlazarForce NFT (tokenId), or which token ids an address holds (owner), with metadata and marketplace operator approvals.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 Who owns a BlazarForce NFT (tokenId), or which token ids an address holds (owner), with metadata and marketplace operator approvals. Read-only.
Annotations the server declares
- title: NFT owner / holdings
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
blazar_nft_listingsListing info for a BlazarForce NFT: owner, the site-stated ask, on-chain marketplace approvals (OpenSea Seaport conduit), and live Rarible orders only if RARIBLE_API_KEY is set in …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 Listing info for a BlazarForce NFT: owner, the site-stated ask, on-chain marketplace approvals (OpenSea Seaport conduit), and live Rarible orders only if RARIBLE_API_KEY is set in your env. There is no on-chain BlazarForce marketplace.
Annotations the server declares
- title: NFT listing info
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
blazar_overviewSTART HERE.Reads text others write1 finding
Why it is in this group
- The description's first verb is "start": a word for a change.
- 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.
Findings
- Warn
The server marks "blazar_overview" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "start": a word for a change.
Description, as the server wrote it START HERE. One call that returns what is live on BlazarForce right now: contract addresses, fees (5 bps wrapper, 30 bps pool), top BlazarSwap pools, BZB price per venue, staking and trading-reward status (e.g. REWARDS_ENDED with date), and which tool to use for what. Use it first in a session, or when unsure which tool fits.
Annotations the server declares
- title: Start here: BlazarForce overview
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
blazar_plan_twapDry-run TWAP planner: splits a swap into N slices every intervalSeconds and compares with one swap now (impact per slice, estimated gain in bps, schedule with min-out per slice).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 Dry-run TWAP planner: splits a swap into N slices every intervalSeconds and compares with one swap now (impact per slice, estimated gain in bps, schedule with min-out per slice). Never sends anything; build each slice with blazar_build_swap when it is due.
Annotations the server declares
- title: TWAP plan (dry run)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
blazar_pricesBZB/WPOL mid price and USD value on BlazarSwap, QuickSwap V2 and SushiSwap V2, with pool depth in USD from the Chainlink-backed Blazar oracle.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 BZB/WPOL mid price and USD value on BlazarSwap, QuickSwap V2 and SushiSwap V2, with pool depth in USD from the Chainlink-backed Blazar oracle. Use for price checks and spread watching, not for a trade quote.
Annotations the server declares
- title: BZB price on each Polygon venue
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
blazar_quotePrice a Polygon swap (POL, WPOL, BZB, BBY, USDC, USDT, WETH, WBTC, M421) before trading.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 Price a Polygon swap (POL, WPOL, BZB, BBY, USDC, USDT, WETH, WBTC, M421) before trading. Use this, not a generic DEX quote, when the user wants BZB or BZB trading rewards: it runs the deployed BlazarFeeRouter math over BlazarSwap, QuickSwap V2 and SushiSwap V2 and returns amountOut, priceImpactBps, venue, warnings[] (shallow pool, high impact, 5 bps wrapper fee vs a direct pool swap), and sizing (largest size under 1% and 5% impact). Read-only. Example: 1 POL -> 12.77 BZB via QuickSwap V2, 36 bps impact.
Annotations the server declares
- title: Quote a Polygon swap (BZB, POL, USDC...)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
blazar_rank_earningRank BlazarForce earning options from live reads only: BZB staking, BlazarSwap LP fee APR (trailing 24h), daily trading rewards, staking v2.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 Rank BlazarForce earning options from live reads only: BZB staking, BlazarSwap LP fee APR (trailing 24h), daily trading rewards, staking v2. Each has status LIVE / UNPROVEN / IDLE / DEAD / NOT_DEPLOYED and why. deadRewards[] lists anything that pays nothing now. Use instead of guessing yields.
Annotations the server declares
- title: Rank earning options; flag dead rewards
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
blazar_staking_infoBZB single-sided staking (BlazarStakingRewards): status first (ACTIVE or REWARDS_ENDED with date), live APR from the reward rate, total staked, and optionally one account's stake, …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 BZB single-sided staking (BlazarStakingRewards): status first (ACTIVE or REWARDS_ENDED with date), live APR from the reward rate, total staked, and optionally one account's stake, earned BZB and allowance. Use before building a stake, or to check rewards.
Annotations the server declares
- title: BZB staking status and APR
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
blazar_staking_v2_infoBlazarMultiRewardStaking (staking v2: stake BZB, earn up to 5 reward tokens, no lock).Reads text others write1 finding
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.
Findings
- Warn
The description contains a 42-character base64 string.
What this check looks forMatched text
description: "..., no lock). Live at 0x4222bFF08cc9D42cd3311033a4882314DfE19615. One call returns s..."
Description, as the server wrote it BlazarMultiRewardStaking (staking v2: stake BZB, earn up to 5 reward tokens, no lock). Live at 0x4222bFF08cc9D42cd3311033a4882314DfE19615. One call returns status/alerts first, minStake, totalStaked, every reward token with per-second rate, next-24h and next-7d emission from the run curves, APR (token-denominated or Chainlink USD when available), run schedule, and optionally one account's stake, share and claimable rewards. Use before blazar_build_staking_v2.
Annotations the server declares
- title: Staking v2 (multi-reward): status, rates, APR, position
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
blazar_tokensUniswap-schema token list (BZB, BBY, WPOL, USDC, USDT, WETH, WBTC, M421) with addresses, decimals and transfer-tax flags.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 Uniswap-schema token list (BZB, BBY, WPOL, USDC, USDT, WETH, WBTC, M421) with addresses, decimals and transfer-tax flags. Use to resolve a symbol to an address.
Annotations the server declares
- title: Token list
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 4Show 4 read-only tools
blazar_compare_venuesCompare one swap across venues before trading: the best BlazarFeeRouter route, the best route on each single venue (BlazarSwap, QuickSwap V2, SushiSwap V2) through the fee router a…Reads text others writeNo findings
Why it is in this group
- The name "blazar_compare_venues" says "compare": a word for reading.
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 Compare one swap across venues before trading: the best BlazarFeeRouter route, the best route on each single venue (BlazarSwap, QuickSwap V2, SushiSwap V2) through the fee router and as a direct pool swap, and a ParaSwap reference price (public API, no key). Each row says rewardsEligible and buildableHere, plus behindBestBps. Read-only. Use when the user asks 'is this the best price?'
Annotations the server declares
- title: Compare a swap across venues
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
blazar_poolsList every BlazarSwap V2 pair on Polygon with live reserves.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "list": a word for reading.
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 List every BlazarSwap V2 pair on Polygon with live reserves. Use for liquidity checks or LP decisions. For a trade price use blazar_quote instead (it also covers QuickSwap and Sushi).
Annotations the server declares
- title: BlazarSwap pools and reserves
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
blazar_recent_eventsRead recent onchain events by log polling: BlazarFeeRouter AggregatedSwap (trader, tokens, amounts, USD) or one BlazarSwap pair's Swap + Sync (reserves and price).Reads text others writeNo findings
Why it is in this group
- The description's first verb is "read": a word for reading.
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 Read recent onchain events by log polling: BlazarFeeRouter AggregatedSwap (trader, tokens, amounts, USD) or one BlazarSwap pair's Swap + Sync (reserves and price). Returns nextFromBlock to poll again. Up to 5,000 blocks per call (about 2 hours).
Annotations the server declares
- title: Recent swaps / pool events (log polling)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
blazar_trading_rewards_previewPreview the BZB daily trading-rewards leaderboard for a UTC day from live BlazarFeeRouter AggregatedSwap logs, using the swap-desk rules: no minimum trade, no per-wallet cap, same-…Reads text others writeNo findings
Why it is in this group
- The name "blazar_trading_rewards_preview" says "preview": a word for reading.
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 Preview the BZB daily trading-rewards leaderboard for a UTC day from live BlazarFeeRouter AggregatedSwap logs, using the swap-desk rules: no minimum trade, no per-wallet cap, same-wallet round trips within 10 minutes netted, top 50 listed, top 25 paid fixed shares of the daily cap. Optional account shows its rank, points, estimated BZB and points needed for a paid slot. An ESTIMATE, not a payment: only poster-posted winners are paid.
Annotations the server declares
- title: Trading-rewards leaderboard preview (estimate)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
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 write26
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out4
- 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 18, 2026, 16:19 UTC, unchanged since Nov 18, 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
- 26
- 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 26 tools that change things (4 irreversible, 22 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.blazarforce.net/mcp: tools/list returned 30 tools to an anonymous client, including blazar_build_swap (irreversible), blazar_build_nft_transfer (irreversible), blazar_decode_tx (irreversible), blazar_simulate_tx (irreversible), blazar_overview (write) and 21 more
Findings
Matches of fixed checks, with the text they matched.
- Warnblazar_overview
The server marks "blazar_overview" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "start": a word for a change.
The server marks "blazar_build_swap" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The input addresses people (input.recipient): what it sends cannot be taken back.
The description contains a 42-character base64 string.
What this check looks forMatched text
description: "..., no lock). Live at 0x4222bFF08cc9D42cd3311033a4882314DfE19615. One call returns s..."
The server marks "blazar_build_nft_transfer" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "blazar_build_nft_transfer" says "transfer": a word for a change that another call does not undo.
The server marks "blazar_build_nft_approve" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "blazar_build_nft_approve" says "approve": a word for a change.
The server marks "blazar_deploy_templates" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "blazar_deploy_templates" says "deploy": a word for a change.
Show 3 more findingsShow fewer
The server marks "blazar_build_deploy" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "blazar_build_deploy" says "deploy": a word for a change.
- Warnblazar_decode_tx
The server marks "blazar_decode_tx" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.
The server marks "blazar_simulate_tx" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.3.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http blazarforce-polygon https://api.blazarforce.net/mcpclaude mcp add --transport http blazarforce-polygon https://api.blazarforce.net/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__blazarforce-polygon__blazar_compare_venues",
"mcp__blazarforce-polygon__blazar_pools",
"mcp__blazarforce-polygon__blazar_recent_events",
"mcp__blazarforce-polygon__blazar_trading_rewards_preview"
],
"ask": [
"mcp__blazarforce-polygon__blazar_overview",
"mcp__blazarforce-polygon__blazar_quote",
"mcp__blazarforce-polygon__blazar_build_swap",
"mcp__blazarforce-polygon__blazar_check_limit",
"mcp__blazarforce-polygon__blazar_plan_twap",
"mcp__blazarforce-polygon__blazar_prices",
"mcp__blazarforce-polygon__blazar_tokens",
"mcp__blazarforce-polygon__blazar_contracts",
"mcp__blazarforce-polygon__blazar_staking_info",
"mcp__blazarforce-polygon__blazar_build_stake",
"mcp__blazarforce-polygon__blazar_staking_v2_info",
"mcp__blazarforce-polygon__blazar_build_staking_v2",
"mcp__blazarforce-polygon__blazar_daily_rewards",
"mcp__blazarforce-polygon__blazar_daily_claimable",
"mcp__blazarforce-polygon__blazar_build_claim",
"mcp__blazarforce-polygon__blazar_earn_strategies",
"mcp__blazarforce-polygon__blazar_rank_earning",
"mcp__blazarforce-polygon__blazar_nft_collections",
"mcp__blazarforce-polygon__blazar_nft_holder",
"mcp__blazarforce-polygon__blazar_nft_listings",
"mcp__blazarforce-polygon__blazar_build_nft_transfer",
"mcp__blazarforce-polygon__blazar_build_nft_approve",
"mcp__blazarforce-polygon__blazar_deploy_templates",
"mcp__blazarforce-polygon__blazar_build_deploy",
"mcp__blazarforce-polygon__blazar_decode_tx",
"mcp__blazarforce-polygon__blazar_simulate_tx"
],
"deny": []
}
}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 blazarforce-polygon. Review it before you use it.
Capability tags behind 27 rules
- mcp__blazarforce-polygon__blazar_overview untrusted-input
- mcp__blazarforce-polygon__blazar_quote untrusted-input
- mcp__blazarforce-polygon__blazar_compare_venues untrusted-input
- mcp__blazarforce-polygon__blazar_build_swap untrusted-input, outbound
- mcp__blazarforce-polygon__blazar_check_limit untrusted-input
- mcp__blazarforce-polygon__blazar_plan_twap untrusted-input
- mcp__blazarforce-polygon__blazar_pools untrusted-input
- mcp__blazarforce-polygon__blazar_prices untrusted-input
- mcp__blazarforce-polygon__blazar_recent_events untrusted-input
- mcp__blazarforce-polygon__blazar_staking_info untrusted-input
- mcp__blazarforce-polygon__blazar_build_stake untrusted-input
- mcp__blazarforce-polygon__blazar_staking_v2_info untrusted-input
- mcp__blazarforce-polygon__blazar_build_staking_v2 untrusted-input
- mcp__blazarforce-polygon__blazar_daily_rewards untrusted-input
- mcp__blazarforce-polygon__blazar_trading_rewards_preview untrusted-input
- mcp__blazarforce-polygon__blazar_daily_claimable untrusted-input
- mcp__blazarforce-polygon__blazar_build_claim untrusted-input
- mcp__blazarforce-polygon__blazar_earn_strategies untrusted-input
- mcp__blazarforce-polygon__blazar_rank_earning untrusted-input
- mcp__blazarforce-polygon__blazar_nft_collections untrusted-input
- mcp__blazarforce-polygon__blazar_nft_holder untrusted-input
- mcp__blazarforce-polygon__blazar_nft_listings untrusted-input
- mcp__blazarforce-polygon__blazar_build_nft_transfer untrusted-input, outbound
- mcp__blazarforce-polygon__blazar_build_nft_approve untrusted-input
- mcp__blazarforce-polygon__blazar_build_deploy untrusted-input
- mcp__blazarforce-polygon__blazar_decode_tx outbound
- mcp__blazarforce-polygon__blazar_simulate_tx untrusted-input, outbound
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/io.github.cannergtfo-commits/blazarforce-polygon/verify?hash=c4cf04fb6643cb63c0167eb738edbefcdb38ea1662754259dce0d954e56e855c" | jq -e '.changed == false'Pinned hash c4cf04fb6643, from Nov 18, 2026, 02:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.cannergtfo-commits/blazarforce-polygon/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.cannergtfo-commits/blazarforce-polygon)Source: MCP Registry. Synced Nov 18, 2026, 02:17 UTC.
BlazarForce Polygon MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the BlazarForce Polygon MCP server safe?
- No scan can promise that. What its definitions show: 30 tools, 26 of which can change, send or delete something, and 9 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 BlazarForce Polygon MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the BlazarForce Polygon MCP server do things that cannot be undone?
- Yes. 4 tools can send, pay, publish or merge: blazar_build_swap, blazar_build_nft_transfer, blazar_decode_tx and blazar_simulate_tx.
What tools does the BlazarForce Polygon MCP server have?
- 30 tools: 4 irreversible, 22 write, 4 read. blazar_build_swap, blazar_build_nft_transfer, blazar_decode_tx, blazar_simulate_tx, blazar_overview, blazar_quote, blazar_check_limit, blazar_plan_twap and 22 more.
Does the BlazarForce Polygon MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the BlazarForce Polygon MCP server send data to outside services?
- 4 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): blazar_build_swap, blazar_build_nft_transfer, blazar_decode_tx and blazar_simulate_tx.
Has the BlazarForce Polygon MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.