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.

JetForge

REMOTE · JETFORGE.IO

Solana launchpad trading: markets, quotes, wallet balances and unsigned buy/sell transactions

Available components

74 Trust /100

Last scanned (4 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Crypto and Web3

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 Security80
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 670 tokens (~167/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 0
    • Schema quality: 143 → 167 ▼ functional
    • “prepare_trade” added an optional parameter “priorityFeeMicroLamports” cosmetic
    • “get_quote” reworded the description of “slippageBps” cosmetic
    • “prepare_trade” reworded the description of “slippageBps” cosmetic
  • 2 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 1 Nov 26 73

    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 5 Nov 2026 · Probed https://jetforge.io/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=jetforge.io CN=YR2,O=Let's Encrypt,C=US 8 Oct 2026 6 Jan 2027 RSA 2048 SHA256-RSA 628306b313c7905ab0aaee8fa26c802f8d5
SANs: app.jetforge.io, jetforge.io, www.jetforge.io
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of jetforge.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 38690 8 Verified
jetforge.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://www.googletagmanager.com; connect-src 'self' wss://api.jetforge.io https://api.jetforge.io https://api.devnet.solana.com https://api.mainnet-beta.solana.com https://mainnet.helius-rpc.com wss://mainnet.helius-rpc.com https://api.coingecko.com https://arweave.net https://api.telegram.org https://*.walletconnect.com https://*.walletconnect.org wss://*.walletconnect.com wss://*.walletconnect.org https://*.web3modal.org https://*.web3modal.com https://*.reown.com https://www.googletagmanager.com https://www.google-analytics.com https://*.google-analytics.com https://*.analytics.google.com; img-src 'self' data: https://arweave.net https://*.arweave.net https://gateway.irys.xyz https://*.legacy.datasprite-cdn.com https://api.jetforge.io blob: https://explorer-api.walletconnect.com https://imagedelivery.net https://www.google-analytics.com https://www.googletagmanager.com https://*.google-analytics.com; style-src 'self' 'unsafe-inline' https
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://jetforge.io/api/mcp Verified 200
http (plaintext) http://jetforge.io/api/mcp HTTPS enforced 301 https://jetforge.io/api/mcp
MCP tools · 4 exposed · ~552 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
get_quote ~175

Price a buy or sell from the token's live on-chain bonding curve, including the 1% fee, price impact and minimum output. Sends nothing. If partialFill is true, the buy would complete the curve and solCharged is what would actually be spent.

NameTypeReqDescription
amountstringyesPositive integer as a string. buy: SOL in lamports (1 SOL = 1000000000). sell: raw token units (6 decimals, 1 token = 1000000)
mintstringyesToken mint address (base58)
sidestringyesTrade direction
slippageBpsinteger–Slippage tolerance in basis points, up to 500 (5%). Default 100 (1%). A sandwich bot can take up to the whole tolerance, so keep it tight

No output schema declared.

No examples provided.

get_wallet ~48

Get the SOL balance and SPL token balances of any Solana wallet.

NameTypeReqDescription
addressstringyesWallet address (base58)
mintsarray–Only return these token mints

No output schema declared.

No examples provided.

list_markets ~74

List active JetForge tokens still on their bonding curve, with live price, reserves and graduation progress (0-100%). Graduated tokens trade on Raydium and are not listed.

NameTypeReqDescription
limitinteger–How many markets to return. Default 50
sortstring–Sort order. Default new

No output schema declared.

No examples provided.

prepare_trade ~255

Build an UNSIGNED buy or sell transaction (base64, legacy format) for the given wallet. This does not execute the trade or move funds. To execute it, sign with that wallet and broadcast to Solana before lastValidBlockHeight. Never send a private key to this tool or any other.

NameTypeReqDescription
amountstringyesPositive integer as a string. buy: SOL in lamports (1 SOL = 1000000000). sell: raw token units (6 decimals, 1 token = 1000000)
mintstringyesToken mint address (base58)
priorityFeeMicroLamportsinteger–Priority fee per compute unit, in micro-lamports. Default 10000. Raise it if trades aren't landing when Solana is busy; the maximum adds at most 0.00025 SOL
sidestringyesTrade direction
slippageBpsinteger–Slippage tolerance in basis points, up to 500 (5%). Default 100 (1%). A sandwich bot can take up to the whole tolerance, so keep it tight
walletPublicKeystringyesPublic address of the wallet that will sign and pay (base58)

No output schema declared.

No examples provided.

Install

How do I install the JetForge MCP server?

JetForge is a hosted endpoint at https://jetforge.io/api/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 · jetforge.io

# add to Claude Code
claude mcp add --transport http io-jetforge-jetforge 'https://jetforge.io/api/mcp'
Common questions

What is the JetForge MCP server?

JetForge is an MCP server listed in the public MCP registry as io.jetforge/jetforge. Solana launchpad trading: markets, quotes, wallet balances and unsigned buy/sell transactions. This page covers its hosted endpoint (https://jetforge.io/api/mcp).

Is the JetForge MCP server safe to use?

JetForge scores 74 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 JetForge MCP server expose?

JetForge exposes 4 tools: list_markets, get_quote, prepare_trade, get_wallet. Their descriptions and schemas cost roughly 552 tokens of context every time the server is loaded.

Does the JetForge MCP server require authentication?

No. We connected to JetForge without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the JetForge MCP server still maintained?

JetForge is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.