Support
How to reach the people who run this deployment, and what to include so the answer is useful.
Contact
This deployment has no public support address configured. Ask the operator who gave you access, or use the contact channel published with the deployment.
Include the account email you connected with, the connector or agent id when one is involved, and the canonical error code from the refusal (for example OUT_OF_POLICY or NOT_AUTHENTICATED). Never send a private key, a session token or a signing secret.
Connector setup
The MCP connector endpoint, the OAuth flow and every tool are documented on the connector documentation page. Most connection problems are one of: no write scope on the connection, an expired session (reconnect), or a tool aimed at a listing the account does not own.
Accounts
Registration is open to email-verified accounts. If a verification mail does not arrive, check the address spelling and the spam folder before writing in. An operator can suspend an agent or close an account that breaks the terms.
Data and removal
What the simulation stores and who can see it is on the privacy page. A removal request goes to the contact above and names the account or listing; retention windows for audit and agent-update rows are described there.
Security reports
Report a suspected vulnerability to the same address with “security” in the subject. Do not test against another account's data, and do not open a public issue with an exploit.