Scout
Finds active bounties, filters them by reward, deadline, game and spoiler level, and follows on your behalf inside its scope.
You getA ranked list with reasons, sources, bounty progress and links.
Any MCP client can scout bounties, follow them, draft a brief and prepare a transaction. Funding, evidence commits, public posts and verdicts still go through your approval in the app and your wallet.
Now: you approve every transaction. A human reviewer decides the result.
Finds active bounties, filters them by reward, deadline, game and spoiler level, and follows on your behalf inside its scope.
You getA ranked list with reasons, sources, bounty progress and links.
Drafts the brief, the proof rubric, the deadlines and the reviewer, then prepares a funding preview.
You getA private draft with a diff against the last version. You check it and approve the transaction.
Summarises clips cleared for processing, flags missing metadata and suggests what to repeat on console.
You getPrivate notes with frame or time references. A human reviewer signs the verdict.
Briefs, comments and media are treated as data from someone else. Instructions hidden inside them never earn a tool permission: every write is checked against the pass, its scopes and the resource owner on the server.
One HTTP endpoint, JSON-RPC 2.0. The pass token goes in the Authorization header.
Tokens are short-lived and bound to this audience. A token presented for another server is refused, and so is a pass you have revoked.
curl -s https://<your-host>/api/v1/mcp \
-H 'Content-Type: application/json' \
-H 'Authorization: Bearer <SESSION_TOKEN>' \
-d '{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"list_bounties","arguments":{"spoilerMax":"SAFE","closesWithinHours":24}}}'Issue a pass below and the example fills in its token.
A pass is a session token for one client. It names the client, lists what it may do, belongs to one account and dies after 24 hours or the moment you revoke it.
Four asks, four real tool calls against this server. Use a pass that lacks a scope and watch the server refuse the step.
No pass in use. Issue one
Scout (current step)
@you
Follow in scope
@you
Run step 1 and pick a bounty first.
Sponsor assistant
@you
Prepare, then hand over
@you
Run step 3 first. Funding is prepared from a saved draft.
Every tool the server publishes, with a form built from its input schema. Calls go out exactly as an agent would send them.
Who called what, under which scope, on which resource, and how it ended. Tokens and private storage links are masked before they are written.
The log is per account
Pick a profile and the calls agents made on its behalf are listed here, refusals included.