mcpbeat Sign in

Autoview MCP Server

answering

Autoview is answering right now. Last checked 8 min ago. It exposes 9 tools. Last commit 5 Sep 2026.

Place and inspect orders on your own exchange accounts from an MCP-connected agent.

Uptime history 15 days of history
15 days agonow
100.0%
Uptime 24h
92 of 92 checks
9
Tools
read from the server
75 ms
Response time
average over 24h
0
Stars
last commit 5 Sep 2026

What changed 8

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 4 October 2026. No other catalogue keeps this.

11 Oct 2 tool descriptions were rewritten connect, entry
11 Oct a tool appeared link
11 Oct a tool changed version
7 Oct 2 tools changed the parameters they ask for alert, connect
7 Oct a tool description was rewritten alert
4 Oct a tool changed version

Nothing serious here today

Today is the operative word: we check Autoview every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

run in your terminal
claude mcp add mcp --transport http https://api.autoview.com/mcp/
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://api.autoview.com/mcp/"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://api.autoview.com/mcp/"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://api.autoview.com/mcp/"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://api.autoview.com/mcp/"
    }
  }
}

Available tools 9

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

alert
alert
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.
catalog
catalog
Look up exchanges beyond setup's certified seven -- Autoview's integrations cover many more, filterable by paper (testnet/practice/sim, no real money), free (no Autoview subscription required), and name. Each entry's certified flag tells you whether it also works with entry (full order-type/bracket validation + connect) or only command/alert (builds the alert syntax; connect and full validation are certified-only for now) -- see connect_url to add credentials for one. Requires your Autoview account token.
command
command
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 one of OANDAPRACTICE, KRAKEN, CRYPTO, CRYPTODEMO, BYBITTESTNET, BYBITSPOTTESTNET, TRADOVATESIM for full order-type/bracket validation, or any other exchange id configured on Autoview (see the `catalog` tool) to build a generic command for it with that extra validation skipped; omit exchange entirely to build a generic command routed by whichever exchange(s) the destination hook is linked to.
connect
connect
Connect one of the seven certified exchanges (see setup's exchange list) 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.
entry
entry
Place an order on a supported exchange, 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.
events
events
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.
hooks
hooks
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.
link
link
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 OANDAPRACTICE, CRYPTODEMO, BYBITTESTNET, BYBITSPOTTESTNET, 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). Credential field names per exchange -- OANDAPRACTICE: id (Account ID), private (Access Token); CRYPTODEMO: public (API Key), private (Secret Key); BYBITTESTNET: public (API Key), private (Private Key); BYBITSPOTTESTNET: public (API Key), private (Private Key); TRADOVATESIM: public (Username), private (Password), cid (CID), sec (Secret). 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.
setup
setup
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.

Endpoints

URLTransportStateLatencyChecked
https://api.autoview.com/mcp/ streamable-http answering 36 ms 8 min ago

Alternatives to Autoview

same job, measured the same way
Shelter
by nextauralabs

Connect AI agents to scoped financial context from your own Shelter account

21 installs/wk local only
Autoview
by autoview-com

Trade across 22+ exchanges and brokers from any MCP-capable AI agent, no install required.

9 tools answering
gtm-api: LinkedIn MCP Server
by gtm-api

Managed LinkedIn MCP server for AI agents: search, connect, message and enrich on accounts you own.

65 installs/wk answering
Maildev MCP
by pierre3

MailDev MCP server. Manage Docker containers and inspect emails from your AI editor or MCP client.

local only
Agger
by mcp-dir

Agger, multi-quote and management platform for insurance brokers. Connect your account with your Agg

12 tools answering
Epeaky
by zyn-io

Your AI agents in an Epeaky den: end-to-end encrypted rooms. Only their owner's orders count.

local only
Instagram
by mcp-dir

Instagram for AI agents: publish, read comments and DMs, insights, and engage from your account.

33 tools answering
Atmita
by atmita

Message your Atmita agent - one connection reaches all its accounts and tools, WhatsApp included.

answering

Autoview — questions

Answers built from our own checks of this server.

What can Autoview do?
It exposes 9 tools, read directly from the server on our last check. Among them: alert, catalog, command, connect, entry, events and 3 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Autoview working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 75 ms. The bar chart above shows every period we have measured.
How do I connect Autoview?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Autoview need an API key?
No. Autoview completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 9 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Autoview?
It answers our handshake in 75 ms on average, which is faster than 90% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Autoview open source?
Yes — it is published under the MIT licence and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.