Authentication
Account keys, twin credentials and webhook secrets.
Three separate secrets
- Account key. Create it at /keys. Your builder sends it to the remote MCP endpoint as
Authorization: Bearer <your account key>. - Provider twin credentials. Temporary credentials your app uses when it calls an isolated twin. Twin rehearsals don't need live vendor keys. A separately authorized live vendor test needs scoped credentials and test destinations.
- Webhook signing secret. Lets your app check that an incoming webhook is genuine.
Where they go
Configure each secret the way your builder guide describes. Keep them in private credentials or config. Never put them in chat or committed source.
A browser connector that discovers tools without a key has not shown that authenticated verification is available.
Keep protection on
Keep webhook protection and signature verification enabled during rehearsals. The rehearsal should exercise the same checks your app runs.
If you get a 401
Check the account key and the Authorization header. Don't swap in a vendor key.
Remote MCP configuration
https://fetchsandbox.com/mcp/v1