Enforcer
connectsapi.instruxi.dev
Authorization for apps and AI agents: allow, deny, or say what would make it an allow.
https://api.instruxi.dev/mcpWebsiteOAuthMCP 2025-11-25v0.9.3last checked 26 Oct 2026spoke MCP on 100% of 89 checks (30 days)initialize in 496 msLast checked 26 Oct 2026
- ✓Answered the MCP handshake (MCP 2025-11-25)
- ✓Auth detected: OAuth
- ✓Lists 7 tools
- ✓No blockers or warnings
- ✓Spoke MCP on 89 of 89 checks (30 days)
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 enforcer https://api.instruxi.dev/mcpClaude 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://api.instruxi.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://api.instruxi.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": {
"enforcer": {
"url": "https://api.instruxi.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": {
"enforcer": {
"type": "http",
"url": "https://api.instruxi.dev/mcp"
}
}
}VS Code (Copilot) docs · read on 2026-08-30
How to authenticate
Checked against the endpoint by our probe on 26 Oct 2026. These are the capabilities the server advertises, not a prediction about any particular client.
| Scheme | OAuth |
|---|---|
| Issuer | https://api.instruxi.dev |
| Dynamic client registration | ✓Advertised (RFC 7591) |
| Client ID Metadata Document | ✓Supported A client identifies itself by a URL to its own metadata, so no registration step is required. |
| PKCE | ✓S256 |
| Grant types | authorization_code, refresh_token, urn:ietf:params:oauth:grant-type:token-exchange, client_credentials |
| Scopes | enforcer:read, policy:self, enforcer:graph-runs.write, enforcer:graph-observations.write, enforcer:graph-nodes.write, enforcer:graph-edges.write, enforcer:graph-graph-import.write, enforcer:graph-graph-templates.write, enforcer:graph-validation.write, enforcer:graph-graphs.write, enforcer:graph-epochs.write, enforcer:files-files.write, enforcer:files-sharing.write, enforcer:invites.write, enforcer:groups.write, enforcer:group-types.write, enforcer:tickets.write, enforcer:contacts.write, enforcer:connections.write, enforcer:email-templates.write, enforcer:terms.write, enforcer:referrals.write, enforcer:support.write, enforcer:telemetry.write, enforcer:account-policies.write, enforcer:directory.write, enforcer:tenants.write, enforcer:accounts.write, enforcer:wf-jobs.write, enforcer:wf-schedule.write, enforcer:wf-crews.write, enforcer:wf-catalog.write, enforcer:wf-comms.write, enforcer:checkin-checkins.write, enforcer:checkin-waypoints.write, enforcer:checkin-settings.write, enforcer:geo-places.write, enforcer:first-name.write, enforcer:agents.write, enforcer:agents-credentials.write, enforcer:agents-credentials.destructive, enforcer:workspace.write, enforcer:graph-review.write, enforcer:kanban-boards.write, enforcer:kanban-cards.write, enforcer:kanban-columns.write, enforcer:kanban-comments.write, enforcer:kanban-checklists.write, enforcer:kanban-labels.write, enforcer:kanban-attachments.write, enforcer:kanban-photos.write, enforcer:kanban-photo-slots.write, enforcer:kanban-custom-fields.write, enforcer:kanban-cards.destructive, enforcer:files-folders.write, enforcer:kanban-members.write, enforcer:kanban-actions.write, enforcer:kanban-templates.write, enforcer:files-storage.write, enforcer:files-ocr.write, enforcer:governance-annotations.write, enforcer:governance-harness-profiles.write, enforcer:governance-ingest.write, enforcer:governance-settings.write, enforcer:governance-views.write, offline_access |
| Protected-resource metadata | ✓Published (RFC 9728) |
| Anonymous access | Refused — credentials required |
| Documentation | https://docs.instruxi.dev |
What the probe found
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.
Neither the reserved <endpoint>/server-card location nor the domain's /.well-known/ai-catalog.json describes this endpoint (SEP-2127), so a client that discovers servers by domain will not find it.
Tools
Contract history
Watch this server
Save its public contract as a baseline and manage breaking-change email alerts.
Set up a watchRoute it through the gateway
Put this endpoint behind one find_tools / call_tool pair with the rest of your servers. Part of Pro.
Add to my gatewayOwn this server?
Sign in to claim this listing by proving control of its host.
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.
[](https://mcpi.app/servers/enforcer)