Five tools, one of them writes
Four tools read public data. The fifth is the full agent — it can prepare buys, sells, launches and orders, and always hands the transaction back for a person to sign.
The read tools
| Tool | Arguments | Returns |
|---|---|---|
| vectr_get_price | — | Native coin USD price (symbol, usd, formatted) |
| vectr_get_tokens | limit? (default 10) | Top tokens by market cap — full JSON |
| vectr_search_token | query | Tokens matching a name or symbol — full JSON |
| vectr_get_token | address | One token's detail: price, market cap, curve state, volume — full JSON |
- vectr_get_price
- Arguments
- —
- Returns
- Native coin USD price (symbol, usd, formatted)
- vectr_get_tokens
- Arguments
- limit? (default 10)
- Returns
- Top tokens by market cap — full JSON
- vectr_search_token
- Arguments
- query
- Returns
- Tokens matching a name or symbol — full JSON
- vectr_get_token
- Arguments
- address
- Returns
- One token's detail: price, market cap, curve state, volume — full JSON
None of these need VECTR_API_KEY. They are thin wrappers over the public REST endpoints — the JSON you get back is the API response verbatim.
vectr_agent
| Argument | Type | Notes |
|---|---|---|
| prompt | string (required) | Natural-language instruction — research, trade prep, launches, orders, portfolio reads, fee claims |
| model | string? | Model override — defaults to claude-sonnet-4-6; premium models like claude-opus-4-7 are selectable |
- prompt
- Type
- string (required)
- Notes
- Natural-language instruction — research, trade prep, launches, orders, portfolio reads, fee claims
- model
- Type
- string?
- Notes
- Model override — defaults to claude-sonnet-4-6; premium models like claude-opus-4-7 are selectable
Under the hood the tool creates an /agent/job, polls it every 1.5s, and returns the finished response. When the turn produced a transaction, the answer ends with a pointer to sign it at vectr.bot/terminal — the tool deliberately cannot broadcast.
The boundary is the point
An MCP client can ask the agent to prepare anything it can describe — but signing stays in the wallet owner's hands. If a workflow needs fully automated execution, that's the read-write API key path in API → Authentication, not MCP.