Autoview

할 수 있는 일

이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.

• 연결 방식: 클라우드에서 실행
• 전송 방식: Streamable HTTP
• 카테고리: 온라인 쇼핑몰 및 결제
• 입력해야 할 값: Authorization

설치

쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.

필요한 것

• 클라우드에서 실행설치할 것 없음. 인터넷으로 연결돼요

어떤 앱을 쓰세요?

claude mcp add --transport http autoview https://api.autoview.com/mcp/ --header 'Authorization: your-value'

{
  "mcpServers": {
    "autoview": {
      "url": "https://api.autoview.com/mcp/",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

{
  "servers": {
    "autoview": {
      "type": "http",
      "url": "https://api.autoview.com/mcp/",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.

직접 입력할 값

• Authorization 비밀 HTTP header
  Bearer av_mcp_ personal access token from /account/tokens/ -- optional if the client authenticates via OAuth instead.

이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.

할 수 있는 일

도구 이름과 설명은 서버가 2026년 11월 6일에 알려 준 그대로예요. 우리가 아니라 제작자가 쓴 글이고, 일반 텍스트로만 보여 드려요.

• setup

  Read this FIRST. Returns your account overview: token scopes (live/exchange), which exchanges your token can call at all (callable), which of those allow a real live order right now vs. force a dry-run for lack of an active subscription (live_allowed/dry_run_forced, with upgrade_

• connect

  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 rep

• link

  Save a PAPER/TESTNET exchange's API keys to your account and link them to a webhook, in one step -- for an agent that has a practice account's keys and no browser. Only ALPACAPAPER, BINANCEDELIVERYTESTNET, BINANCEFUTURESTESTNET, BINANCETEST, BITGETDEMO, BITGETMIXDEMO, BITMEXTESTN

• revoke_token

  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)

• unlink

  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)

• catalog

  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

• entry

  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,

• events

  Read what your orders did. Pass trace (the id entry or command's caller received) to read one order's events; omit trace to list your account's recent events instead, newest first, optionally narrowed by hook_id and/or canonical_id — this is the only way to see an order any webho

• hooks

  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": "..."}

• command

  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 a

• explain_command

  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 (for example t=p

• sandbox_run

  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: th

• sandbox_results

  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_

• pricing

  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 { cu

• live_limits

  Read this token's live limits: the max order size and daily limit (USD notional = quantity x limit price) 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 no

• alert

  Build everything TradingView's create_alert(webhook, message, expiration, resolution) needs, in one call: fuses `command` (the message) and `hooks` (the webhook URL for hook_id), and fills in the expiration (default 1 year out -- TradingView itself defaults to only 30 days, which

• send_feedback

  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 resp

기본 점검i

누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 7일 점검

• ✓ 통과

  제작자와 저장소 일치

  레지스트리 이름이 도메인 autoview.com 기준으로 확인되었어요(레지스트리가 도메인 소유를 확인해요)

• … 아직 점검 안 함

  계속 관리되고 있음

  아직 GitHub에서 이 저장소를 읽어 오지 않았어요

• … 아직 점검 안 함

  라이선스 있음

  아직 GitHub에서 이 저장소를 읽어 오지 않았어요

• ✓ 통과

  엔드포인트 응답

  278ms 만에 응답(HTTP 200)

• – 해당 없음

  OAuth로 로그인

  로그인 필요 없음

• ✓ 통과

  도구 설명에 숨겨진 지시 없음

  도구 설명 17개를 읽었고, AI에게 보내는 숨겨진 지시는 없었어요

온라인 쇼핑몰 및 결제 카테고리의 다른 서버와 비교i

• 이 카테고리의 다른 서버 1748개 중 0%보다 스타가 많아요
• 이 카테고리의 다른 서버 1748개 중 89%보다 최근에 레지스트리에 공개됐어요
• 기본 점검 결과가 이 카테고리의 다른 서버 1748개 중 100%와 같거나 더 좋아요

레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.

대안

같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.

카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i

제작자의 README

https://api.autoview.com/mcp/