MCP
MCP Authentication
Keys, permissions and limits for MCP.
API-first financial agents and workflows run in the app. The browser execution examples below document retained legacy interfaces; browser execution is disabled. Use Financial workspace guides for current features.
- Every MCP request must carry Authorization: Bearer <key>. Requests without a valid key get HTTP 401.
- Tool discovery works with any valid key; each tool call checks its own permission and returns an error result if the key lacks it.
- MCP and REST share the 60-requests-per-minute limit per key, and appear together in Developer Settings → Usage & Activity.
- Website content and assistant prompts are treated as untrusted input. They can't change Taken's safety rules or approve trades.