Search / xyz.mindjack/mcp
protogridR0· no sign-inSolana memecoin rug check for trading agents: pump.fun launches, calibrated rug risk, wallets, KOL.
v1.4.5 · active · repository · website · descriptor JSON · versions
{
"mcpServers": {
"mindjack": {
"type": "http",
"url": "https://api.mindjack.xyz/mcp",
"headers": {
"X-API-Key": "${X_API_KEY}"
}
}
}
}claude mcp add --transport http mindjack https://api.mindjack.xyz/mcp --header "X-API-Key: ${X_API_KEY}"[mcp_servers.mindjack]
url = "https://api.mindjack.xyz/mcp"
env_http_headers = { "X-API-Key" = "X_API_KEY" }
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mindjack": {
"type": "remote",
"url": "https://api.mindjack.xyz/mcp",
"enabled": true,
"headers": {
"X-API-Key": "{env:X_API_KEY}"
}
}
}
}{
"mcpServers": {
"mindjack": {
"type": "http",
"url": "https://api.mindjack.xyz/mcp",
"headers": {
"X-API-Key": "${X_API_KEY}"
}
}
},
"deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=mindjack&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vYXBpLm1pbmRqYWNrLnh5ei9tY3AiLCJoZWFkZXJzIjp7IlgtQVBJLUtleSI6IiR7WF9BUElfS0VZfSJ9fQ%3D%3D"
}{
"servers": {
"mindjack": {
"type": "http",
"url": "https://api.mindjack.xyz/mcp",
"headers": {
"X-API-Key": "${X_API_KEY}"
}
}
}
}{
"mcpServers": {
"mindjack": {
"httpUrl": "https://api.mindjack.xyz/mcp",
"headers": {
"X-API-Key": "${X_API_KEY}"
}
}
}
}extensions:
"mindjack":
enabled: true
name: "mindjack"
type: streamable_http
uri: "https://api.mindjack.xyz/mcp"
headers:
"X-API-Key": "${X_API_KEY}"
timeout: 300
Placeholders to fill from your own secret store: ${X_API_KEY}. The registry never accepts secret values.
protocol.modernnewest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28protocol.statelessonly applies to 2026-07-28 serversprotocol.transportstreamable HTTPprotocol.list_ttlonly applies to 2026-07-28 serversauth.prm, auth.as_metadata, auth.cimdno remote uses OAuthauth.secret_in_urlno templated URLtools.descriptionsevery tool has a descriptiontools.description_lengthdescriptions are concisetools.schemasevery tool has an object input schematools.annotations26 of 26 tools declare readOnlyHint or destructiveHinttools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: check_token (idempotentHint, openWorldHint); inspect_token (idempotentHint, openWorldHint); token_report (idempotentHint, openWorldHint); …tools.token_costabout 3,611 tokens to load every tooltools.api_dumptools are not a one-to-one API dumpstability.changesno tool changes in 30 daysstability.rug_pullno tool changed its meaning under the same namedeps.known_vulnsno known advisory in 98 resolved packagesdeps.mcp_sdk_version@modelcontextprotocol/sdk 1.30.1 has 1 known advisory (GHSA-6qxp-vccf-f47h); update @modelcontextprotocol/sdk to 1.31.0 or laterdeps.resolvable@mindjack/[email protected] resolved: 98 packagesNo tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
+repository +dns-namespace +website +reachable +uptime-97% ~updated-49d-ago
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
@mindjack/[email protected] npm97 dependencies, resolved · MCP SDK @modelcontextprotocol/sdk 1.30.1 · advisories checked 2026-10-19
| advisory | severity | package | fixed in |
|---|---|---|---|
| GHSA-6qxp-vccf-f47hMCP TypeScript SDK: OAuth client could send credentials to an authorization server chosen by the MCP server | high | @modelcontextprotocol/[email protected]MCP SDK, direct | fixed in 1.31.0 |
Dependency graphs from deps.dev; advisories from OSV.dev, including the GitHub Advisory Database and the PyPI Advisory Database; all CC BY 4.0. The graph is what a clean install of this version resolves today; nothing was installed or run. How it is checked.
| remote | auth | reachable | uptime 30d | p50 | protocol | last ok |
|---|---|---|---|---|---|---|
https://api.mindjack.xyz/mcp streamable-http | none | yes | 97% | 690 ms | 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07 | 2026-10-20 |
| package | registry | version | runtime | secrets |
|---|---|---|---|---|
@mindjack/mcp | npm | 1.4.5 | npx |
can_i_exitread-only | [$0.005] Can this token be sold RIGHT NOW, and what does a round trip cost: real Jupiter buy and sell routes at $100 and $1000, and the fraction of your money that survives. Verdict follows the worst rung: clear / elevated / thin / trapped / blocked. Quotes only, nothing is signed; not cached, takes a few hundred ms. |
check_tokenread-only | [$0.001] Is this Solana token dangerous? A calibrated rug verdict whose probability is a MEASURED frequency (see get_scorecard), the concentration facts behind it, and how fast this band tends to collapse. Cheapest call, run it on every token; it decides whether inspect_token, token_identity or token_report is worth paying for. Does not name holders. |
check_walletread-only | [$0.006] One wallet across every token we indexed: launches it appeared in, how many ran, roles it recurs in, realised record. Works for any address. kol_record is the per-trade history of tracked KOLs; wallet_network is who this wallet moves with. |
compare_tokensread-only | [$0.025] Were these tokens run by the same people? Give 2-4 mints and get the wallets appearing in more than one, each with the role it played in each. Weigh the roles rather than the count: shared holders are common, a wallet that was an insider in one and a sniper in the next is not. Mints outside our index come back named in not_covered. |
fetchread-only | [$0.025] ChatGPT entry point: everything we hold on one token as one document: the calibrated verdict with its measured hit rate, who holds it and how they connect, and whether it can still be sold. Takes an id from `search`. Same endpoint and price as token_report, which other clients should call. |
find_serial_insidersread-only | [$0.025 per 25] Wallets that keep turning up as insiders across the whole index. Each row carries the wallet's full footprint, because ranking on insider count alone puts bots on top (the highest is flagged in 1,642 tokens and holds 4,091). Read insider_in against also_held: close is a real serial insider, far apart is a bot. |
find_tokensread-only | [$0.005] Recently analysed tokens, each already carrying a verdict, to rank locally before paying for depth. Filters: hours (1-168), min_mcap, platform, limit (1-100). A time-ordered feed with no query; to find a token you know by name or mint, use search_tokens. |
funder_networksread-only | [$0.025/page] Funders ranked by how many fresh wallets they seeded across the whole index, each labelled when we know the exchange behind it. A funder inside one token is a line item; across the index it is a desk. A null label with a high count is the shape worth opening. |
get_balanceread-only | [free] Credits remaining on your key. There is no free allowance: a new key starts at zero and is funded with a USDC deposit, so a balance of 0 means the paid tools will answer 402 until you top up. |
get_coverageread-only | [free] What we hold and how fresh, plus a live example mint guaranteed to have data. Call this first: we index every pump.fun and letsbonk migration since our start date, so an older token you already know will return nothing. |
get_sampleread-only | [free, no key] One fixed token answered in full: the complete check_token, inspect_token and token_identity responses, each carrying the price that call costs. Served by the same handlers as the paid tools, so it is what you would actually get. Use get_coverage for freshness, this for depth. |
get_scorecardread-only | [free] Our measured hit rate per risk band, and how fast each band tends to collapse. Read this to decide how much weight to give our verdicts. Most risk APIs ask you to trust a score; this one shows how it performed. |
inspect_tokenread-only | [$0.005] Who is involved: top holders and supply, the sniper / fresh-wallet / insider / early-buyer split, connected-group topology, tracked-trader activity. Counts and structure only: token_wallets names them, token_graph draws the edges, token_web follows them to earlier launches. |
kol_leaderboardread-only | [$0.02/page] Every tracked KOL wallet, ranked from the recorded trades: lifetime realized SOL, per-token win rate on NET realized SOL, and a recent-activity window. Sort by profit, success or activity. Use to build or refresh a copy-trading watchlist. |
kol_recordread-only | [$0.02] One tracked KOL in depth: lifetime stats, per-token history from every recorded trade (buys, sells, volume, realized SOL) and the latest trades raw. Untracked addresses answer null and cost nothing; check_wallet covers any wallet. |
searchread-only | [$0.005/page] ChatGPT entry point: the same catalogue search as search_tokens (same endpoint and price) returning {id, title, url} rows, each id a Solana mint for `fetch`. ChatGPT connects to nothing without this exact name; other clients should call search_tokens. |
search_tokensread-only | [$0.005/page] Find a token in the analysed catalogue by symbol, name fragment or exact mint, with platform, size and age filters. find_tokens lists what just migrated; this finds the one you mean. `search` is the same call in the shape ChatGPT requires. |
test_hypothesisread-only | [$0.025] Measure what happened to every indexed launch matching your filters: rug rate against the index base rate, peak-gain percentiles, time to peak, collapse speed. Answers pattern questions like 'do launches with under 200 holders die faster?'; to shortlist live tokens to act on, use find_tokens instead. filters is {field: {min,max}} over numeric fields listed by get_coverage, e.g. {total_holders: {min: 200}}. Returns cohort aggregates and a one-sentence finding, never per-token rows. Read-only over stored history; measured past, not a forecast. |
token_changesread-only | [$0.025] Who sold since we analysed it: reads the chain now and diffs the large positions against what we recorded. Use when a cached read feels stale or to see whether concentrated wallets are exiting. The only call that touches the chain live. |
token_graphread-only | [$0.04] The wallet relationship graph behind a token: edges with strength and confidence, cluster membership and role, wash-trading wallets. token_wallets names the holders; this shows how they are CONNECTED and whether a distributed-looking set is one person. Not a first look. |
token_identityread-only | [$0.025] Who is BEHIND this token: what its largest holders did in earlier launches, which sibling tokens the same wallets ran and how those ended, and the measured upside band. The decision-point call. Coverage is reported per call; an empty result is free. |
token_price_pathread-only | [$0.005] What the token did after we called it: peak, drawdown from peak, and where it stands now, at 4-5 second resolution. Our feed starts at analysis; the bonding-curve phase before that is not included. |
token_reportread-only | [$0.025] check_token + inspect_token + token_identity in one call. depth="full" ($0.07) adds the outcome path, live sellability and the wallet graph. Cheaper than the parts; use once a token is worth a real look. `fetch` is this call under the name ChatGPT requires. |
token_walletsread-only | [$0.005] The NAMED wallets behind one token: insiders, snipers, early buyers, fresh wallets, wash traders and tracked KOLs, each with funder (exchanges named), link count and cluster. Lists cap at 100 per class; *_total fields carry real counts. inspect_token gives counts, this gives addresses. |
token_webread-only | [$0.04] Earlier launches tied to this token through shared wallets, with the wallets themselves, each launch's outcome and its highest recorded market cap. Use when token_identity reported shared wallets and you need WHICH launches. token_graph stays inside one token; this crosses tokens. |
wallet_networkread-only | [$0.025] Who one wallet is wired to across the index: direct counterparts with interaction counts, shared tokens, transfer direction where the chain shows it, plus a bounded second hop. check_wallet says what it DID; this says who it MOVES WITH. |
Schemas: list_tools.
{
"name": "xyz.mindjack/mcp",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"remotes": [
{
"url": "https://api.mindjack.xyz/mcp",
"type": "streamable-http",
"headers": [
{
"name": "X-API-Key",
"isSecret": true,
"description": "Optional. Listing the tools needs no credential at all. Calling one needs either this key or an OAuth token: connect without either and the endpoint answers 401 with the address of its protected resource metadata, which is enough for a connector client to complete the OAuth flow on its own. Mint a key instead at https://api.mindjack.xyz/v1/keys"
}
]
}
],
"version": "1.4.5",
"packages": [
{
"version": "1.4.5",
"transport": {
"type": "stdio"
},
"identifier": "@mindjack/mcp",
"runtimeHint": "npx",
"registryType": "npm",
"registryBaseUrl": "https://registry.npmjs.org"
}
],
"repository": {
"url": "https://github.com/freyotrisolana/mindjack-mcp",
"source": "github"
},
"websiteUrl": "https://api.mindjack.xyz",
"description": "Solana memecoin rug check for trading agents: pump.fun launches, calibrated rug risk, wallets, KOL."
}