Autoview
by autoview.com · remote · no sign-in to list tools · v0.4.0 · published by com.autoview
Place and inspect orders on your own exchange accounts from an MCP-connected agent.
9 tools: 1 can delete or cancel things, 4 change things and 4 only read.
Scanned Oct 21, 2026
- Deletes or cancels1Claude Code: deny: see these tools
- Can't be undone0Claude Code: ask
- Changes things4Claude Code: ask: see these tools
- Only reads4Claude Code: allow: see these tools
9 checks matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.
claude mcp add --transport http autoview https://api.autoview.com/mcp/Findings
Matches of fixed checks, with the text they matched.
- Infosetup
The description mentions "credential".
What this check looks forMatched text
description: "...money venue, its setup_url and required credential labels), and your hooks with their link..."
- Infoconnect
The description mentions "credentials".
What this check looks forMatched text
description: "...hook and links it to your already-saved credentials for that exchange, the same steps 2-4 t..."
- Infolink
The description mentions "credentials".
What this check looks forMatched text
description: "...iew.com in a browser (see connect). The credentials object uses named keys (public, private..."
- Infolink
The input schema at properties.credentials.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.credentials.description: "...e fields the chosen exchange takes. The credentials object uses named keys (public, private..."
- Infolink
The input schema at required[1] mentions "credentials".
What this check looks forMatched text
inputSchema.required[1]: "credentials"
- Infocatalog
The description mentions "credentials".
What this check looks forMatched text
description: "...ry, command, alert and connect once its credentials are linked to one of your hooks (the ex..."
Show 3 more findingsShow fewer
- Infocatalog
The input schema at properties.exchange.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.exchange.description: "...ACTICE" or "oanda-practice") to get its credential schema and facts instead of the list; p..."
- Infoentry
The description mentions "Credentials".
What this check looks forMatched text
description: "...canonical_id (or trace) a moment later. Credentials come from hook_id -- the credentials yo..."
- Infoentry
The input schema at properties.hook_id.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.hook_id.description: "use the credentials already linked to this hook (see the `h..."
Tools
Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.
9 tools
Deletes or cancels 1Claude Code: deny
entryPlace an order on any exchange you have linked to a hook, right now — or manage existing orders/positions on `symbol` via `action` (cancel open orders, close open positions, or fla…2 findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
Findings
- Info
The description mentions "Credentials".
What this check looks forMatched text
description: "...canonical_id (or trace) a moment later. Credentials come from hook_id -- the credentials yo..."
- Info
The input schema at properties.hook_id.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.hook_id.description: "use the credentials already linked to this hook (see the `h..."
Description, as the server wrote it Place an order on any exchange you have linked to a hook, right now — or manage existing orders/positions on `symbol` via `action` (cancel open orders, close open positions, or flat/liquidate everything — Tradovate only). You fill structured order fields (symbol, side, quantity, type, price, trigger) — Autoview assembles the order for you. Dry-run by default: a bare call returns the parsed order without placing it; set live:true to place a real order. On a paid exchange without an active Autoview subscription, live:true is silently downgraded to a dry-run — the response then carries dry_run_forced:true and a dry_run_reason explaining why (see the `setup` tool for which exchanges this applies to, and where to subscribe). The order is relayed to the exchange asynchronously: this returns { queued, trace, canonical_id } immediately, not the fill. For a dry-run (the default), entry waits up to ~10s for the exchange's own reply and returns it as dry_run_events when it arrives in time — otherwise dry_run_pending:true, and you can poll the `events` tool with canonical_id (or trace) a moment later. Credentials come from hook_id -- the credentials you already linked to one of your hooks (see the `hooks` or `setup` tool) -- so no exchange secret is passed with the order. exchange is optional when that hook links to exactly one exchange; pass it explicitly if the hook links to more than one. If you don't have credentials linked yet, use the `command` tool to check an order's shape without a hook. Requires your Autoview account token.
Annotations the server declares
- destructiveHint: true
- openWorldHint: true
- readOnlyHint: false
- title: Place an order
Changes things 4Claude Code: ask
alertBuild everything TradingView's create_alert(webhook, message, expiration, resolution) needs, in one call: fuses `command` (the message) and `hooks` (the webhook URL for hook_id), a…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Build everything TradingView's create_alert(webhook, message, expiration, resolution) needs, in one call: fuses `command` (the message) and `hooks` (the webhook URL for hook_id), and fills in the expiration (default 1 year out -- TradingView itself defaults to only 30 days, which silently stops the alert) and resolution (default "1") TradingView also needs. The order is validated against the exchange(s) hook_id is actually linked to and rejected if it could never fire there. Returns warnings you should read, including never putting the hook's key in the message field and a fan-out warning when the hook links more than one exchange. Dry-run by default like `command`; set live:true to build a command that trades for real once the alert fires. Requires your Autoview account token.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Build a TradingView alert
commandBuild an Autoview alert command string from structured order fields (symbol, side, quantity, type, price, trigger) without placing an order — the output is the value TradingView's …No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Build an Autoview alert command string from structured order fields (symbol, side, quantity, type, price, trigger) without placing an order — the output is the value TradingView's create_alert `message` field should carry. Also builds cancel/close/flat management commands via `action` (see entry's description). Dry-run by default: a bare call returns a preview command (appends d=1); set live:true to build a command that trades for real once TradingView fires the alert. Prefer the `alert` tool if you also need the destination webhook, expiration, and resolution in one call. Requires your Autoview account token — live:true requires a live-scoped token. exchange is optional: pass any exchange id configured on Autoview (see the `catalog` tool; a bracket is refused if that exchange lists sl/tp as unsupported); omit exchange entirely to build a generic command routed by whichever exchange(s) the destination hook is linked to.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Build an alert command
connectConnect any exchange configured on Autoview (see catalog) to your account: creates a webhook and links it to your already-saved credentials for that exchange, the same steps 2-4 th…1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...hook and links it to your already-saved credentials for that exchange, the same steps 2-4 t..."
Description, as the server wrote it Connect any exchange configured on Autoview (see catalog) to your account: creates a webhook and links it to your already-saved credentials for that exchange, the same steps 2-4 the website's setup wizard runs. Safe to call more than once -- if a webhook is already linked, it reports connected:true and creates nothing new. If you have no credentials saved for this exchange yet, returns connect_url instead: open it in a browser to add them, then call connect again with the same exchange (for a paper/testnet exchange you can instead call link with its keys; real-money keys are browser-only). Connecting a real-money (non-paper) exchange requires a live-scoped token; any token can connect a paper/testnet exchange. Requires your Autoview account token.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: false
- title: Connect an exchange
linkSave a PAPER/TESTNET exchange's API keys to your account and link them to a webhook, in one step -- for an agent that has a practice account's keys and no browser.3 findings
Why it is in this group
- The name "link" says "link": a word for a change.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...iew.com in a browser (see connect). The credentials object uses named keys (public, private..."
- Info
The input schema at properties.credentials.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.credentials.description: "...e fields the chosen exchange takes. The credentials object uses named keys (public, private..."
- Info
The input schema at required[1] mentions "credentials".
What this check looks forMatched text
inputSchema.required[1]: "credentials"
Description, as the server wrote it Save a PAPER/TESTNET exchange's API keys to your account and link them to a webhook, in one step -- for an agent that has a practice account's keys and no browser. Only ALPACAPAPER, BINANCEDELIVERYTESTNET, BINANCEFUTURESTESTNET, BINANCETEST, BITGETDEMO, BITGETMIXDEMO, BITMEXTESTNET, BYBITCOPYTESTNET, BYBITSPOTTESTNET, BYBITTESTNET, CAPITALDEMO, CRYPTODEMO, DERIBITTESTNET, GATEFUTURESTESTNET, GEMINISANDBOX, HYPERLIQUIDTESTNET, OANDAPRACTICE, OKXDEMO, OKXEEADEMO, OKXUSDEMO, TRADOVATESIM are accepted (they never move real money); real-money exchanges are refused whatever your token's scope, and their keys must be added on autoview.com in a browser (see connect). The credentials object uses named keys (public, private, passphrase, email, vault, id, cid, sec); which of them an exchange takes, and what each is called on that exchange, is in catalog({ exchange }): its credentials schema lists the exact keys (titles are the exchange's own labels) and which are required. The keys are encrypted and stored exactly as the website's setup form stores them, and are never echoed back. hook_id, if given, must be one of your own hooks with no exchange linked yet (an order fires on every exchange a hook links); omit it to use an empty hook of yours or get a new one. Then call entry with the returned hook_id (dry-run by default) to check the keys work. Requires your Autoview account token; any token can link a paper exchange.
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
- readOnlyHint: false
- title: Link paper exchange keys
Only reads 4Claude Code: allow
catalogList every exchange configured on Autoview, filterable by paper (testnet/practice/sim, no real money), free (no Autoview subscription required), and name.2 findings
Why it is in this group
- The description's first verb is "list": a word for reading.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...ry, command, alert and connect once its credentials are linked to one of your hooks (the ex..."
- Info
The input schema at properties.exchange.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.exchange.description: "...ACTICE" or "oanda-practice") to get its credential schema and facts instead of the list; p..."
Description, as the server wrote it List every exchange configured on Autoview, filterable by paper (testnet/practice/sim, no real money), free (no Autoview subscription required), and name. Every listed exchange works with entry, command, alert and connect once its credentials are linked to one of your hooks (the exchange itself validates the order); linkable ones also take paper keys via link -- see connect_url to add credentials for one. Pass exchange (any spelling of its id, e.g. "OANDAPRACTICE") to get that one exchange in detail instead of the list: credentials is a JSON Schema whose property keys are exactly the keys link takes (titles are the exchange's own labels, required lists the ones it needs), plus linkable and unsupported_parameters (command parameters the exchange rejects, e.g. sl/tp; an attached bracket using one is refused up front). Requires your Autoview account token.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Browse the exchange catalog
eventsRead what your orders did.No findings
Why it is in this group
- The description's first verb is "read": a word for reading.
Description, as the server wrote it Read what your orders did. Pass trace (the id entry or command's caller received) to read one order's events; omit trace to list your account's recent events instead, newest first, optionally narrowed by hook_id and/or canonical_id — this is the only way to see an order a TradingView (or other webhook) alert fired directly, since it never went through entry and has no trace. Requires your Autoview account token. Poll this a moment after an order if the events are not there yet — the exchange reports back out-of-band.
Annotations the server declares
- destructiveHint: false
- openWorldHint: false
- readOnlyHint: true
- title: Read order events
hooksList your Autoview webhook URLs — the destination for a TradingView (or any other) alert's webhook field.No findings
Why it is in this group
- The description's first verb is "list": a word for reading.
Description, as the server wrote it List your Autoview webhook URLs — the destination for a TradingView (or any other) alert's webhook field. Each hook already knows which exchange(s) it is linked to; there is nothing further to configure on the Autoview side. Pair with the `command` tool (or use `alert` to build both at once). Requires your Autoview account token. The returned URL is itself a bearer secret for unattended trading — treat it like a password; rotate a hook's key from /account/hooks/ on the Autoview site if it leaks.
Annotations the server declares
- destructiveHint: false
- openWorldHint: false
- readOnlyHint: true
- title: List webhook URLs
setupRead this FIRST.1 finding
Why it is in this group
- The description's first verb is "read": a word for reading.
Findings
- Info
The description mentions "credential".
What this check looks forMatched text
description: "...money venue, its setup_url and required credential labels), and your hooks with their link..."
Description, as the server wrote it Read this FIRST. Returns your account overview: token scopes (live/exchange), which exchanges your token can call at all (callable), which of those allow a real live order right now vs. force a dry-run for lack of an active subscription (live_allowed/dry_run_forced, with upgrade_url when forced), per-exchange facts (supported order types, symbol format example, bracket/flat support, whether a manual priceRef is required, whether it's a free paper/no-real-money venue, its setup_url and required credential labels), and your hooks with their linked exchanges. If no hook is linked to any exchange yet, recommended_first_exchange points at a free paper venue to start with. failing_hooks flags any hook whose last several alerts all failed with the SAME error (a stuck webhook loop). Requires your Autoview account token.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Account overview
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Install
Pinned to version 0.4.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http autoview https://api.autoview.com/mcp/Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__autoview__setup",
"mcp__autoview__catalog",
"mcp__autoview__events",
"mcp__autoview__hooks"
],
"ask": [
"mcp__autoview__connect",
"mcp__autoview__link",
"mcp__autoview__command",
"mcp__autoview__alert"
],
"deny": [
"mcp__autoview__entry"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as autoview. Review it before you use it.