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 · SCANNED SEP 24

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

Available components

remote · api.autoview.com 79
+13 this week 79 Trust /100
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 Security97
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
  • The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
Schema Quality & AI Usability60
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 3452 tokens (~575/item across 6 items; 6 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 Management10
  • Stability check failed: schema churn in the 18 days we've observed: 0 tool removals, 2 breaking changes, 0 auth/transport breaks, 4 additions. See how to fix → Fail
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
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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
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 autoview-com-mcp 'https://api.autoview.com/mcp/'
// .cursor/mcp.json
{
  "mcpServers": {
    "autoview-com-mcp": {
      "url": "https://api.autoview.com/mcp/"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "autoview-com-mcp": {
      "type": "http",
      "url": "https://api.autoview.com/mcp/"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.autoview-com-mcp]
url = "https://api.autoview.com/mcp/"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "autoview-com-mcp": {
      "type": "remote",
      "url": "https://api.autoview.com/mcp/",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add autoview-com-mcp --url 'https://api.autoview.com/mcp/' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  autoview-com-mcp:
    url: "https://api.autoview.com/mcp/"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "autoview-com-mcp": {
      "Transport": "http",
      "Url": "https://api.autoview.com/mcp/"
    }
  }
}
# add to Vellum
assistant mcp add autoview-com-mcp -t streamable-http -u 'https://api.autoview.com/mcp/'
// mcp.json
{
  "mcpServers": {
    "autoview-com-mcp": {
      "type": "http",
      "url": "https://api.autoview.com/mcp/"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 24 Sept 26 0
    • MCP protocol: Implements a current MCP spec version (2026-07-28). functional
    • MCP protocol version: 2025-11-25 → 2026-07-28 functional
  • 23 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7.

  • 20 Sept 26 +11
    • Authorization: unverified → pass ▲ security
    • First check of Authorization: partial security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “command” rewrote its description, which is the text the model reads security
    • Tool “entry” rewrote its description, which is the text the model reads security
    • Tool “events” rewrote its description, which is the text the model reads security
    • Tool “hooks” rewrote its description, which is the text the model reads security
    • Tool “entry” is now declared destructive security
    • Schema quality: 516 → 575 ▼ functional
    • “entry” added a required parameter “hook_id”, so existing callers break ▼ functional
    • “entry” dropped the required parameter “credentials” ▼ functional
    • Server version: 0.1.0 → 0.2.0 functional
    • New tool “alert” functional
    • New tool “setup” functional
    • “events” added an optional parameter “canonical_id” cosmetic
    • “events” added an optional parameter “hook_id” cosmetic
    • “command” reworded the description of “token” cosmetic
    • “entry” reworded the description of “exchange” cosmetic
    • “entry” reworded the description of “token” cosmetic
    • “events” reworded the description of “token” cosmetic
    • “events” reworded the description of “trace” cosmetic
    • “hooks” reworded the description of “token” cosmetic
    • “command” made “token” optional cosmetic
    • “entry” made “exchange” optional cosmetic
    • “entry” made “token” optional cosmetic
    • “events” made “token” optional cosmetic
    • “events” made “trace” optional cosmetic
    • “hooks” made “token” optional cosmetic
  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 9 to 12.

  • 17 Sept 26 +1
    • Tool “entry” rewrote its description, which is the text the model reads security
    • Schema quality: 604 → 516 ▲ functional
    • New tool “command” functional
    • New tool “hooks” functional
  • 15 Sept 26 0
    • “entry” reworded the description of “credentials” cosmetic

    1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.

  • 12 Sept 26 +3
    • Stability: 0.17 → fail ▼ security
    • A breaking change shipped without a version bump: still 0.1.0 ▼ security
    • Schema quality: 234 → 595 ▼ functional
    • “events” changed the type of “limit”: number → integer ▼ functional
    • Tool coverage: 0% → 100% ▲ functional
    • Schema quality: fair → excellent functional
    • “entry” reworded the description of “credentials” cosmetic
    • “entry” reworded the description of “exchange” cosmetic
    • “entry” reworded the description of “live” cosmetic
    • “entry” reworded the description of “price” cosmetic
    • “entry” reworded the description of “priceRef” cosmetic
    • “entry” reworded the description of “quantity” cosmetic
    • “entry” reworded the description of “side” cosmetic
    • “entry” reworded the description of “sizeAgainstEquity” cosmetic
    • “entry” reworded the description of “stopLoss” cosmetic
    • “entry” reworded the description of “symbol” cosmetic
    • “entry” reworded the description of “takeProfit” cosmetic
    • “entry” reworded the description of “token” cosmetic
    • “entry” reworded the description of “trailActivate” cosmetic
    • “entry” reworded the description of “trailFrequency” cosmetic
    • “entry” reworded the description of “trailStop” cosmetic
    • “entry” reworded the description of “trigger” cosmetic
    • “entry” reworded the description of “type” cosmetic
    • “events” reworded the description of “limit” cosmetic
    • “events” reworded the description of “token” cosmetic
    • “events” reworded the description of “trace” cosmetic
  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

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 24 Sept 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 10 Aug 2026 8 Nov 2026 ECDSA 256 ECDSA-SHA256 fd90ca5b518e1e4013699c3ad5006af9
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. present 19718 13 Verified
autoview.com. present 2371 13 Verified
api.autoview.com. Verified address RRset verified with the apex keys
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer resource_metadata="https://api.autoview.com/.well-known/oauth-protected-resource/mcp/" 

Bearer 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

Document https://api.autoview.com/.well-known/oauth-protected-resource/mcp/
Retrieved Yes
Resource https://api.autoview.com/mcp/
Authorisation server https://api.autoview.com/

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 · 6 exposed · ~2,996 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 ~639

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.

NameTypeReqDescription
exchangestring–optional — validate order-type and bracket support against this exchange's capabilities; omit to skip that check
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 limit, post_only, ioc, fok, and stop_limit
priceRefnumber–reference price for percent sizing and brackets
quantity–yesorder size: a positive number (contracts/units), or a percent-of-balance string like "50%" (1-100%)
resolutionstring–chart timeframe TradingView's create_alert needs; defaults to "1" (1 minute)
sidestringyesorder direction
sizeAgainstEquityboolean–for a percent quantity, size against equity instead of available balance (y=equity)
stopLossnumber–attached bracket stop-loss as a POINT distance from the fill; pairs with takeProfit or a trail leg
symbolstringyesthe instrument symbol, e.g. EUR_USD, XBTUSD, BTC_USD
takeProfitnumber–attached bracket take-profit as a POINT distance from the fill; 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 market

No output schema declared.

No examples provided.

command ~646

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.

NameTypeReqDescription
exchangestring–optional — validate order-type and bracket support against this exchange's capabilities; omit to skip that check
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 limit, post_only, ioc, fok, and stop_limit
priceRefnumber–reference price for percent sizing and brackets
quantity–yesorder size: a positive number (contracts/units), or a percent-of-balance string like "50%" (1-100%)
sidestringyesorder direction
sizeAgainstEquityboolean–for a percent quantity, size against equity instead of available balance (y=equity)
stopLossnumber–attached bracket stop-loss as a POINT distance from the fill; pairs with takeProfit or a trail leg
symbolstringyesthe instrument symbol, e.g. EUR_USD, XBTUSD, BTC_USD — or the exchange-native symbol a TradingView EXCHANGE:TICKER maps to
takeProfitnumber–attached bracket take-profit as a POINT distance from the fill; 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 market

No output schema declared.

No examples provided.

entry ~1,035

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.

NameTypeReqDescription
exchangestring–the exchange to trade on; omit when hook_id links to exactly one exchange (see the hooks tool) -- otherwise required to disambiguate
hook_idstringyesuse the credentials already linked to this hook (see the `hooks` tool). The hook must belong to your account.
liveboolean–false (default) = a dry-run preview that returns the parsed order without placing it; true = place a real order on your live account
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–yesorder size: a positive number (contracts/units), or a percent-of-balance string like "50%" (1-100%). On TRADOVATESIM (no live market-data feed), a percent quantity also requires priceRef — see priceR…
sidestringyesorder direction
sizeAgainstEquityboolean–for a percent quantity, size against equity instead of available balance (y=equity)
stopLossnumber–attached bracket stop-loss as a POINT distance from the fill; pair with takeProfit for a fixed OCO, or with a trailing leg. Market entry, bracket-capable exchanges only (Tradovate). On TRADOVATESIM a…
symbolstringyesthe instrument symbol, e.g. EUR_USD, XBTUSD, BTC_USD
takeProfitnumber–attached bracket take-profit as a POINT distance from the fill; pair with stopLoss, or with a trailing leg. On TRADOVATESIM also pass priceRef (or price) — see priceRef.
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; defaults to market. limit/post_only/ioc/fok and stop_limit need a price; stop/stop_limit need a trigger. An entry stop keeps the order side. Not every exchange supports every type (e.g. O…

No output schema declared.

No examples provided.

events ~296

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.

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.

hooks ~195

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.

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.

setup ~185

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.

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.

Common questions

What is the Autoview MCP server?

Autoview is an MCP server listed in the public MCP registry as io.github.autoview-com/mcp. Trade across 22+ exchanges and brokers from any MCP-capable AI agent, no install required. This page covers its hosted endpoint (https://api.autoview.com/mcp/).

Is the Autoview MCP server safe to use?

Autoview scores 79 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 6 tools: setup, entry, events, hooks, command, alert. Their descriptions and schemas cost roughly 2,996 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 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.