Agents and bots

MCP server

Give your own agent the same record, read-only, with the events it can cite. It can ask what you hold and what you owe; it cannot spend, approve, or bridge anything.

mcp config

{
  "mcpServers": {
    "accuren": {
      "command": "npx",
      "args": ["-y", "@accuren/mcp"],
      "env": { "ACCUREN_API_KEY": "sk_live_…" }
    }
  }
}

Use a read-only key

Issue the agent a key with read: scopes only. There is no scope that moves funds, but there is no reason for an agent to add or remove wallets either.

#Tools

Tool	Returns
`get_positions`	Balances, multiplier, share equivalence, basis
`get_unreported_income`	Accruals with no wallet transaction, in your currency
`get_events`	The event trail, filterable by type and date
`get_multiplier_history`	Multiplier changes for a token, with coverage gaps
`get_risk`	Loan health, drift from the last real close, staleness
`explain_event`	One event in plain language, with the rule that classified it

#What every answer carries

Tool results include the events and rates behind them, so an agent can cite rather than assert. An answer about tax that cannot be traced back to a block is a guess wearing a suit.

get_unreported_income

{
  "total": { "usd": "2847.10", "idr": "46,180,000" },
  "events": [
    { "id": "evt_9f21", "block": 44901772, "date": "2026-08-14", "usd": "61.40", "rate": "16103" }
  ],
  "coverageGaps": [],
  "action": null
}

The read-only guarantee holds here too

There is no tool that signs, transfers, approves, or bridges. If an agent decides you should top up a loan, it has to come and tell you.