TMU MCP

Security, with clear limits

Separate access for each student

Account ownership is checked on data and actions. Connection credentials are encrypted at rest and bound to the account and service. Your password stays on the provider’s sign-in page.

Changes have a record

Requested writes bind to an exact payload and request key. Optional review adds confirmation. If a result is uncertain, the system records that uncertainty and must not blindly send again.

Your connector is licensed to you

The Google connector runs in your own Google account. Each download is a compact build carrying a licence for your account, and the service refuses a connector licensed to someone else. Pairing also requires your signed-in account and a one-time code. Code that runs in your account can still be read, so the protection is the service and your account, not secrecy.

AI content is untrusted

School files and email can contain misleading text or instructions. The server tells the AI to treat these as data, but this cannot guarantee that an AI will resist every prompt injection. Use additional write review if you want another confirmation step.

Report an issue

Support contact will be published before sales open.

Do not include passwords, connector keys, private school documents or message contents in a report. Share a time, affected operation and sanitized error code.