# ORE program

The ORE program comprehended: its program graph (which PDAs derive from what), instruction planning, and PDA derivation, so a call names the right accounts first time.

- Surface: `ore` (program), access: open, served now
- Origin: the ORE program on Solana mainnet
- MCP endpoint: https://mcp.geckovision.tech/ore/mcp
- HTML page: https://geckovision.tech/catalog/ore

## Use cases

### See what the program can do and what each account needs

Ask: "Which ORE instructions can I plan, and what do their accounts derive from?"

Tools, in order: `get_program_graph`, `plan_instruction`, `derive_pda`

## Get started

```bash
claude mcp add --transport http ore https://mcp.geckovision.tech/ore/mcp
```

First call: `get_program_graph` with `{}`.

Raw MCP over HTTP, the order for money paths, and the definition of done: https://geckovision.tech/agents.md

## Tools served now

Measured at 2026-09-02T03:01:24.610Z (server ore 1.28.1): 3 tools.

- `get_program_graph`: Return the full instruction↔PDA derivation graph for this Solana program: every instruction, which of its accounts are program-derived (PDAs), and how each PDA 
- `plan_instruction`: Return the friction-free build plan for one instruction: which PDA accounts to derive, in dependency order, and what each is derived from (which accounts / args
- `derive_pda`: Derive a program-derived address (PDA) for this program. Give the account name (e.g. 'miner') and any seed bindings it needs — accounts as base58 pubkeys, integ