aictrl

connects

aictrl.dev

Governance layer for AI coding agents: knowledge-graph grounding, session audit, policy controls.

https://aictrl.dev/mcpOAuthlast checked 3 Sep 2026spoke MCP on 3 of 3 checks (30 days)initialize in 424 ms

Will my client connect?

Decided from what the probe found at the endpoint, and from what each client's own documentation says it can complete. Every row carries the day that documentation was read.

✓Claude CodeConnects

The authorization server advertises RFC 7591 registration, so Claude Code can register itself and sign you in through the browser.

claude mcp add --transport http aictrl https://aictrl.dev/mcp

Claude Code docs · read on 2026-08-30

✓Claude (claude.ai & Desktop)Connects

The authorization server advertises RFC 7591 registration, so Claude (claude.ai & Desktop) can register itself and sign you in through the browser.

Settings → Connectors → Add custom connector, then paste https://aictrl.dev/mcp.

Claude (claude.ai & Desktop) docs · read on 2026-08-30

✓ChatGPTConnects

The authorization server advertises RFC 7591 registration, so ChatGPT can register itself and sign you in through the browser.

Settings → Apps → Advanced settings → Developer mode, then create a connector pointing at https://aictrl.dev/mcp.

ChatGPT docs · read on 2026-08-30

✓CursorConnects

The authorization server advertises RFC 7591 registration, so Cursor can register itself and sign you in through the browser.

{
  "mcpServers": {
    "aictrl": {
      "url": "https://aictrl.dev/mcp"
    }
  }
}

Cursor docs · read on 2026-08-30

✓VS Code (Copilot)Connects

The authorization server advertises RFC 7591 registration, so VS Code (Copilot) can register itself and sign you in through the browser.

{
  "servers": {
    "aictrl": {
      "type": "http",
      "url": "https://aictrl.dev/mcp"
    }
  }
}

VS Code (Copilot) docs · read on 2026-08-30

How to authenticate

Checked against the endpoint by our probe on 3 Sep 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme	OAuth
Issuer	https://aictrl.dev
Dynamic client registration	✓Advertised (RFC 7591)
Client ID Metadata Document	✕Not advertised
PKCE	✓S256
Grant types	authorization_code, refresh_token
Scopes	mcp:access
Protected-resource metadata	✓Published (RFC 9728)
Anonymous access	Refused — credentials required
Documentation	https://app.aictrl.dev/#quick-start

What the probe found

No CORS headers for browser-based clients

A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.

Contract history

No contract recorded yet — the server has not answered an anonymous connection.

Run this server? A verified owner can publish snapshots with their own credentials, and the contract history starts here, marked owner-reported.

mcpi-cli publish https://aictrl.dev/mcp

Get alerted when this contract changes

Depend on this server? Leave an email. No contract is on record here yet, so alerts can only start once one is published — and alerts are being built; signing up is what tells us to hurry.

Prefer a feed reader? This page's contract changes are also an Atom feed.

Own this server?

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

[![MCP status](https://mcpi.app/servers/aictrl/badge.svg)](https://mcpi.app/servers/aictrl)