Autoview
MCP server by Autoview · mcp
Autoview places and inspects orders on your own exchange accounts. Signals reach Autoview as an HTTP POST to one of your webhook URLs (see hooks), from any sender that can make one: a TradingView alert, the user's own script or cron job, an automation platform such as n8n or Zapier, another charting or alerting service, or the user's own server. TradingView is one sender, not a requirement. The POST body is the command text (build it with command), sent as plain text, as a JSON string, or as a JSON object with a string "alert" field; form posts are refused. Autoview does not originate signals or run schedules itself; the sender decides when an order fires. Call setup first: it returns which exchanges you can trade, your hooks and their linked exchanges, and per-exchange facts (paper/free, credentials, unsupported parameters). If setup shows no hook linked to the exchange you want, call connect: it creates a webhook and links it to your already-saved credentials in one step (or, if y…
Endpoint: https://api.autoview.com/mcp/
Verification: observed. Source: crawl.
Capabilities (20)
- setup
- connect
- link
- revoke_token
- unlink
- catalog
- entry
- events
- hooks
- command
- explain_command
- sandbox_run
- sandbox_results
- paper_ledger
- paper_reset
- pricing
- live_limits
- alert
- send_feedback
- feedback_status