# Autoview (remote · api.autoview.com)

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

- Trust score: 79/100 (medium)
- Change this week: +13
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-24

## Components

- remote · `api.autoview.com`: 79/100 (this document), [markdown](https://verifymcp.io/servers/autoview-com-mcp/api.md), [page](https://verifymcp.io/servers/autoview-com-mcp/api)

## Channel facts

- Endpoint: `https://api.autoview.com/mcp/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-24.

- **Endpoint Security**: 97/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability check failed: schema churn in the 18 days we've observed: 0 tool removals, 2 breaking changes, 0 auth/transport breaks, 4 additions.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## 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.

### Claude

```bash
claude mcp add --transport http autoview-com-mcp 'https://api.autoview.com/mcp/'
```

### Cursor

```json
{
  "mcpServers": {
    "autoview-com-mcp": {
      "url": "https://api.autoview.com/mcp/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "autoview-com-mcp": {
      "type": "http",
      "url": "https://api.autoview.com/mcp/"
    }
  }
}
```

### Codex

```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
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add autoview-com-mcp --url 'https://api.autoview.com/mcp/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  autoview-com-mcp:
    url: "https://api.autoview.com/mcp/"
```

### Netclaw

```json
{
  "McpServers": {
    "autoview-com-mcp": {
      "Transport": "http",
      "Url": "https://api.autoview.com/mcp/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add autoview-com-mcp -t streamable-http -u 'https://api.autoview.com/mcp/'
```

### Other

```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 recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-24 (score 79, 0)

- [functional] MCP protocol: Implements a current MCP spec version (2026-07-28).
- [functional] MCP protocol version: 2025-11-25 → 2026-07-28

### 2026-09-23 (score 79, +1)

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

### 2026-09-20 (score 78, +11)

- [security improvement] 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
- [functional regression] Schema quality: 516 → 575
- [functional regression] “entry” added a required parameter “hook_id”, so existing callers break
- [functional regression] “entry” dropped the required parameter “credentials”
- [functional] Server version: 0.1.0 → 0.2.0
- [functional] New tool “alert”
- [functional] New tool “setup”
- [cosmetic] “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

### 2026-09-19 (score 67, +1)

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

### 2026-09-17 (score 66, +1)

- [security] Tool “entry” rewrote its description, which is the text the model reads
- [functional improvement] Schema quality: 604 → 516
- [functional] New tool “command”
- [functional] New tool “hooks”

### 2026-09-15 (score 65, 0)

- [cosmetic] “entry” reworded the description of “credentials”

### 2026-09-12 (score 65, +3)

- [security regression] Stability: 0.17 → fail
- [security regression] A breaking change shipped without a version bump: still 0.1.0
- [functional regression] Schema quality: 234 → 595
- [functional regression] “events” changed the type of “limit”: number → integer
- [functional improvement] Tool coverage: 0% → 100%
- [functional] Schema quality: fair → excellent
- [cosmetic] “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”

### 2026-09-11 (score 62, +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.

## MCP tools (6)

### `setup` (~185 tokens)

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.

Input parameters:

- `token` (string): 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…

### `entry` (~1035 tokens)

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.

Input parameters:

- `exchange` (string): the exchange to trade on; omit when hook_id links to exactly one exchange (see the hooks tool) -- otherwise required to disambiguate
- `hook_id` (string, required): use the credentials already linked to this hook (see the `hooks` tool). The hook must belong to your account.
- `live` (boolean): false (default) = a dry-run preview that returns the parsed order without placing it; true = place a real order on your live account
- `price` (number): 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.
- `priceRef` (number): 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` (required): order 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…
- `side` (string, required): order direction
- `sizeAgainstEquity` (boolean): for a percent quantity, size against equity instead of available balance (y=equity)
- `stopLoss` (number): 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…
- `symbol` (string, required): the instrument symbol, e.g. EUR_USD, XBTUSD, BTC_USD
- `takeProfit` (number): 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.
- `token` (string): 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…
- `trailActivate` (number): POINTS of profit the price must move before the trailing stop starts trailing (atx=). Required whenever trailStop is set
- `trailFrequency` (number): how often the trailing stop re-checks price (atf=); defaults to 1 if omitted
- `trailStop` (number): 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…
- `trigger` (number): absolute trigger (stop) price; required for stop and stop_limit
- `type` (string): 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…

### `events` (~296 tokens)

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.

Input parameters:

- `canonical_id` (string): when trace is omitted, narrow the account-wide listing to events reported for one webhook delivery (the canonical id a webhook call produces)
- `hook_id` (string): when trace is omitted, narrow the account-wide listing to events reported for this hook
- `limit` (integer): max events to return (default 20)
- `token` (string): 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…
- `trace` (string): the trace id returned by the entry tool for the order you want to inspect; omit to list your account's recent events instead

### `hooks` (~195 tokens)

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.

Input parameters:

- `token` (string): 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…

### `command` (~646 tokens)

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.

Input parameters:

- `exchange` (string): optional — validate order-type and bracket support against this exchange's capabilities; omit to skip that check
- `live` (boolean): false (default) = build a dry-run preview command (appends d=1); true = build a command that places a real order when the alert fires
- `price` (number): absolute limit price; required for limit, post_only, ioc, fok, and stop_limit
- `priceRef` (number): reference price for percent sizing and brackets
- `quantity` (required): order size: a positive number (contracts/units), or a percent-of-balance string like "50%" (1-100%)
- `side` (string, required): order direction
- `sizeAgainstEquity` (boolean): for a percent quantity, size against equity instead of available balance (y=equity)
- `stopLoss` (number): attached bracket stop-loss as a POINT distance from the fill; pairs with takeProfit or a trail leg
- `symbol` (string, required): the instrument symbol, e.g. EUR_USD, XBTUSD, BTC_USD — or the exchange-native symbol a TradingView EXCHANGE:TICKER maps to
- `takeProfit` (number): attached bracket take-profit as a POINT distance from the fill; pairs with stopLoss or a trail leg
- `token` (string): 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…
- `trailActivate` (number): points of profit before the trail starts; required whenever trailStop is set
- `trailFrequency` (number): how often the trailing stop re-checks price; defaults to 1 if omitted
- `trailStop` (number): auto-trail stop distance in points; requires trailActivate
- `trigger` (number): absolute trigger (stop) price; required for stop and stop_limit
- `type` (string): order type; defaults to market

### `alert` (~639 tokens)

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.

Input parameters:

- `exchange` (string): optional — validate order-type and bracket support against this exchange's capabilities; omit to skip that check
- `expiration` (string): ISO 8601 timestamp for TradingView's alert expiration; defaults to 1 year from now
- `hook_id` (string, required): the hook whose URL becomes the alert's webhook (see the `hooks` tool)
- `live` (boolean): false (default) = build a dry-run preview command (appends d=1); true = build a command that places a real order when the alert fires
- `price` (number): absolute limit price; required for limit, post_only, ioc, fok, and stop_limit
- `priceRef` (number): reference price for percent sizing and brackets
- `quantity` (required): order size: a positive number (contracts/units), or a percent-of-balance string like "50%" (1-100%)
- `resolution` (string): chart timeframe TradingView's create_alert needs; defaults to "1" (1 minute)
- `side` (string, required): order direction
- `sizeAgainstEquity` (boolean): for a percent quantity, size against equity instead of available balance (y=equity)
- `stopLoss` (number): attached bracket stop-loss as a POINT distance from the fill; pairs with takeProfit or a trail leg
- `symbol` (string, required): the instrument symbol, e.g. EUR_USD, XBTUSD, BTC_USD
- `takeProfit` (number): attached bracket take-profit as a POINT distance from the fill; pairs with stopLoss or a trail leg
- `token` (string): 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…
- `trailActivate` (number): points of profit before the trail starts; required whenever trailStop is set
- `trailFrequency` (number): how often the trailing stop re-checks price; defaults to 1 if omitted
- `trailStop` (number): auto-trail stop distance in points; requires trailActivate
- `trigger` (number): absolute trigger (stop) price; required for stop and stop_limit
- `type` (string): order type; defaults to market

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/autoview-com-mcp/api#diagnostics

## Score history

- 2026-09-24: 79
- 2026-09-23: 79
- 2026-09-22: 78
- 2026-09-21: 78
- 2026-09-20: 78
- 2026-09-19: 67
- 2026-09-18: 66
- 2026-09-17: 66
- 2026-09-16: 65
- 2026-09-15: 65
- 2026-09-14: 65
- 2026-09-13: 65
- 2026-09-12: 65
- 2026-09-11: 62
- 2026-09-10: 61
- 2026-09-09: 61
- 2026-09-08: 60
- 2026-09-07: 60
- 2026-09-06: 59

## 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.

## Links

- Remote endpoint: https://api.autoview.com/mcp/
- Repository: https://github.com/autoview-com/mcp
- Website: https://autoview.com/
- Changelog RSS feed: https://verifymcp.io/servers/autoview-com-mcp/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/autoview-com-mcp/api.json
- HTML version of this page: https://verifymcp.io/servers/autoview-com-mcp/api