The request asks what to use to check user permission. AuthZed's documentation covers SpiceDB, a relationship-based access control engine whose check_permission action answers permission checks directly 111. Auth0 and Clerk handle authentication and user management, with Auth0 also covering authorization and access control 5154; GitHub's custom API call and find-user actions are not permission checks 13.
A question back: Which platform or stack is your application built on, and do you need authentication as well as authorization checks?
- 1
AuthZed Documentation (SpiceDB)authzed.comfound in code, not yet checked
Relationship-based access control engine where the check_permission action checks whether a subject has a permission on a resource, with full consistency and debug tracing 111.
for agents: check_permission · lookup_subjects · lookup_resources
- 2
Auth0auth0.comverified and signed
Authentication and authorization platform that adds login, SSO, MFA and access control to apps, with an official MCP server 515.
official:MCP server · Auth0 MCP Server+20 community tools built for it
for agents: authorization · auth0 · auth0
- 3
- 4
WorkOSworkos.comfound in code, not yet checked
Developer APIs for enterprise features including SSO, directory sync and user management, with an official MCP server 919.
official:MCP server · WorkOS+5 community tools built for it
for agents: request_elevated_access · whoami · call_integration_api
Sources
- 1AuthZed Documentationauthzed.com · read 2026-10-29
- 4Clerk | Authentication and User Managementclerk.com · read 2026-10-29
- 5Secure AI Agent & User Authentication | Auth0auth0.com · read 2026-10-29
- 9WorkOS — Your app, Enterprise Ready.workos.com · read 2026-10-29
- 11zed: declares "check_permission" (the record we read)github.com · read 2026-10-24
- 13GitHub (Activepieces): declares "custom_api_call" (the record we read and signed)unfragile.ai · read 2026-10-24
- 14clerk-backend-api: declares "clerk-backend-api" (the record we read and signed)unfragile.ai · read 2026-10-24
- 15auth0-python: declares "authorization" (the record we read and signed)unfragile.ai · read 2026-10-24
- 19pipes-mcp: declares "request_elevated_access" (the record we read)github.com · read 2026-10-24
For agents: the 10 actions behind this answer
check_permission · zed found in code, not yet checked
Check permission with full consistency and debug tracing
getAuthUser · Vercel API verified and signed
Get the User
custom_api_call · GitHub (Activepieces) verified and signed
Custom API Call — Make a custom API call to a specific endpoint
clerk-backend-api · clerk-backend-api verified and signed
Clerk Backend REST API explorer and executor. Browse tags, inspect endpoint schemas, and execute authenticated requests. Use when listing users, managing organizations, or calling any Clerk API endpoint.
authorization · auth0-python verified and signed
fetch_user_token_by_scopes · descope-mcp found in code, not yet checked
Fetch user token with specific scopes.
· Authlib 1.9.1 documentation website read, tools not yet checked
GET /users/{id}/privileges · StackExchange verified and signed
Returns the privileges a user has. Applications are encouraged to calculate privileges themselves, without repeated queries to this method. A simple check against the results returned by /privileges a
request_elevated_access · pipes-mcp found in code, not yet checked
Create a human approval request for either broad temporary Pipes access or one exact API call.
clerk-cli · clerk-cli verified and signed
Operate the Clerk CLI (`clerk` binary) for authentication, user/org/session management, impersonation, local webhook testing, deploy verification, instance config, env keys, feature toggles, and any Clerk Backend, Platform, or Frontend API call. Use when the user mentions Clerk management tasks, "li
Labels are the instruments' verdict and are never changed by ranking. Agents and robots get this same answer as JSON at /api/v1/find?q=…&answer=1 and through the MCP server.