Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

SolGuard Solana Token-2022 Scanner & Safe-Swap Router

REMOTE · SOLGUARD-PROTOCOL.PAGES.DEV

Solana Token-2022 honeypot scanner, 1-SOL slippage probe & Jito MEV-safe swap router.

−68 this week 0 Trust /100

Last scanned (2 days ago)

Scores higher than 0% of remote servers

Unreachable for 7 days in a row. Last reached 12 Nov 2026.

Category Crypto and Web3

Dead

Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security11
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (2)

  • HTTPS
  • Transport

Checks we could not complete (9)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • TLS certificate in Endpoint SecurityTLS not yet verified: we couldn't open a connection to check the certificate.
  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • HSTS header in Endpoint SecurityHSTS not yet verified: we couldn't read the response headers to check for it.
  • DNSSEC in Endpoint SecurityDNSSEC not yet verified: we couldn't validate it against a resolver.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Nov 26 −14

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 18 Nov 26 −13

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 17 Nov 26 −14

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 16 Nov 26 −13

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 15 Nov 26 −14

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 13 Nov 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • DNSSEC: fail → unverified ▼ security
    • HSTS header: fail → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 12 Nov 26 68

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 19 Nov 2026 · Probed https://solguard-protocol.pages.dev/mcp

TLS unreached
DNSSEC inconclusive

Validation of solguard-protocol.pages.dev. — Inconclusive

Zone DS Keys Algorithms Outcome
solguard-protocol.pages.dev. Error no A/AAAA/CNAME RRset answered for the name
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://solguard-protocol.pages.dev/mcp Unreachable
http (plaintext) http://solguard-protocol.pages.dev/mcp HTTPS enforced
MCP tools · 3 exposed · ~702 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
build_jito_safe_exit ~272

Emergency Dump / Safe-Exit (Token -> SOL): builds an unsigned Solana v0 VersionedTransaction via Jupiter v1 + Jito bundleOnly=true MEV protection, APPENDING the 65 bps (or 45/20 bps partner referral) atomic SOL fee AFTER Jupiter unwraps WSOL so wallets with near-zero free SOL pay the fee directly out of SOL sale proceeds.

NameTypeReqDescription
amountRawstring–Optional exact integer raw base units to sell instead of sellPct
amountTokensnumber–Optional exact UI token amount to sell instead of sellPct
inputMintstring–Token mint Base58 address to sell into native SOL
mintstring–Alias for inputMint (token mint to exit into SOL)
referrerPubkeystring–Optional partner Solana wallet Base58 pubkey for atomic 45/20 bps revenue split (earns 20 bps)
sellPctnumber–Percentage of wallet ATA balance to dump (1-100, default 100)
slippageBpsinteger–Max slippage in basis points (10 to 3000, default 150)
userPublicKeystringyesUser Solana wallet Base58 public key (fee payer & signer)

No output schema declared.

No examples provided.

build_jito_safe_swap ~295

Builds an unsigned Solana v0 VersionedTransaction via Jupiter v1 + atomic 65 bps SolGuard fee transfer + Jito bundleOnly=true MEV protection (supports side='buy' SOL->Token after anti-rug verification, or side='sell' Token->SOL post-unwrap Safe-Exit).

NameTypeReqDescription
amountRawstring–Optional integer base units when side='sell'
amountSolnumber–Swap input amount in SOL (0.0001 to 10000)
amountTokensnumber–Optional UI token quantity when side='sell'
inputMintstring–Input mint Base58 (defaults to native WSOL on buy)
outputMintstringyesTarget Solana token mint Base58 address
referrerPubkeystring–Optional partner Solana wallet Base58 pubkey for atomic 45/20 bps revenue split (earns 20 bps)
sellPctnumber–Optional wallet ATA percentage (1-100) when side='sell'
sidestring–Trade direction: 'buy' (SOL->Token) or 'sell' (Token->SOL)
slippageBpsinteger–Max slippage in basis points (10 to 3000, default 100)
userPublicKeystringyesUser Solana wallet Base58 public key (fee payer & signer)

No output schema declared.

No examples provided.

solana_token_forensic_audit ~135

Live Solana Mainnet forensic honeypot & real-slippage audit: checks mintAuthority, freezeAuthority, Token-2022 extensions (permanentDelegate, transferHook, pausableConfig, nonTransferable, transferFeeConfig), DexScreener liquidity, and live Jupiter v1 1.0 SOL -> Token -> SOL round-trip impact in bps.

NameTypeReqDescription
mintstringyesSolana Base58 SPL or Token-2022 mint address
probeSolnumber–SOL probe size for round-trip quote (0.01 to 100 SOL, default 1.0)

No output schema declared.

No examples provided.

Install

How do I install the SolGuard Solana Token-2022 Scanner & Safe-Swap Router MCP server?

SolGuard Solana Token-2022 Scanner & Safe-Swap Router is a hosted endpoint at https://solguard-protocol.pages.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · solguard-protocol.pages.dev

# add to Claude Code
claude mcp add --transport http tradelord223-solguard-mcp 'https://solguard-protocol.pages.dev/mcp'
Common questions

What is the SolGuard Solana Token-2022 Scanner & Safe-Swap Router MCP server?

SolGuard Solana Token-2022 Scanner & Safe-Swap Router is an MCP server listed in the public MCP registry as io.github.Tradelord223/solguard-mcp. Solana Token-2022 honeypot scanner, 1-SOL slippage probe & Jito MEV-safe swap router. This page covers its hosted endpoint (https://solguard-protocol.pages.dev/mcp).

Is the SolGuard Solana Token-2022 Scanner & Safe-Swap Router MCP server safe to use?

SolGuard Solana Token-2022 Scanner & Safe-Swap Router scores 0 out of 100 on VerifyMCP. 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 SolGuard Solana Token-2022 Scanner & Safe-Swap Router MCP server expose?

SolGuard Solana Token-2022 Scanner & Safe-Swap Router exposes 3 tools: solana_token_forensic_audit, build_jito_safe_swap, build_jito_safe_exit. Their descriptions and schemas cost roughly 702 tokens of context every time the server is loaded.

Does the SolGuard Solana Token-2022 Scanner & Safe-Swap Router MCP server require authentication?

Its publisher declares no required credentials for SolGuard Solana Token-2022 Scanner & Safe-Swap Router. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the SolGuard Solana Token-2022 Scanner & Safe-Swap Router MCP server still maintained?

SolGuard Solana Token-2022 Scanner & Safe-Swap Router has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 12 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the SolGuard Solana Token-2022 Scanner & Safe-Swap Router MCP server?

VerifyMCP ran 2 checks on SolGuard Solana Token-2022 Scanner & Safe-Swap Router, covering HTTPS and Transport. 9 items could not be completed, a gap on our side rather than a finding about SolGuard Solana Token-2022 Scanner & Safe-Swap Router: TLS certificate, Authorization, HSTS header, DNSSEC and 5 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.