_ registry / mcp + a2a streamable-http

mindjack

https://api.mindjack.xyz

Registry code: 4aee1fbf00333cf1

api record

Mindjack answers from a point-in-time record of Solana launches: holder

distribution, insider, fresh-wallet and sniper detection as they stood at

endpoint
https://api.mindjack.xyz/mcp
door code
9177ddea252face8
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
unknown
uptime
—
latency
—

last good check

priced tools
2

of 26 tools

_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 26 tools
2 paid 24 never probed 2 of 26 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • funder_networks 0.025 USDC paid never probed

    [$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.

    mcp-tool

    {
  "type": "object",
  "examples": [
    {
      "min_wallets": 20
    }
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "description": "Rows, 1-100. Default 25."
    },
    "min_wallets": {
      "type": "integer",
      "description": "Minimum wallets seeded. Default 3."
    }
  }
}
    arguments 18 lines
  • search 0.005 USDC paid never probed

    [$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.

    mcp-tool

    {
  "type": "object",
  "examples": [
    {
      "query": "bonk"
    }
  ],
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "description": "Rows, 1-100. Default 25."
    },
    "query": {
      "type": "string",
      "description": "Symbol, name fragment, or an exact mint address."
    }
  }
}
    arguments 21 lines
  • check_token unknown never probed

    [$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.

    mcp-tool

    {
  "type": "object",
  "examples": [
    {
      "mint": "6acH1iae44zL4haWNNCaqcTqS2Q7KNYsWErxCoLW9u9P"
    }
  ],
  "required": [
    "mint"
  ],
  "properties": {
    "mint": {
      "type": "string",
      "description": "Solana token mint, base58."
    }
  }
}
    arguments 17 lines
  • inspect_token unknown never probed

    [$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.

    mcp-tool

    {
  "type": "object",
  "examples": [
    {
      "mint": "6acH1iae44zL4haWNNCaqcTqS2Q7KNYsWErxCoLW9u9P"
    }
  ],
  "required": [
    "mint"
  ],
  "properties": {
    "mint": {
      "type": "string",
      "description": "Solana token mint, base58."
    }
  }
}
    arguments 17 lines
  • token_report unknown never probed

    [$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.

    mcp-tool

    {
  "type": "object",
  "examples": [
    {
      "mint": "6acH1iae44zL4haWNNCaqcTqS2Q7KNYsWErxCoLW9u9P",
      "depth": "full"
    }
  ],
  "required": [
    "mint"
  ],
  "properties": {
    "mint": {
      "type": "string",
      "description": "Solana token mint, base58."
    },
    "depth": {
      "enum": [
        "core",
        "full"
      ],
      "type": "string",
      "description": "core: verdict, holders, identity. full adds graph, price path, sellability."
    }
  }
}
    arguments 26 lines
  • token_identity unknown never probed

    [$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.

    mcp-tool

    {
  "type": "object",
  "examples": [
    {
      "mint": "6acH1iae44zL4haWNNCaqcTqS2Q7KNYsWErxCoLW9u9P"
    }
  ],
  "required": [
    "mint"
  ],
  "properties": {
    "mint": {
      "type": "string",
      "description": "Solana token mint, base58."
    }
  }
}
    arguments 17 lines
  • find_tokens unknown never probed

    [$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.

    mcp-tool

    {
  "type": "object",
  "examples": [
    {
      "hours": 6,
      "min_mcap": 50000
    }
  ],
  "properties": {
    "hours": {
      "type": "integer",
      "description": "Hours back, 1-168. Default 24."
    },
    "limit": {
      "type": "integer",
      "description": "Rows, 1-100. Default 25."
    },
    "min_mcap": {
      "type": "number",
      "description": "Minimum market cap, USD."
    },
    "platform": {
      "type": "string",
      "description": "Launchpad, e.g. pumpfun or letsbonk."
    }
  }
}
    arguments 27 lines
  • check_wallet unknown never probed

    [$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.

    mcp-tool

    {
  "type": "object",
  "examples": [
    {
      "address": "bwamJzztZsepfkteWRChggmXuiiCQvpLqPietdNfSXa"
    }
  ],
  "required": [
    "address"
  ],
  "properties": {
    "address": {
      "type": "string",
      "description": "Solana wallet, base58."
    }
  }
}
    arguments 17 lines
  • can_i_exit unknown never probed

    [$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.

    mcp-tool

    {
  "type": "object",
  "examples": [
    {
      "mint": "6acH1iae44zL4haWNNCaqcTqS2Q7KNYsWErxCoLW9u9P"
    }
  ],
  "required": [
    "mint"
  ],
  "properties": {
    "mint": {
      "type": "string",
      "description": "Solana token mint, base58."
    }
  }
}
    arguments 17 lines
  • token_changes unknown never probed

    [$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.

    mcp-tool

    {
  "type": "object",
  "examples": [
    {
      "mint": "6acH1iae44zL4haWNNCaqcTqS2Q7KNYsWErxCoLW9u9P"
    }
  ],
  "required": [
    "mint"
  ],
  "properties": {
    "mint": {
      "type": "string",
      "description": "Solana token mint, base58."
    }
  }
}
    arguments 17 lines
  • token_price_path unknown never probed

    [$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.

    mcp-tool

    {
  "type": "object",
  "examples": [
    {
      "mint": "6acH1iae44zL4haWNNCaqcTqS2Q7KNYsWErxCoLW9u9P"
    }
  ],
  "required": [
    "mint"
  ],
  "properties": {
    "mint": {
      "type": "string",
      "description": "Solana token mint, base58."
    }
  }
}
    arguments 17 lines
  • find_serial_insiders unknown never probed

    [$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.

    mcp-tool

    {
  "type": "object",
  "examples": [
    {
      "limit": 50,
      "min_tokens": 8
    }
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "description": "Rows, 1-100. Default 25."
    },
    "min_tokens": {
      "type": "integer",
      "description": "Minimum tokens flagged in. Default 3."
    }
  }
}
    arguments 19 lines
  • compare_tokens unknown never probed

    [$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.

    mcp-tool

    {
  "type": "object",
  "examples": [
    {
      "mints": [
        "6acH1iae44zL4haWNNCaqcTqS2Q7KNYsWErxCoLW9u9P",
        "CuPKnZJ6ut7WR5XGjdZtvLQQJpewHNPTuRyXvC8ThXEq"
      ]
    }
  ],
  "required": [
    "mints"
  ],
  "properties": {
    "mints": {
      "type": "array",
      "items": {
        "type": "string",
        "description": "Solana token mint, base58."
      },
      "description": "Two to four mints to compare."
    }
  }
}
    arguments 24 lines
  • test_hypothesis unknown never probed

    [$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.

    mcp-tool

    {
  "type": "object",
  "examples": [
    {
      "filters": {
        "total_holders": {
          "min": 200
        }
      },
      "window_days": 30
    }
  ],
  "required": [
    "filters"
  ],
  "properties": {
    "filters": {
      "type": "object",
      "description": "Field bounds as {min,max}; get_coverage lists the fields."
    },
    "window_days": {
      "type": "integer",
      "description": "Cohort window, days. Default 30."
    }
  }
}
    arguments 26 lines
  • get_scorecard unknown never probed

    [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.

    mcp-tool

    {
  "type": "object",
  "examples": [
    {}
  ],
  "properties": {}
}
    arguments 7 lines
  • get_sample unknown never probed

    [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.

    mcp-tool

    {
  "type": "object",
  "examples": [
    {}
  ],
  "properties": {}
}
    arguments 7 lines
  • token_graph unknown never probed

    [$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.

    mcp-tool

    {
  "type": "object",
  "examples": [
    {
      "mint": "6acH1iae44zL4haWNNCaqcTqS2Q7KNYsWErxCoLW9u9P"
    }
  ],
  "required": [
    "mint"
  ],
  "properties": {
    "mint": {
      "type": "string",
      "description": "Solana token mint, base58."
    }
  }
}
    arguments 17 lines
  • token_wallets unknown never probed

    [$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.

    mcp-tool

    {
  "type": "object",
  "examples": [
    {
      "mint": "6acH1iae44zL4haWNNCaqcTqS2Q7KNYsWErxCoLW9u9P"
    }
  ],
  "required": [
    "mint"
  ],
  "properties": {
    "mint": {
      "type": "string",
      "description": "Solana token mint, base58."
    }
  }
}
    arguments 17 lines
  • token_web unknown never probed

    [$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.

    mcp-tool

    {
  "type": "object",
  "examples": [
    {
      "mint": "6acH1iae44zL4haWNNCaqcTqS2Q7KNYsWErxCoLW9u9P",
      "min_shared": 5
    }
  ],
  "required": [
    "mint"
  ],
  "properties": {
    "mint": {
      "type": "string",
      "description": "Solana token mint, base58."
    },
    "min_shared": {
      "type": "integer",
      "description": "Minimum shared wallets. Default 3."
    }
  }
}
    arguments 22 lines
  • wallet_network unknown never probed

    [$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.

    mcp-tool

    {
  "type": "object",
  "examples": [
    {
      "address": "bwamJzztZsepfkteWRChggmXuiiCQvpLqPietdNfSXa"
    }
  ],
  "required": [
    "address"
  ],
  "properties": {
    "address": {
      "type": "string",
      "description": "Solana wallet, base58."
    }
  }
}
    arguments 17 lines
  • kol_leaderboard unknown never probed

    [$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.

    mcp-tool

    {
  "type": "object",
  "examples": [
    {
      "days": 30,
      "sort": "success"
    }
  ],
  "properties": {
    "days": {
      "type": "integer",
      "description": "Recent window, 1-90 days. Default 7."
    },
    "sort": {
      "enum": [
        "profit",
        "success",
        "activity"
      ],
      "type": "string",
      "description": "profit: realised SOL. success: win rate. activity: recent trades."
    },
    "limit": {
      "type": "integer",
      "description": "Rows, 1-100. Default 25."
    }
  }
}
    arguments 28 lines
  • kol_record unknown never probed

    [$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.

    mcp-tool

    {
  "type": "object",
  "examples": [
    {
      "address": "CyaE1VxvBrahnPWkqm5VsdCvyS2QmNht2UFrKJHga54o"
    }
  ],
  "required": [
    "address"
  ],
  "properties": {
    "address": {
      "type": "string",
      "description": "Solana wallet, base58."
    }
  }
}
    arguments 17 lines
  • search_tokens unknown never probed

    [$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.

    mcp-tool

    {
  "type": "object",
  "examples": [
    {
      "q": "bonk",
      "days": 7
    }
  ],
  "properties": {
    "q": {
      "type": "string",
      "description": "Symbol, name fragment, or exact mint."
    },
    "days": {
      "type": "integer",
      "description": "Analysed within this many days."
    },
    "limit": {
      "type": "integer",
      "description": "Rows, 1-100. Default 25."
    },
    "offset": {
      "type": "integer",
      "description": "Rows to skip. Default 0."
    },
    "min_mcap": {
      "type": "number",
      "description": "Minimum market cap, USD."
    },
    "platform": {
      "type": "string",
      "description": "Launchpad, e.g. pumpfun or letsbonk."
    }
  }
}
    arguments 35 lines
  • fetch unknown never probed

    [$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.

    mcp-tool

    {
  "type": "object",
  "examples": [
    {
      "id": "6acH1iae44zL4haWNNCaqcTqS2Q7KNYsWErxCoLW9u9P"
    }
  ],
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "A Solana mint address, usually from `search`."
    }
  }
}
    arguments 17 lines
  • get_coverage unknown never probed

    [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.

    mcp-tool

    {
  "type": "object",
  "examples": [
    {}
  ],
  "properties": {}
}
    arguments 7 lines
  • get_balance unknown never probed

    [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.

    mcp-tool

    {
  "type": "object",
  "examples": [
    {}
  ],
  "properties": {}
}
    arguments 7 lines
_ try it over mcp through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/4aee1fbf00333cf1/badge.svg)](https://brick.blue/agent/4aee1fbf00333cf1)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we knowoff the mcp door
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.