xyz.mindjack/mcp
REMOTE · API.MINDJACK.XYZ · 2 COMPONENTS · SCANNED OCT 4
Solana memecoin rug check for trading agents: pump.fun launches, calibrated rug risk, wallets, KOL.
Available components
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 Security100
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability97
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 2929 tokens (~97/item across 30 items; 26 tools + 4 resources), lean.Pass
- Tools include usage examples.Pass
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 26 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 28 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
How do I install the xyz.mindjack/mcp server?
xyz.mindjack/mcp is a hosted endpoint at https://api.mindjack.xyz/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 · api.mindjack.xyz
claude mcp add --transport http xyz-mindjack-mcp 'https://api.mindjack.xyz/mcp'
{
"mcpServers": {
"xyz-mindjack-mcp": {
"url": "https://api.mindjack.xyz/mcp"
}
}
} {
"servers": {
"xyz-mindjack-mcp": {
"type": "http",
"url": "https://api.mindjack.xyz/mcp"
}
}
} [mcp_servers.xyz-mindjack-mcp] url = "https://api.mindjack.xyz/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"xyz-mindjack-mcp": {
"type": "remote",
"url": "https://api.mindjack.xyz/mcp",
"enabled": true
}
}
} openclaw mcp add xyz-mindjack-mcp --url 'https://api.mindjack.xyz/mcp' --transport streamable-http
mcp_servers:
xyz-mindjack-mcp:
url: "https://api.mindjack.xyz/mcp" {
"McpServers": {
"xyz-mindjack-mcp": {
"Transport": "http",
"Url": "https://api.mindjack.xyz/mcp"
}
}
} assistant mcp add xyz-mindjack-mcp -t streamable-http -u 'https://api.mindjack.xyz/mcp'
{
"mcpServers": {
"xyz-mindjack-mcp": {
"type": "http",
"url": "https://api.mindjack.xyz/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 17 Sept 26 0
- Stability: 0.97 → pass security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
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 6 Oct 2026 · Probed https://api.mindjack.xyz/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mindjack.xyz | CN=YE1,O=Let's Encrypt,C=US | 17 Sept 2026 | 16 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6414cbc7850ae87b9dfb412261eb4898787 |
| SANs: *.mindjack.xyz, mindjack.xyz | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of api.mindjack.xyz. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | present | 3599, 18130 | 8, 8 | Verified |
| mindjack.xyz. | present | 2371 | 13 | Verified |
| api.mindjack.xyz. | Verified address RRset verified with the apex keys |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://api.mindjack.xyz/.well-known/oauth-protected-resource", scope="mcp:call"
Bearer resource_metadata="https://api.mindjack.xyz/.well-known/oauth-protected-resource", scope="mcp:call" | Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://d3js.org https://cdn.jsdelivr.net https://unpkg.com https://static.cloudflareinsights.com https://challenges.cloudflare.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://cdn.jsdelivr.net; font-src 'self' https://fonts.gstatic.com https://cdn.jsdelivr.net; img-src 'self' data: blob: https:; connect-src 'self' https://api.jup.ag https://quote-api.jup.ag https://lite-api.jup.ag https://api.dexscreener.com https://api.geckoterminal.com https://api.coingecko.com https://auth.privy.io https://api.mainnet-beta.solana.com https://cloudflareinsights.com https://challenges.cloudflare.com https://unpkg.com https://api.mindjack.xyz wss://mindjack.xyz wss://www.mindjack.xyz; frame-src https://auth.privy.io https://dexscreener.com https://challenges.cloudflare.com; frame-ancestors 'none'; base-uri 'self'; form-action 'self'; |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=(), magnetometer=(), gyroscope=() |
Protected resource metadata
| Document | https://api.mindjack.xyz/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://api.mindjack.xyz/mcp |
| Authorisation server | https://mindjack.xyz |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.mindjack.xyz/mcp | Verified | 400 | |
| http (plaintext) | http://api.mindjack.xyz/mcp | HTTPS enforced | 301 | https://api.mindjack.xyz/mcp |
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 →
can_i_exit ~99
[$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.
| Name | Type | Req | Description |
|---|---|---|---|
| mint | string | yes | Solana token mint, base58. |
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | – | – |
| checked_at_sol_usd | number | – | SOL price used to size the ladder, so a dollar rung can be reproduced later. |
| exit | object | – | verdict (clear/elevated/thin/trapped/blocked), action, worst_retained_pct, and a ladder of... |
| method | string | – | How the answer was obtained, and what it cannot see. Quotes only — nothing is signed. |
| mint | string | – | Solana token mint address (base58). |
| says | string | – | The finding in one plain sentence, safe to quote. |
{"mint":"6acH1iae44zL4haWNNCaqcTqS2Q7KNYsWErxCoLW9u9P"} check_token ~97
[$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.
| Name | Type | Req | Description |
|---|---|---|---|
| mint | string | yes | Solana token mint, base58. |
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | – | – |
| facts | object | – | Counts AND the share of supply behind each: snipers, insiders, fresh wallets, wallet groups,... |
| mint | string | – | Solana token mint address (base58). |
| name | string | – | – |
| rug_risk | object | – | – |
| safety | object | – | Mint/freeze authority, LP and timelock state. Reports unknown as unknown, never as zero. |
| symbol | string | – | – |
{"mint":"6acH1iae44zL4haWNNCaqcTqS2Q7KNYsWErxCoLW9u9P"} check_wallet ~80
[$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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Solana wallet, base58. |
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | – | – |
| history | object | – | Appearances, roles it recurs in, and its realised record across the index. |
| known | boolean | – | False when we have never seen this wallet in an indexed token. Never billed. |
| says | string | – | The finding in one plain sentence, safe to quote. |
| trading | object | – | – |
| wallet | string | – | Solana wallet address (base58). |
{"address":"bwamJzztZsepfkteWRChggmXuiiCQvpLqPietdNfSXa"} compare_tokens ~107
[$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.
| Name | Type | Req | Description |
|---|---|---|---|
| mints | array | yes | Two to four mints to compare. |
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | – | – |
| compared | array | – | – |
| count | integer | – | – |
| in_all | integer | – | – |
| not_covered | array | – | mints we do not hold; the rest is still answered, as coverage 'partial'. |
| says | string | – | The finding in one plain sentence, safe to quote. |
| shared | array | – | wallet, in_tokens, mints, roles (holder / insider / early / sniper). |
{"mints":["6acH1iae44zL4haWNNCaqcTqS2Q7KNYsWErxCoLW9u9P","CuPKnZJ6ut7WR5XGjdZtvLQQJpewHNPTuRyXvC8ThXEq"]} fetch ~90
[$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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | A Solana mint address, usually from `search`. |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | The mint this document is about. |
| metadata | object | – | – |
| text | string | – | The full report as JSON text. |
| title | string | – | – |
| url | string | – | Public page for the token, or null if the id was not an address. |
{"id":"6acH1iae44zL4haWNNCaqcTqS2Q7KNYsWErxCoLW9u9P"} find_serial_insiders ~122
[$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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Rows, 1-100. Default 25. |
| min_tokens | integer | – | Minimum tokens flagged in. Default 3. |
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | – | – |
| count | integer | – | – |
| filters | object | – | – |
| says | string | – | The finding in one plain sentence, safe to quote. |
| wallets | array | – | wallet, insider_in, also_held, early_investor_in, avg_supply_pct, realized_sol,... |
{"limit":50,"min_tokens":8} find_tokens ~143
[$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.
| Name | Type | Req | Description |
|---|---|---|---|
| hours | integer | – | Hours back, 1-168. Default 24. |
| limit | integer | – | Rows, 1-100. Default 25. |
| min_mcap | number | – | Minimum market cap, USD. |
| platform | string | – | Launchpad, e.g. pumpfun or letsbonk. |
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | – | – |
| count | integer | – | – |
| filters | object | – | The filters actually applied, echoed back — a caller should not have to guess whether a... |
| says | string | – | The finding in one plain sentence, safe to quote. |
| tokens | array | – | – |
{"hours":6,"min_mcap":50000} funder_networks ~106
[$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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Rows, 1-100. Default 25. |
| min_wallets | integer | – | Minimum wallets seeded. Default 3. |
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | – | – |
| count | integer | – | – |
| filters | object | – | – |
| funders | array | – | funder, funder_known (exchange name when we know the address, else null), wallets_funded,... |
| says | string | – | The finding in one plain sentence, safe to quote. |
{"min_wallets":20} get_balance ~57
[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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| credit_balance | number | – | Credits left. A new key starts at 0. |
| free_remaining | number | – | – |
| key_prefix | string | – | – |
| plan | string | – | – |
| plan_credits_per_month | number | – | – |
| plan_expires_at | number | – | – |
{} get_coverage ~59
[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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | – | – |
| history_from | string | – | – |
| index | object | – | – |
| not_covered | object | – | – |
| platforms | array | – | – |
| pricing | object | – | – |
| start_here | object | – | – |
| stats | object | – | – |
| universe | string | – | – |
{} get_sample ~71
[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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | – | – |
| identity | object | – | – |
| inspect | object | – | – |
| mint | string | – | – |
| next | array | – | – |
| not_shown | object | – | – |
| says | string | – | – |
| screen | object | – | – |
{} get_scorecard ~59
[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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | – | – |
| bands | array | – | – |
| base_rate_pct | number | – | – |
| calibrated_at | string | – | – |
| says | string | – | – |
| window_days | number | – | – |
{} inspect_token ~83
[$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.
| Name | Type | Req | Description |
|---|---|---|---|
| mint | string | yes | Solana token mint, base58. |
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | – | – |
| activity | object | – | transactions analysed and fee cost. |
| groups | object | – | – |
| holder_wealth | object | – | top-50 SOL distribution; a median near zero is a launch distributed to nobody. |
| mint | string | – | Solana token mint address (base58). |
| top_holders | array | – | rank, wallet, supply_pct, is_whale, is_notable. |
| tracked_traders | object | – | Activity from traders we follow by name. |
| trading_patterns | object | – | scalp score and wash-trading share. |
| wallet_classes | object | – | snipers, insiders, fresh_wallets, early_buyers. |
{"mint":"6acH1iae44zL4haWNNCaqcTqS2Q7KNYsWErxCoLW9u9P"} kol_leaderboard ~125
[$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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Recent window, 1-90 days. Default 7. |
| limit | integer | – | Rows, 1-100. Default 25. |
| sort | string | – | profit: realised SOL. success: win rate. activity: recent trades. |
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | – | – |
| count | integer | – | – |
| filters | object | – | – |
| kols | array | – | wallet, name, handle, verified, followers, lifetime {trades, volume_sol, realized_sol,... |
| says | string | – | The finding in one plain sentence, safe to quote. |
{"days":30,"sort":"success"} kol_record ~75
[$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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Solana wallet, base58. |
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | – | – |
| kol | object | – | Identity and lifetime stats. Null when the address is not a tracked KOL; nothing is charged... |
| recent_trades | array | – | Latest trades: side, sol, realized_sol, roi_pct, entry_mcap, timestamp. |
| tokens | array | – | Per-token rollup: mint, symbol, buys, sells, volume_sol, realized_sol, first and last trade... |
{"address":"CyaE1VxvBrahnPWkqm5VsdCvyS2QmNht2UFrKJHga54o"} search ~102
[$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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Rows, 1-100. Default 25. |
| query | string | yes | Symbol, name fragment, or an exact mint address. |
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | – | coverage, billing and price_usd for this call. |
| count | number | – | – |
| results | array | – | Rows of {id, title, url}. id is the mint; pass it to fetch. |
| says | string | – | – |
{"query":"bonk"} search_tokens ~159
[$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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Analysed within this many days. |
| limit | integer | – | Rows, 1-100. Default 25. |
| min_mcap | number | – | Minimum market cap, USD. |
| offset | integer | – | Rows to skip. Default 0. |
| platform | string | – | Launchpad, e.g. pumpfun or letsbonk. |
| q | string | – | Symbol, name fragment, or exact mint. |
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | – | – |
| count | integer | – | – |
| query | object | – | – |
| says | string | – | The finding in one plain sentence, safe to quote. |
| tokens | array | – | mint, symbol, name, analyzed_at, mcap_at_analysis, platform, holders, insiders, snipers,... |
{"days":7,"q":"bonk"} test_hypothesis ~174
[$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.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | yes | Field bounds as {min,max}; get_coverage lists the fields. |
| window_days | integer | – | Cohort window, days. Default 30. |
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | – | – |
| cohort | object | – | n, rug_pct, base_rate_pct, rug_lift_vs_base, median_peak_gain_pct, p75/p90_peak_gain_pct,... |
| disclaimer | string | – | Measured history, not a forecast, and not adjusted for slippage or fees. |
| filters | object | – | The filters applied, echoed back. |
| says | string | – | The finding in one plain sentence, safe to quote. |
| window_days | integer | – | – |
{"filters":{"total_holders":{"min":200}},"window_days":30} token_changes ~74
[$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.
| Name | Type | Req | Description |
|---|---|---|---|
| mint | string | yes | Solana token mint, base58. |
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | – | – |
| changes | object | – | Movement against the baseline: who left, who grew, and the supply behind it. |
| mint | string | – | Solana token mint address (base58). |
| ready | boolean | – | False when we hold no holder baseline for this token; nothing is charged in that case. |
| says | string | – | The finding in one plain sentence, safe to quote. |
{"mint":"6acH1iae44zL4haWNNCaqcTqS2Q7KNYsWErxCoLW9u9P"} token_graph ~80
[$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.
| Name | Type | Req | Description |
|---|---|---|---|
| mint | string | yes | Solana token mint, base58. |
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | – | – |
| edges | array | – | wallet_a/wallet_b ties with strength and confidence. |
| edges_total | integer | – | True edge count; compare against the returned array to detect truncation. |
| members | array | – | Which wallet sits in which cluster, and its role. |
| members_total | integer | – | – |
| mint | string | – | Solana token mint address (base58). |
| says | string | – | The finding in one plain sentence, safe to quote. |
| wash_wallets | array | – | – |
{"mint":"6acH1iae44zL4haWNNCaqcTqS2Q7KNYsWErxCoLW9u9P"} token_identity ~79
[$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.
| Name | Type | Req | Description |
|---|---|---|---|
| mint | string | yes | Solana token mint, base58. |
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | – | – |
| creator | object | – | address, allocation_pct, has_sold. |
| identity | object | – | holders_checked, holders_with_history (a COUNT), coverage_pct, prior_appearances,... |
| mint | string | – | Solana token mint address (base58). |
| sibling_outcomes | object | – | known vs rugged among the siblings. |
| sibling_tokens | array | – | Earlier tokens these wallets ran: mint, seen_at, shared_wallets, rugged. |
| upside | object | – | Measured 2x/5x rate for tokens whose holders carried this much winning history, against... |
{"mint":"6acH1iae44zL4haWNNCaqcTqS2Q7KNYsWErxCoLW9u9P"} token_price_path ~75
[$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.
| Name | Type | Req | Description |
|---|---|---|---|
| mint | string | yes | Solana token mint, base58. |
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | – | – |
| coverage_note | string | – | Where our feed starts, so the path is not mistaken for the token's whole life. |
| mint | string | – | Solana token mint address (base58). |
| path | object | – | analysed_at, first/last tick, tick count, market cap at analysis / latest / peak / trough,... |
| says | string | – | The finding in one plain sentence, safe to quote. |
{"mint":"6acH1iae44zL4haWNNCaqcTqS2Q7KNYsWErxCoLW9u9P"} token_report ~114
[$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.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | string | – | core: verdict, holders, identity. full adds graph, price path, sellability. |
| mint | string | yes | Solana token mint, base58. |
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | – | – |
| depth | string | – | Which tiers are included. |
| identity | object | – | The full body of the endpoint it names, exactly as that endpoint returns it. |
| inspect | object | – | The full body of the endpoint it names, exactly as that endpoint returns it. |
| mint | string | – | The token this describes. |
| says | string | – | The finding in one plain sentence, safe to quote. |
| screen | object | – | The full body of the endpoint it names, exactly as that endpoint returns it. |
{"depth":"full","mint":"6acH1iae44zL4haWNNCaqcTqS2Q7KNYsWErxCoLW9u9P"} token_wallets ~93
[$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.
| Name | Type | Req | Description |
|---|---|---|---|
| mint | string | yes | Solana token mint, base58. |
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | – | – |
| early_investors | array | – | Addresses with funding source, cluster membership and flags. Capped at 100; the matching... |
| early_total | integer | – | – |
| fresh_total | integer | – | – |
| fresh_wallets | array | – | Addresses with funding source, cluster membership and flags. Capped at 100; the matching... |
| insiders | array | – | Addresses with funding source, cluster membership and flags. Capped at 100; the matching... |
| insiders_total | integer | – | – |
| kols | array | – | Addresses with funding source, cluster membership and flags. Capped at 100; the matching... |
| kols_total | integer | – | – |
| mint | string | – | – |
| says | string | – | The finding in one plain sentence, safe to quote. |
| scalpers | array | – | Addresses with funding source, cluster membership and flags. Capped at 100; the matching... |
| snipers | array | – | Addresses with funding source, cluster membership and flags. Capped at 100; the matching... |
| snipers_total | integer | – | – |
| wash_total | integer | – | – |
| wash_wallets | array | – | Addresses with funding source, cluster membership and flags. Capped at 100; the matching... |
{"mint":"6acH1iae44zL4haWNNCaqcTqS2Q7KNYsWErxCoLW9u9P"} token_web ~92
[$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.
| Name | Type | Req | Description |
|---|---|---|---|
| min_shared | integer | – | Minimum shared wallets. Default 3. |
| mint | string | yes | Solana token mint, base58. |
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | – | – |
| common_wallets | array | – | The shared wallets themselves, with which launches each ties. |
| mint | string | – | – |
| says | string | – | The finding in one plain sentence, safe to quote. |
| tokens | array | – | Launches sharing wallets with this one: mint, shared wallet count, outcome and the highest... |
| web_wallet_pool | integer | – | Wallets considered when building the web. |
{"min_shared":5,"mint":"6acH1iae44zL4haWNNCaqcTqS2Q7KNYsWErxCoLW9u9P"} wallet_network ~74
[$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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Solana wallet, base58. |
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | – | – |
| direct | array | – | Counterparts, each with the wallet, interaction count, shared tokens and transfer direction... |
| direct_total | integer | – | Counterparts found, before the cap. |
| edge_total | integer | – | Edges behind both rings. |
| says | string | – | The finding in one plain sentence, safe to quote. |
| second_hop | array | – | A bounded second ring, reached through the direct counterparts. |
| wallet | string | – | The wallet asked about. |
{"address":"bwamJzztZsepfkteWRChggmXuiiCQvpLqPietdNfSXa"} What is the xyz.mindjack/mcp server?
xyz.mindjack/mcp is listed in the public MCP registry as xyz.mindjack/mcp. Solana memecoin rug check for trading agents: pump.fun launches, calibrated rug risk, wallets, KOL. This page covers its hosted endpoint (https://api.mindjack.xyz/mcp).
Is the xyz.mindjack/mcp server safe to use?
xyz.mindjack/mcp scores 99 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 xyz.mindjack/mcp server expose?
xyz.mindjack/mcp exposes 26 tools: check_token, inspect_token, token_report, token_identity, find_tokens, and 21 more. Their descriptions and schemas cost roughly 2,489 tokens of context every time the server is loaded.
Does the xyz.mindjack/mcp server require authentication?
Yes. xyz.mindjack/mcp asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the xyz.mindjack/mcp server still maintained?
xyz.mindjack/mcp is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.