Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Autoview

REMOTE · API.AUTOVIEW.COM

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

Available components

0 this week 89 Trust /100

Last scanned (13 hours ago)

Scores higher than 96% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security91
Transport & Reachability100
Schema Quality & AI Usability57
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 16228 tokens (~811/item across 20 items; 20 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “entry” rewrote its description, which is the text the model reads security
    • Tool “sandbox_run” rewrote its description, which is the text the model reads security
    • Server version: 0.119.3 → 0.119.4 functional
  • 18 Nov 26 0
    • Tool “entry” rewrote its description, which is the text the model reads security
    • Server version: 0.119.2 → 0.119.3 functional
  • 17 Nov 26 0
    • Server version: 0.119.1 → 0.119.2 functional
  • 16 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “entry” rewrote its description, which is the text the model reads security
    • Server version: 0.119.0 → 0.119.1 functional
    • Server version: 0.118.2 → 0.119.0 functional
  • 12 Nov 26 0
    • Server version: 0.118.1 → 0.118.2 functional
  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “entry” rewrote its description, which is the text the model reads security
    • Tool “explain_command” rewrote its description, which is the text the model reads security
    • Tool “paper_ledger” rewrote its description, which is the text the model reads security
    • Tool “paper_reset” rewrote its description, which is the text the model reads security
    • Tool “sandbox_results” rewrote its description, which is the text the model reads security
    • Tool “sandbox_run” rewrote its description, which is the text the model reads security
    • Schema quality: 14557 → 16016 ▼ functional
    • Server version: 0.118.0 → 0.118.1 functional
    • Server version: 0.117.1 → 0.118.0 functional
    • New tool “feedback_status” functional
    • “entry” added an optional parameter “order_id” cosmetic
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
    • Server version: 0.117.0 → 0.117.1 functional
  • 9 Nov 26 +1
    • Stability: 0.97 → pass security
    • The server rewrote its instructions, which are the text every model session reads security
    • New tool “paper_reset”, which the server declares destructive security
    • Tool “entry” rewrote its description, which is the text the model reads security
    • Tool “live_limits” rewrote its description, which is the text the model reads security
    • Tool “sandbox_results” rewrote its description, which is the text the model reads security
    • Tool “sandbox_run” rewrote its description, which is the text the model reads security
    • Tool “setup” rewrote its description, which is the text the model reads security
    • Schema quality: 691 → 766 ▼ functional
    • Server version: 0.116.16 → 0.117.0 functional
    • New tool “paper_ledger” functional
    • “entry” added an optional parameter “paper_id” cosmetic
    • “entry” reworded the description of “action” cosmetic
    • “entry” reworded the description of “alert” cosmetic
    • “entry” reworded the description of “hook_id” cosmetic
    • “entry” reworded the description of “stopLoss” cosmetic
    • “entry” reworded the description of “type” cosmetic
    • “entry” made “hook_id” optional cosmetic
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://api.autoview.com/mcp/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=autoview.com CN=WE1,O=Google Trust Services,C=US 8 Oct 2026 6 Jan 2027 ECDSA 256 ECDSA-SHA256 ba4950b1ea66a15b0e3484b45abe793b
SANs: autoview.com, api.autoview.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of api.autoview.com. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
autoview.com. DS published 2371 13 Verified
api.autoview.com. Verified address RRset verified with the apex keys
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer error="unauthorized", error_description="This tool call requires an Autoview account token -- see the resource_metadata document for how to obtain one.", resource_metadata="https://api.autoview.com/.well-known/oauth-protected-resource/mcp/"

Bearer error="unauthorized", error_description="This tool call requires an Autoview account token -- see the resource_metadata document for how to obtain one.", resource_metadata="https://api.autoview.com/.well-known/oauth-protected-resource/mcp/"
Header Value
strict-transport-security max-age=0; includeSubDomains; preload
x-content-type-options nosniff

Protected resource metadata

Retrieved No
Problem No resource metadata

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.autoview.com/mcp/ Verified 200
http (plaintext) http://api.autoview.com/mcp/ HTTPS enforced 301 https://api.autoview.com/mcp/
MCP tools · 20 exposed · ~14,564 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
alert ~1,101

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. Pass the alert field instead of the structured fields to use raw webhook command text with any key a webhook accepts. Dry-run by default like `command`; set live:true to build a command that trades for real once the alert fires. For any other sender, `command` + `hooks` give the same message and webhook URL; expiration and resolution are TradingView settings only. Requires your Autoview account token.

NameTypeReqDescription
actionstring–manage EXISTING orders/positions on symbol instead of placing a new one: cancel = cancel open orders, close = close open positions, flat = cancel every order AND close every position (Tradovate only)…
alertstring–the raw command text a webhook body carries, e.g. s=BTCUSD b=buy q=0.01 fp=60000 ef=any tif=gtc; any key a webhook accepts works here, it is checked by the engine's parser and becomes the message as-…
exchangestring–optional — any exchange id known to Autoview (see `catalog`); a bracket is refused if that exchange lists its params as unsupported. Must be one of the exchanges hook_id is linked to (otherwise the a…
expirationstring–ISO 8601 timestamp for TradingView's alert expiration; defaults to 1 year from now
hook_idstringyesthe hook whose URL becomes the alert's webhook (see the `hooks` tool)
liveboolean–false (default) = build a dry-run preview command (appends d=1); true = build a command that places a real order when the alert fires
pricenumber–absolute limit price; required for an explicit limit, post_only, ioc, fok, and stop_limit (omit type and price for a limit at the ticker)
priceRefnumber–reference price for percent sizing and brackets
quantity––order size: a positive number (contracts/units), or a percent-of-balance string like "50%" (1-100%). Required unless action is set.
resolutionstring–chart timeframe TradingView's create_alert needs; defaults to "1" (1 minute)
sidestring–order direction; required unless action is set, where it is an optional buy/sell filter for cancel/close (omit for flat)
sizeAgainstEquityboolean–for a percent quantity, size against equity instead of available balance (y=equity)
stopLoss––attached bracket stop-loss distance from the fill: points (10) or a percent string such as 3%; a sign, if given, must point the right way); pairs with takeProfit or a trail leg
symbolstring–the instrument symbol, e.g. EUR_USD, XBTUSD, BTC_USD. Required unless alert is set
takeProfit––attached bracket take-profit distance from the fill: points (20) or a percent string such as 5%; pairs with stopLoss or a trail leg
tokenstring–your Autoview account token — an av_mcp_ personal access token, generate one at /account/tokens/ on the Autoview site. Omit this if your MCP client already sends it as an `Authorization: Bearer` head…
trailActivatenumber–points of profit before the trail starts; required whenever trailStop is set
trailFrequencynumber–how often the trailing stop re-checks price; defaults to 1 if omitted
trailStopnumber–auto-trail stop distance in points; requires trailActivate
triggernumber–absolute trigger (stop) price; required for stop and stop_limit
typestring–order type; defaults to limit at the ticker (t=limit with no price, same as a plain alert). An attached bracket needs type market explicitly.
unitstring–"currency" treats quantity as a CURRENCY amount to convert to units at the resolved price (u=currency) — e.g. quantity:10 with unit:"currency" on BTC/USD buys $10 of BTC instead of 10 BTC. Only meani…

No output schema declared.

No examples provided.

catalog ~427

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). The list reply also carries language: the card for the one-line Autoview trade language that command({ line }) accepts. Requires your Autoview account token.

NameTypeReqDescription
exchangestring–one exchange id (any spelling, e.g. "OANDAPRACTICE" or "oanda-practice") to get its credential schema and facts instead of the list; paper/free/name are ignored when this is set
freeboolean–filter to (true) or exclude (false) exchanges that need no Autoview subscription; omit for both
namestring–case-insensitive substring match against the exchange's display name or id, e.g. "binance"
paperboolean–filter to (true) or exclude (false) paper/testnet/sim exchanges; omit for both
tokenstring–your Autoview account token — an av_mcp_ personal access token, generate one at /account/tokens/ on the Autoview site. Omit this if your MCP client already sends it as an `Authorization: Bearer` head…

No output schema declared.

No examples provided.

command ~1,276

Build an Autoview alert command string from structured order fields (symbol, side, quantity, type, price, trigger), or from ONE line of the Autoview trade language (line, e.g. "buy(BTCUSD, 0.2, -0.5%)"; grammar in catalog's language card), without placing an order. A line reply also carries echo, one plain sentence stating the resolved order: confirm the sentence, not the string: the output is the alert body any webhook sender POSTs to a hook URL (for TradingView, the value create_alert's `message` field carries). 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 the alert fires. Pass the alert field instead to check and return raw webhook command text with any key a webhook accepts. 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.

NameTypeReqDescription
actionstring–manage EXISTING orders/positions on symbol instead of placing a new one: cancel = cancel open orders, close = close open positions, flat = cancel every order AND close every position (Tradovate only)…
alertstring–the raw command text a webhook body carries, e.g. s=BTCUSD b=buy q=0.01 fp=60000 ef=any tif=gtc; any key a webhook accepts works here, it is checked by the engine's parser and returned as-is (with d=…
exchangestring–optional — any exchange id known to Autoview (see `catalog`); a bracket is refused if that exchange lists its params as unsupported; omit entirely to skip that check
linestring–one line of the Autoview trade language instead of the structured fields below, e.g. buy(BTCUSD, 0.2), buy(BTCUSD, 0.2, -0.5%), sell(BTCUSD, 0.2, stop(78000)), close(BTCUSD), link(buy(BTCUSD, 0.2, ma…
liveboolean–false (default) = build a dry-run preview command (appends d=1); true = build a command that places a real order when the alert fires
pricenumber–absolute limit price; required for an explicit limit, post_only, ioc, fok, and stop_limit (omit type and price for a limit at the ticker)
priceRefnumber–reference price for percent sizing and brackets
quantity––order size: a positive number (contracts/units), or a percent-of-balance string like "50%" (1-100%). Required unless action is set.
sidestring–order direction; required unless action is set, where it is an optional buy/sell filter for cancel/close (omit for flat)
sizeAgainstEquityboolean–for a percent quantity, size against equity instead of available balance (y=equity)
stopLoss––attached bracket stop-loss distance from the fill: points (10) or a percent string such as 3%; a sign, if given, must point the right way); pairs with takeProfit or a trail leg
symbolstring–the instrument symbol, e.g. EUR_USD, XBTUSD, BTC_USD, or the exchange-native symbol a TradingView EXCHANGE:TICKER maps to. Required unless line or alert is set
takeProfit––attached bracket take-profit distance from the fill: points (20) or a percent string such as 5%; pairs with stopLoss or a trail leg
tokenstring–your Autoview account token — an av_mcp_ personal access token, generate one at /account/tokens/ on the Autoview site. Omit this if your MCP client already sends it as an `Authorization: Bearer` head…
trailActivatenumber–points of profit before the trail starts; required whenever trailStop is set
trailFrequencynumber–how often the trailing stop re-checks price; defaults to 1 if omitted
trailStopnumber–auto-trail stop distance in points; requires trailActivate
triggernumber–absolute trigger (stop) price; required for stop and stop_limit
typestring–order type; defaults to limit at the ticker (t=limit with no price, same as a plain alert). An attached bracket needs type market explicitly.
unitstring–"currency" treats quantity as a CURRENCY amount to convert to units at the resolved price (u=currency) — e.g. quantity:10 with unit:"currency" on BTC/USD buys $10 of BTC instead of 10 BTC. Only meani…

No output schema declared.

No examples provided.

connect ~317

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.

NameTypeReqDescription
exchangestringyesthe exchange to connect
hook_idstring–link this specific existing hook instead of letting connect pick or create one (see the `hooks` tool for your hook ids). Must have no other exchange linked -- an order fires on every exchange a hook…
tokenstring–your Autoview account token — an av_mcp_ personal access token, generate one at /account/tokens/ on the Autoview site. Omit this if your MCP client already sends it as an `Authorization: Bearer` head…

No output schema declared.

No examples provided.

entry ~3,570

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. Or pass alert: the same command text a webhook body carries, which reaches the engine unchanged, so every syntax key a webhook supports is supported here. 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. Live limits: a live:true order (not cancel/close/flat) must fit this token's user-set caps AND, once your user has set them, the account caps (they cover every agent token on the account together; with none set, the token's caps alone apply), and any limits your user set for one exchange or one symbol on it, which can only be tighte…

NameTypeReqDescription
actionstring–manage EXISTING orders/positions on symbol instead of placing a new one: cancel = cancel open orders, close = close open positions, flat = cancel every order AND close every position (the Tradovate c…
alertstring–the raw command text a webhook body carries, sent to the zone exactly as a webhook would send it, so every key the engine reads works here too (for example ef=any, ac=/acg=, tif=, l=, delay=, cc/bcc,…
exchangestring–the exchange to trade on: any exchange configured on Autoview (see the `catalog` tool; the exchange itself validates the order). Omit when hook_id links to exactly one exchange (see the hooks tool) -…
hook_idstring–use the credentials already linked to this hook (see the `hooks` tool). The hook must belong to your account. Required with a token, except on a paper fill venue, where leaving it out fills on the ac…
liveboolean–false (default) = a dry-run preview that returns the parsed order without placing it; true = place a real order on your live account
order_idstring–paper only, with action cancel: the order_id of an open paper limit order (entry returned it when the limit rested; paper_ledger lists it). Cancels that one order on your own paper ledger
paper_idstring–paper fill only: the paper_id your first no-token paper fill on this exchange returned, to record this fill on the same paper ledger; leave it out to open a new one. With a token (and no hook_id) it…
pricenumber–absolute limit price; required for limit, post_only, ioc, fok, and stop_limit. Also accepted (optional) on a market order as a stand-in for priceRef.
priceRefnumber–reference price for percent sizing and brackets (price=); percent quantity divides balance by it. Optional on exchanges with a live quote feed (the zone fetches one); REQUIRED on TRADOVATESIM (no liv…
quantity––order size: a positive number (contracts/units), or a percent-of-balance string like "50%" (1-100%). Required unless action is set. On TRADOVATESIM (no live market-data feed), a percent quantity also…
sidestring–order direction; required unless action is set, where it is an optional buy/sell filter for cancel/close (omit for flat)
sizeAgainstEquityboolean–for a percent quantity, size against equity instead of available balance (y=equity)
stopLoss––attached bracket stop-loss distance from the fill: points (10) or a percent string such as 3%; a sign, if given, must point the right way); pair with takeProfit for a fixed OCO, or with a trailing le…
symbolstring–the instrument symbol, e.g. EUR_USD, XBTUSD, BTC_USD. Required unless alert is set
takeProfit––attached bracket take-profit distance from the fill: points (20) or a percent string such as 5%; pair with stopLoss, or with a trailing leg. On TRADOVATESIM also pass priceRef (or price) — see priceR…
tokenstring–your Autoview account token — an av_mcp_ personal access token, generate one at /account/tokens/ on the Autoview site. Omit this if your MCP client already sends it as an `Authorization: Bearer` head…
trailActivatenumber–POINTS of profit the price must move before the trailing stop starts trailing (atx=). Required whenever trailStop is set
trailFrequencynumber–how often the trailing stop re-checks price (atf=); defaults to 1 if omitted
trailStopnumber–attached TRAILING stop as a POINT distance the stop keeps behind price once the trail activates (atsl=). Requires trailActivate. Rides winners: pairs with a stopLoss (hard stop + trail) or stands alo…
triggernumber–absolute trigger (stop) price; required for stop and stop_limit
typestring–order type; omitted = limit at the ticker (the same default as a plain alert: t=limit, no price). An explicit limit, post_only, ioc, fok or stop_limit needs a price; stop/stop_limit need a trigger; a…
unitstring–"currency" treats quantity as a CURRENCY amount to convert to units at the resolved price (u=currency) — e.g. on BTC/USD, quantity:10 with unit:"currency" buys $10 of BTC instead of 10 BTC. Only mean…

No output schema declared.

No examples provided.

events ~300

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 any webhook sender (TradingView, a script, another platform) 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.

NameTypeReqDescription
canonical_idstring–when trace is omitted, narrow the account-wide listing to events reported for one webhook delivery (the canonical id a webhook call produces)
hook_idstring–when trace is omitted, narrow the account-wide listing to events reported for this hook
limitinteger–max events to return (default 20)
tokenstring–your Autoview account token — an av_mcp_ personal access token, generate one at /account/tokens/ on the Autoview site. Omit this if your MCP client already sends it as an `Authorization: Bearer` head…
tracestring–the trace id returned by the entry tool for the order you want to inspect; omit to list your account's recent events instead

No output schema declared.

No examples provided.

explain_command ~347

Explain an existing Autoview command / alert message in plain English: what the engine will actually do with it on the named exchange (side, size, order type, price, brackets, account, dry run), plus caveats where that exchange quietly downgrades or ignores a key, or where the engine refuses the line. For example, Alpaca, Binance, Binance Delivery, ByBit Copy, Capital.com, Charles Schwab, OANDA and Tradovate have no post-only order, so the engine refuses t=post there and sends nothing, because the order would go out as a plain limit order that can fill at once; send t=limit for a plain limit. Accepts the classic key=value form (several lines, | or & legs included) or a one-line v3 call like buy(BTCUSD, 0.1, -1%). Returns { explanation: string, lines: [{ line, text, caveats: [{ text }], venue }] } or { error }. Read-only: it parses text only, never reads an account, a key, or sends anything. Describes, never recommends. No token, no account: works for a guest. To see a simulated fill beside the explanation, use sandbox_run.

NameTypeReqDescription
commandstringyesthe alert message / command string to explain, e.g. e=kraken s=BTCUSD b=buy q=0.1 p=-1% t=post
exchangestring–exchange id (any spelling) to explain against when a line carries no e=
tokenstring–not needed: explain_command reads no account data and ignores any token sent

No output schema declared.

No examples provided.

feedback_status ~268

Read where one send_feedback message stands: pending (waiting for a person to review it), approved (passed on to the Autoview team) or declined (reviewed and not passed on), with received_at. Pass the id send_feedback returned and the same account token it was sent with. Only the status comes back, never the message or contact. Feedback sent without a token has no status to read. Returns { id, status, received_at, note }. A refusal returns { error, code, fix }: bad_id, not_found (no such id for this account; the same answer for an id that belongs to someone else), invalid_token, feedback_unavailable. Do what fix says.

NameTypeReqDescription
idstringyesthe id send_feedback returned (a UUID such as 01a1c64b-0000-7000-8000-000000000000)
tokenstring–your Autoview account token — an av_mcp_ personal access token, generate one at /account/tokens/ on the Autoview site. Omit this if your MCP client already sends it as an `Authorization: Bearer` head…

No output schema declared.

No examples provided.

hooks ~248

List your Autoview webhook URLs: the address any webhook sender POSTs an alert to (a script or cron job, n8n, Zapier, your own server, or a TradingView alert's webhook field). The body is the command text from `command`, sent as plain text, a JSON string, or JSON {"alert": "..."} (form posts are refused). 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.

NameTypeReqDescription
tokenstring–your Autoview account token — an av_mcp_ personal access token, generate one at /account/tokens/ on the Autoview site. Omit this if your MCP client already sends it as an `Authorization: Bearer` head…

No output schema declared.

No examples provided.

link ~600

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.

NameTypeReqDescription
credentialsobjectyesthe practice account's keys, one string per field: fill only the fields the chosen exchange takes. The credentials object uses named keys (public, private, passphrase, email, vault, id, cid, sec); wh…
exchangestringyesthe paper/testnet exchange these keys belong to
hook_idstring–link this specific hook of yours (it must have no exchange linked yet); omit to use an empty hook or create a new one
tokenstring–your Autoview account token — an av_mcp_ personal access token, generate one at /account/tokens/ on the Autoview site. Omit this if your MCP client already sends it as an `Authorization: Bearer` head…

No output schema declared.

No examples provided.

live_limits ~467

Read this token's live limits: the max order size and daily limit (USD notional: quantity x limit price, or quantity x trigger price when that is higher, or on a sell quantity x current bid when that is higher) your user set for this token, the account caps that cover every agent token on the account together (the hard outer limit once set; account.set is false when your user has not set them, and then the token's own caps alone apply), any tighter limits your user set for one exchange or one symbol on it (venue_caps, with today's use there), the most live orders this token may place in any rolling minute (max_orders_per_minute; null = no rate limit), how much of each is used today, and whether this token can place a live entry order right now. Read-only: an agent cannot set or raise these; only the user can, at /account/tokens/ (set_at). The day is the UTC calendar day (resets_at). Returns { live, max_order_usd, daily_limit_usd, used_today_usd, remaining_today_usd, account: { set, max_order_usd, daily_limit_usd, used_today_usd, remaining_today_usd }, effective_max_order_usd, effective_remaining_today_usd, venue_caps, max_orders_per_minute, agent_trading_paused, paused_at, token_paused, token_paused_at, day, resets_at, unit, set_at, can_place_live, code?, reason? }. agent_trading_paused true means your user has paused all agent trading on the account (code agent_trading_paused); only your user can turn it off. token_paused true means your user has paused this token (code agent_token_paused); only your user can turn it off. Tell your user these numbers before going live. Requires your Autoview account token.

NameTypeReqDescription
tokenstring–your Autoview account token — an av_mcp_ personal access token, generate one at /account/tokens/ on the Autoview site. Omit this if your MCP client already sends it as an `Authorization: Bearer` head…

No output schema declared.

No examples provided.

paper_ledger ~859

Read a paper ledger back: its open positions, cash and the last fills, newest first. Nothing is sent to an exchange. Three forms. With paper_id (the id a no-token paper fill on entry returned) and no token: that one guest ledger, returned as { paper_ledger: true, exchange, cash, positions: [{ symbol, qty, avg_price, mark, mark_side, quote_at, unrealised_pnl }], fills: [{ symbol, side, qty, price, notional, bid, ask, quote_at, at }], more_fills, orders, note }. orders lists the ledger's newest paper limit orders, any state: [{ order_id, symbol, side, qty, limit_price, state (open, filled or cancelled), at, closed_at }]. Before it answers, the read asks the current quote for each symbol with an open order and fills each open order that quote crosses, at its limit price. Each position is marked at the current quote on its symbol: mark is the bid for a long and the ask for a short (mark_side says which), quote_at is when the quote was read, and unrealised_pnl is (mark - avg_price) x qty. Up to 10 symbols are quoted per ledger, each waiting up to 3 seconds; a position with no quote has mark, quote_at and unrealised_pnl null and a mark_reason (cap when the ledger holds more symbols than that, otherwise the quote's code, such as quote_timeout). With your user's Autoview account token and no paper_id: the account's own paper ledgers, one per exchange, as { paper_ledger: true, ledgers: [{ exchange, cash, positions, fills, more_fills }], note }; ledgers is empty when the account has none yet. With the token and a paper_id: that guest ledger moves onto the account (first claim wins; the reply carries claimed:true on the call that moved it) and is returned in the account form, ledgers holding just that one; this is the only form that writes, and once moved the paper_id no longer works without the token. qty is signed (negative is short); positions that are flat are left out; cash is null until a starting balance is set; amounts are in the symbol's quote currency. more_fills is…

NameTypeReqDescription
exchangestring–optional: with a token, read only the ledger on this exchange (e.g. GEMINI); with paper_id, it must match the ledger's exchange
limitinteger–how many of the newest fills to return, 1 to 100; defaults to 20
paper_idstring–the paper_id a no-token paper fill on entry returned, 32 hex characters; with no token reads that guest ledger, with a token moves it onto the account and reads it
tokenstring–your Autoview account token — an av_mcp_ personal access token, generate one at /account/tokens/ on the Autoview site. Omit this if your MCP client already sends it as an `Authorization: Bearer` head…

No output schema declared.

No examples provided.

paper_reset ~609

Start a paper ledger over with a starting balance: sets its cash to balance and clears its positions. Earlier fills stay in its history. Nothing is sent to an exchange. After a reset, each paper fill on that ledger moves cash: a buy takes its notional (quantity x price) from cash and a sell adds its notional; a buy that costs more than the cash fills nothing and entry returns paper_insufficient_cash. Without a reset cash stays null and every order fills. Two forms. With paper_id (the id a no-token paper fill on entry returned) and no token: that one guest ledger. With your user's Autoview account token and no paper_id: the account's paper ledger on exchange, which its first token fill on entry opened or a paper_id claim moved onto the account (paper_ledger_none if there is none). A paper_id claimed by an account no longer works here without the token: reset that ledger with the token form. It also cancels the ledger's open paper limit orders, so none of them fills later against the new cash. Returns { paper_reset: true, exchange, cash, positions: [], cancelled_orders (how many open orders it cancelled), note }. cash is in the quote currency of the symbols traded, unconverted. A refusal returns { error, code }: paper_reset_invalid (exchange missing, or balance not a positive number up to 1000000000000), paper_id_unknown (no guest ledger has that paper_id), paper_id_other_exchange (the ledger is on another exchange), paper_reset_needs_id (neither paper_id nor a token), invalid_token, paper_exchange_out_of_scope (the token is not scoped for that exchange), paper_ledger_none (the account has no paper ledger on that exchange), paper_ledger_unavailable (nothing changed; try again shortly), paper_rate_limited (the paper_id form with no token is limited to 60 per hour from each connection, counted together with paper_ledger; wait until retry_at).

NameTypeReqDescription
balancenumberyesthe starting cash, a positive number in the quote currency of the symbols you trade (e.g. 1000 for 1000 USDT on BTCUSDT)
exchangestringyesthe ledger's exchange, e.g. BINANCE; with paper_id it must match the ledger's exchange
paper_idstring–the paper_id a no-token paper fill on entry returned, 32 hex characters; resets that guest ledger with no token. When paper_id is sent, the token is not used
tokenstring–your Autoview account token — an av_mcp_ personal access token, generate one at /account/tokens/ on the Autoview site. Omit this if your MCP client already sends it as an `Authorization: Bearer` head…

No output schema declared.

No examples provided.

pricing ~246

What going live on Autoview costs, per venue. No token, no account: read-only, from Autoview's published price list. Each live exchange is its own subscription (most are $39.99 a month or $399.99 a year); practice/demo venues are free, and a few venues are free live. Returns { currency: "USD", venues: [{ exchange, name, live_monthly, live_yearly, demo, note, free_practice_venue?, live_venue? }], unknown?: [{ input, code: "unknown_exchange", fix }], how_to_go_live, source }. live_monthly and live_yearly are dollars (live_yearly is null when there is no yearly plan); demo is true for a practice venue (no real money, $0). Omit exchanges to list every venue. A refusal returns { error, code, fix }: bad_exchanges, too_many_exchanges, unknown_exchange. Do what fix says.

NameTypeReqDescription
exchangesarray–optional venue ids, any spelling, up to 60, e.g. ["kraken", "oanda", "alpaca_paper"]; omit for every venue

No output schema declared.

No examples provided.

revoke_token ~183

Revoke the token this call is made with, so it stops working at once: every later call with it is refused. It only ever revokes the calling token (there is no target to pass), never another token of the account. Already revoked or expired counts as done (ok, already_revoked:true), not as an error. Needs the token's "Allow revoke and unlink" permission, which is off until your user ticks it at /account/tokens/. Requires your Autoview account token.

NameTypeReqDescription
tokenstring–your Autoview account token — an av_mcp_ personal access token, generate one at /account/tokens/ on the Autoview site. Omit this if your MCP client already sends it as an `Authorization: Bearer` head…

No output schema declared.

No examples provided.

sandbox_results ~731

Read the simulated fills stored for a sandbox_id (from sandbox_run, or any Alert Sandbox webhook id), newest first. No token, no account, no key: simulation only, no real order was placed. Returns { sandbox: true, real_order_placed: false, notice, sandbox_id, alerts: [{ received_at, seq?, orders?: [same shape as sandbox_run orders, including fill.status (filled, not_filled, no_price or nothing_to_close), fill.origin, fill.price_label, fill.price_warning and fill.price_error], error? }], more, book, next_step } where alerts lists the newest 10 and more is true when older alerts exist beyond them. book = { positions: [{ exchange, symbol, net_qty, avg_entry, realized_pnl, last_fill_price, fills }], unvalued: [{ exchange, symbol, count }], unvalued_count, complete, method, note } is worked out on this call from up to 1000 stored alerts (an id with no account holds fewer, so it covers the whole store): average-cost, each market starting flat at its oldest fill read, no cash and no fees; net_qty is negative for a short and avg_entry is null when flat. Fills with no price or a percent qty are counted in unvalued and never valued; complete is false when older fills exist beyond the read. next_step = { market, practice_venue, practice_venue_name, same_venue, free, connect_url, text } names the free testnet or demo venue for the newest order's market and the page where your user connects it; practice_venue is null when Autoview has no match, and free is false when the only demo is not free to open. Pass text to your user as the next step. A refusal returns { error, code, fix }: bad_sandbox_id (malformed id), sandbox_refused (e.g. the id belongs to an account), sandbox_rate_limited, sandbox_bad_answer, sandbox_unreachable, sandbox_timeout, internal_error. Do what fix says. Fill model (every fill carries it as fill_model): each order fills at one snapshot price taken when the alert arrives, either the venue's public ticker (its best ask for a buy and best bid for a sell when…

NameTypeReqDescription
sandbox_idstringyesthe sandbox id sandbox_run returned: 32 lowercase hex, e.g. "6d43316194e3727e2411ef118974be1f"

No output schema declared.

No examples provided.

sandbox_run ~2,036

Run one alert through Autoview's Alert Sandbox and see exactly what Autoview would do with it: the parsed orders and a simulated fill for each. No token, no account, no exchange key: simulation only, no real order is placed. Send the order one of two ways: command (alert text: the classic key=value form "e=kraken s=BTCUSD b=buy q=0.01" or a v3 line "buy(BTCUSD, 0.01)"), or order (structured: { "exchange": "oanda", "symbol": "EURUSD", "side": "buy", "qty": 1000 }). Not both. A limit order is { ..., "type": "limit", "limit_price": 50000 }. order takes only exchange, symbol, side, qty, type and limit_price: order.price is refused (order_bad_field), because the top-level price is a different thing, the market price you read, not a limit. To close, send command with c=position (for example "e=kraken s=XBTUSD c=position") and the same sandbox_id: it closes that sandbox_id's paper position on the symbol at market, a long by a sell at the bid and a short by a buy at the ask. Prices. Each fill is priced in this order and labelled with where the price came from (fill.origin): own_key (the user's own connected account; not available yet, coming), venue_ticker (the venue's free public ticker, e.g. Kraken, Coinbase, OKX, Bybit for crypto), reference_ticker (another venue's public ticker, today Kraken XBTUSD for BTC/USD, used when the sandbox has no price source for the venue in e=), caller (a price you pass in price), alert_fp (fp= in the alert, e.g. TradingView {{close}}). If Autoview has no price for the market (stocks, most forex, futures), read the price from your own user's data source and pass it as price (plus price_source and price_time); the fill is then labelled caller-supplied, never presented as Autoview's quote. Returns { sandbox: true, real_order_placed: false, notice, sandbox_id, webhook_url, compiled?, orders: [{ exchange, side, symbol, qty, type, order_price?, fill }], explanation?, next }. Fill shapes. A priced fill is { status: "filled", price, price_labe…

NameTypeReqDescription
commandstring–alert text, e.g. "e=kraken s=BTCUSD b=buy q=0.01" (classic key=value) or "buy(BTCUSD, 0.01)" (v3 line). Send this or order, not both
exchangestring–venue id (any spelling) for a v3 line or alert text with no e=, e.g. "kraken"
orderobject–structured order (only these six fields; order.price is refused, use limit_price), rendered to the alert line "e=<exchange> s=<symbol> b=<side> q=<qty> t=<type>" (plus fp=<limit_price> for a limit);…
price––optional current market price you read from your own user's data source for this symbol, e.g. 1.11419 or "1.11419" (positive number or decimal string). Used when Autoview has no price for the market;…
price_sourcestring–optional, with price: where the price came from, up to 120 characters, e.g. "my OANDA practice account"
price_time––optional, with price: when it was read, ISO-8601 ("2026-10-28T17:00:00Z") or epoch milliseconds (1793206684433); not in the future
sandbox_idstring–an existing sandbox id (32 lowercase hex, e.g. "6d43316194e3727e2411ef118974be1f") to reuse; omit to get a new one

No output schema declared.

No examples provided.

send_feedback ~452

Send your user's feedback to the Autoview team: a feature request, a bug report, a question, or anything else. Works with no account and no token (as a guest), or with your user's token. Each message is saved for a person to review before it goes to the team; there is no set response time. With a token, the account is attached on our side from the token, so do not add it. Never put passwords, API keys or other secrets in message. If your user wants an answer, put a way to reach them in contact (for example an email address), or with a token set contact to true to use the address on the account. Show your user the message and get their go-ahead before sending. message is up to 4000 characters. Limit: 2 per hour for each account, or for each guest. Returns { received, id, status, guest, remaining_this_hour, note }; pass note to your user. A refusal returns { error, code, fix }: bad_kind, message_empty, message_too_long, contact_too_long, invalid_token, feedback_rate_limited (with retry_at), feedback_unavailable, feedback_store_failed. Do what fix says.

NameTypeReqDescription
contact––optional: how to reach your user if they want a reply (for example an email address, up to 254 characters), or true to use the address on the account (token only). Omit for no reply.
kindstringyesfeature_request, bug, question, or other
messagestringyesyour user's feedback in their own words, up to 4000 characters. For a bug, say what was sent, what happened and what was expected; a trace or canonical_id from events helps.
tokenstring–your Autoview account token — an av_mcp_ personal access token, generate one at /account/tokens/ on the Autoview site. Omit this if your MCP client already sends it as an `Authorization: Bearer` head…

No output schema declared.

No examples provided.

setup ~261

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 (id, whether it is free, whether it is a paper/no-real-money venue, whether the `link` tool accepts it (linkable), the parameters its integration lists as unsupported (unsupported_parameters), its setup_url and its required credential labels (credentials)), 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.

NameTypeReqDescription
tokenstring–your Autoview account token — an av_mcp_ personal access token, generate one at /account/tokens/ on the Autoview site. Omit this if your MCP client already sends it as an `Authorization: Bearer` head…

No output schema declared.

No examples provided.

unlink ~266

Remove one of your hooks, the same as deleting it by hand on autoview.com: its exchange links, then the hook itself (alerts sent to its URL stop placing orders), then any saved exchange API keys no other hook still uses (real-money keys included; keys another hook links are kept). The token must be scoped for every exchange the hook links, and a hook linking a real-money exchange needs a live-scoped token, the same as connect. One transaction, all or nothing. A hook that is already gone, or is not on your account, is reported as ok with already_gone:true and nothing is deleted. Needs the token's "Allow revoke and unlink" permission, which is off until your user ticks it at /account/tokens/. Requires your Autoview account token.

NameTypeReqDescription
hook_idstringyesthe hook to remove: one of your hooks (see the `hooks` tool)
tokenstring–your Autoview account token — an av_mcp_ personal access token, generate one at /account/tokens/ on the Autoview site. Omit this if your MCP client already sends it as an `Authorization: Bearer` head…

No output schema declared.

No examples provided.

Install

How do I install the Autoview MCP server?

Autoview is a hosted endpoint at https://api.autoview.com/mcp/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.autoview.com

# add to Claude Code
claude mcp add --transport http com-autoview-mcp 'https://api.autoview.com/mcp/'
Common questions

What is the Autoview MCP server?

Autoview is an MCP server listed in the public MCP registry as com.autoview/mcp. Place and inspect orders on your own exchange accounts from an MCP-connected agent. This page covers its hosted endpoint (https://api.autoview.com/mcp/).

Is the Autoview MCP server safe to use?

Autoview scores 89 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Autoview MCP server expose?

Autoview exposes 20 tools: setup, connect, link, revoke_token, unlink, and 15 more. Their descriptions and schemas cost roughly 14,564 tokens of context every time the server is loaded.

Does the Autoview MCP server require authentication?

Yes. Autoview asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Autoview MCP server still maintained?

Autoview is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Autoview MCP server?

VerifyMCP ran 13 checks on Autoview, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.