Autoview MCP server

• alertFree

  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. Returns warnings you should read, including never putting the hook's key in the message field. 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.

• commandFree

  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. 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 one of OANDAPRACTICE, KRAKEN, CRYPTO, CRYPTODEMO, BYBITTESTNET, BYBITSPOTTESTNET, TRADOVATESIM to also validate order-type/bracket support for that exchange; omit it to build a generic command routed by whichever exchange(s) the destination hook is linked to.

• entryFree

  Place an order on a supported exchange, right now. 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, so this returns { queued, trace } immediately, not the fill — pass the trace to the `events` tool to read what the order did. 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 ever enters this chat. exchange is optional when that hook links to exactly one exchange; pass it explicitly if the hook links to more than one. Requires your Autoview account token.

• eventsFree

  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.

• hooksFree

  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.

• setupFree

  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 support, whether a manual priceRef is required), and your hooks with their linked exchanges. Requires your Autoview account token.

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 1595ms20/20
• Tool poisoning6 tool descriptions checked15/15
• Auth qualityopen endpoint, read-only tools10/15
• Maintenancelast push 15 days ago15/15
• Maintainer identityregistry namespace matches repository owner7/10

Autoview: common questions

Is Autoview MCP server safe?

Yes, by our scan: it is graded A (89/100). Read the Autoview safety report

How do I install Autoview?

It runs remotely at api.autoview.com. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.

Does Autoview need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Autoview maintained?

The last commit was 15 days ago (2026-09-05). The latest release is v1.0.0.

Is Autoview up?

100% of our last 6 checks got an answer. We check remote servers about four times a day.

What can I use instead of Autoview?

Servers from other publishers that do the same job: Skillsmith MCP server, Tetrees MCP server and Agent Lsp MCP server. Compare all Autoview alternatives.