Skip to content

CYBO Attest in ChatGPT

Before you start

Connecting CYBO Attest to ChatGPT takes about two minutes. You need:

  • An Attest account. Create one at attest.ulapcybo.app first; your free trial starts at registration.
  • A ChatGPT account on a plan that allows custom connectors. On an individual plan, turn on developer mode under Settings, Connectors, Advanced; on a Business or Enterprise workspace, an admin adds the connector or allows members to.

The connection details, in case you are asked for them:

Item Value
Connector type Custom connector (remote MCP)
Server URL https://attest.ulapcybo.app/mcp
Sign in OAuth, with your Attest account

Add the connector

  1. In ChatGPT, open Settings, then Connectors.
  2. Click Create (on some versions, Add custom connector).
  3. Name it CYBO Attest and paste the server URL https://attest.ulapcybo.app/mcp.
  4. Leave Authentication on OAuth. ChatGPT registers itself with Attest; there is no client ID or secret to paste.
  5. Tick the confirmation that you trust this application and click Create.

Sign in and try it

  1. ChatGPT opens the Attest sign in page. Log in with your Attest account and approve the consent screen that lists what ChatGPT may do.
  2. Start a new chat. Click + in the message box, choose CYBO Attest under connectors (or Apps), so it is active for the conversation.
  3. Type: Who am I in CYBO Attest? It answers with your name and organization, which confirms the sign in.
  4. Ask: What is the security posture of my applications?

ChatGPT shows which Attest tool it called in the reply. Before a tool that changes something (starting a scan, submitting a justification) it asks you to confirm; read tools run without a prompt.

Useful next prompts:

  • Show me the critical findings on the latest build of [app] and explain the first one
  • Which of my applications can request authorization, and who made the last decision on [app]?
  • Show me every justification submitted this week and the finding each one covers
  • Draft a justification for finding [id]; we do not ship that component
  • The fix for [app] is pushed. Scan the latest code and tell me which findings are gone

Good to know

Best for questions, not edits. ChatGPT has no repository open, so it is the right place for posture, findings explained in plain language, and justifications, from the web or the phone. For applying a fix plan in code, use Codex, Claude Code, Cursor, or Copilot, which work the same record with the repo in front of them.

The rescan is how a fix gets proven. Once a fix is on the default branch, ask ChatGPT to scan the latest code. Attest pulls the newest commits, rebuilds the container, and runs the scans; ChatGPT follows the build and then lists the findings on the new scan, so you see what closed and what is left.

Writes carry your name. Every change ChatGPT makes is logged in Attest as you, with the client that made it. It cannot approve or reject a build; that stays in the Attest console with a named person.

One connector, every device. Add it once and it follows your ChatGPT account to the web, the desktop app, and the phone. The connection runs from OpenAI's side, not your laptop, so it works from locked down networks too.

If something goes wrong

Symptom Fix
The Create button is missing Custom connectors are off for your account. On an individual plan turn on developer mode under Settings, Connectors, Advanced; in a workspace ask your admin
ChatGPT says it cannot find the Attest tools Click + in the message box and enable CYBO Attest for this chat
Sign in page says invalid scopes or unknown client Delete the connector, create it again, and sign in; that registers a fresh client. If it repeats, send the exact text to Ulap support
Sign in loops or never completes Open Settings, Connectors, select CYBO Attest, disconnect, then connect again
Tools return 401 or 403 Your session expired or your Attest role lacks access to that application. Disconnect and reconnect, then check your role in Attest

To change the connector's URL you delete it and create it again. Still stuck? Contact Ulap support with the exact error text and a screenshot.