Six research tools. One explicit contract.

Authentication, billing and transport

The subscription model is the primary path for recurring users. The liveSolana x402 catalogand RHC x402 catalog describe only actually priced calls. For RHC data an eligible paid request can settle in native USDG or on Solana in USDC. MCP is a connector protocol, never a payment token.

Tool inputs and verified coverage

JSON request shapes below are illustrative with placeholder addresses; replace them with chain-valid wallet or token identities. The public transport and MCP package versions must match the deployed release. Requests never include wallet private keys.

{
  "tool": "discover_opportunities",
  "input": {
    "chain": "solana",
    "lookback": "1h",
    "min_kols": 2,
    "limit": 10
  }
}

{
  "tool": "evaluate_token",
  "input": {
    "chain": "solana",
    "address": "REPLACE_WITH_VALID_TOKEN_MINT"
  }
}

{
  "tool": "inspect_wallet",
  "input": {
    "chain": "robinhood-chain",
    "address": "0xREPLACE_WITH_40_HEX_CHARACTERS"
  }
}

{
  "tool": "inspect_deployer",
  "input": {
    "chain": "solana",
    "address": "REPLACE_WITH_VALID_CREATOR_WALLET"
  }
}

{
  "tool": "evaluate_signal",
  "input": {
    "chain": "solana",
    "signal_name": "runner_rate",
    "history": false
  }
}

{
  "tool": "changes_since",
  "input": {
    "chain": "solana",
    "since": "REPLACE_WITH_RECENT_UTC_TIMESTAMP",
    "limit": 50
  }
}

Output contract and data freshness

Responses identify the tool, chain, generation time, evidence and limitations. A report can be available, partial or unavailable. Source timestamps are not the same as the time the answer was assembled. Do not translate missing KOL/holder/deployer coverage into zero activity or a safe token.

{
  "contract_version": 1,
  "tool": "evaluate_token",
  "chain": "solana",
  "generated_at": "2026-10-09T10:00:00Z",
  "status": "partial",
  "evidence": [
    {
      "source": "sol_token_risk",
      "observed_at": null,
      "status": "unavailable",
      "limitations": [
        "Could not verify this factor"
      ]
    }
  ],
  "warnings": [
    "One or more factors could not be checked"
  ],
  "data": {
    "sources": {}
  },
  "next_cursor": null
}

Illustrative contract, not a live token response.

Cursor replay and honest gaps

The sample above uses a placeholder on purpose: a fixed date in documentation would fall outside the journal retention window after 24 hours. Generate your initial timestamp at request time, for example usingnew Date(Date.now() - 600000).toISOString(). For changes_since, start with a UTC since value within the supported 24-hour horizon. Continue with the returned opaque next_cursor bound to your principal, chain and source journal. The journal stores 72 hours for short-term recovery, but the public cursor window is 24 hours. Deployer and KOL updates are not the same as every Solana or RHC transfer.

Every change distinguishes the original event timestamp, the timestamp recorded by the source and when the journal first observed it. When a source is down or its replay completeness is unverified, do not advance the cursor. Retry the same cursor later, or treat an expired window as an explicit research gap rather than a continuous feed.

Errors and retry behavior