Griffin31
HEStart a pilot
HE
Closed beta · Limited seats

See, prove and fix your GitHub, Copilot and Claude Code setup.

AI coding agents now open pull requests, run commands and connect to your systems. Griffin31 is coming to where that happens: connect your GitHub organization, including Copilot, and your Claude Code configuration, and get evidence-backed checks with step-by-step fixes, without having to know in advance what to look for.

Built on the same read-only approach as Griffin31 for Microsoft 365.

Recommendations · Claude Code
FailedLimit the MCP servers Claude Code may connect to
Risk HighImpact MajorEffort Easy
MCP serverDefined inApprovedResult
githubmanaged settingsyesPassed
filesystem.mcp.jsonyesPassed
web-scraperuser settingsnoFailed
db-admin.mcp.jsonnoFailed

2 of 4 servers are on the approved list

Example data. Checks may change before launch.
Why now

AI agents got commit rights. Their settings never got a review.

Coding agents read your repos, run commands, open pull requests and call tools through MCP. The settings that decide what they may do are new, spread across GitHub, the repo and every developer’s laptop, and they change every month. Most teams have never checked them.

Spread across places

Settings live at the organization, the repo and the machine. There is no single place to see it all.

Changing every month

New capabilities and settings ship faster than anyone can read the release notes.

Nobody owns it

It falls between R&D and security, so nobody checks it.

Coverage

What the beta checks

GitHub

  • Enterprise and organization access: SSO, Managed Users, 2FA and owners
  • Repository rules and branch protection
  • Actions and workflow permissions
  • Copilot policies
  • Secret scanning and dependency alerts

Claude Code

  • Managed settings, and who can override them
  • Permission rules: which commands and files the agent may touch
  • MCP servers: approved sources only
  • Hooks and plugins from trusted sources

Planned coverage for the beta. Final checks may differ.

GitHub Copilot

GitHub Copilot for developers

An organization-wide GitHub Copilot license comes with the whole GitHub platform. If your developers only need a coding assistant inside their IDE, close off everything else.

In the beta, Griffin31 is set to check these settings and show, with evidence, what is already closed and what is still open.

  • GitHub for licensing and management only

    Block repository creation, forks, Pages, Actions and external sharing, while your code stays in your existing source control.

  • Identities your organization manages

    Managed accounts provisioned automatically from Entra ID, Conditional Access, and admin roles through PIM.

  • Copilot, restricted

    Approved models only, with web search, MCP servers and unapproved agents blocked.

  • A managed IDE

    VS Code and Visual Studio settings through Intune: approved extensions only, and Copilot with the corporate account only.

  • Network and DLP

    Copilot reaches approved endpoints only, through the corporate proxy, and DLP blocks keys and passwords in prompts to the assistant.

How it works

No need to know what to look for.

  1. 01

    Connect

    Connect your GitHub organization, including Copilot, and your Claude Code configuration, read-only.

  2. 02

    See

    Every result with the evidence behind it: which repo, which setting, which machine.

  3. 03

    Fix

    Step-by-step remediation. Or let OnCloud’s architects fix it with you.

Waitlist

Get on the list.

We’re opening the beta to a small group of teams first. Tell us a little about your setup, and we’ll reach out when your seat is ready.

  • Early access before general release
  • A direct line to the people building it
  • Your feedback shapes the checks
What do you use today?

By joining you agree to our Privacy Policy.