ScorpTech x402 API

Sol Pda

sol_pda

Read-onlyIdempotent

Derive Solana program-derived addresses offline: findProgramAddress (canonical bump search) for any program and typed seeds (utf8, base58 pubkey, hex, u8/u16/u32/u64 little- or big-endian), or the associated token account (ATA) of an owner + mint for SPL Token or Token-2022. Same algorithm as @solana/web3.js (sha256 + ed25519 off-curve check). Useful to locate token accounts, Anchor PDAs and vaults without an RPC. Price: $0.002 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/sol-pda

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sol_pda"
  }
}

Input Schema

Name	Required	Description	Default
`bump`	No	custom: use this bump (createProgramAddress) instead of searching
`mint`	No	ata: token mint
`owner`	No	ata: wallet that owns the token account
`seeds`	No	custom: seeds as "utf8:vault", "pubkey:<base58>", "hex:0a0b", "u8:1", "u64:42", "u32be:7" (no prefix: a 32-byte base58 string is a pubkey, else utf8); JSON array if a seed contains commas
`preset`	No	ata = associated token account of owner + mint; custom = programId + seeds	custom
`programId`	No	custom: program id (base58)
`tokenProgram`	No	ata: SPL Token (default) or Token-2022	token

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.3/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Adds substantial context beyond the annotations: the computation is local/offline ('without an RPC'), matches @solana/web3.js semantics (sha256 + ed25519 off-curve check), costs $0.002 USDC per successful call via x402, and has an HTTPS alternative endpoint. The pricing model and payment protocol in particular are behavioral facts an agent cannot infer from readOnlyHint/idempotentHint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the purpose and the two modes before pricing and endpoint details, and every clause carries information. It is dense to the point of being a single long block, but nothing is clearly redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description could have been more explicit about what comes back (address plus bump? full ATA struct?), though 'derive ... address' implies it. All-optional parameters are disambiguated by the required preset, which the description explains. Overall complete enough to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so each of the 7 parameters is already documented, including the full seed type-prefix grammar and the preset split. The description restates the same typed-seed and ATA concepts without adding syntax or constraints beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Derive Solana program-derived addresses offline') and immediately enumerates the two operations it performs: canonical bump search via findProgramAddress with typed seeds, or the ATA of owner + mint. This distinguishes it clearly from the RPC-based Solana siblings (sol_account, sol_balance, sol_tx_status) by scoping it to offline derivation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete usage context — 'locate token accounts, Anchor PDAs and vaults without an RPC' — and the preset values (custom vs ata) map to the two use cases. It stops short of explicitly saying when to prefer a sibling like sol_account for on-chain lookups versus this offline derivation, so the routing is implied rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ScorpTech x402 API tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?