A
licenseNot graded
qualityB
maintenanceEnforces fine-grained, context-aware access control on MCP tool calls, with a tamper-evident, replayable audit log that records denials and verifies every decision.
MIT
Enforcer
Server Details
Identity and authorization in one system: allow, deny, the reason, and a record.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 33.0% over 43 days
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP
- URL
TDQS
A4.4/5.0
Scored across 7 tools
Disambiguation5/5
Each tool has a clearly distinct role: auth config discovery, SIWE nonce issuance, login, token refresh, registration, and OTP request by channel. The only adjacent pair, requestOtp and requestSms, is cleanly separated by email versus phone.
Naming Consistency4/5
Most tools follow a verb_noun camelCase pattern like getAuthConfig, getSiweNonce, requestOtp, and refreshToken. The bare verbs login and register are minor deviations but are conventional auth actions, so the set remains predictable.
Tool Count5/5
Seven tools is well-scoped for an authentication-focused server. Each tool addresses a necessary step in the auth lifecycle without redundancy or filler.
Completeness4/5
The toolset covers configuration discovery, SIWE and OTP authentication, registration, login, and token refresh. The main gap is the lack of an explicit logout or token revocation tool, though agents can discard tokens and the refresh token reuse behavior provides some reclamation.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
7 tool updates
- First observed
getAuthConfig - First observed
getSiweNonce - First observed
login - First observed
refreshToken - First observed
register - First observed
requestOtp - First observed
requestSms
Related MCP Connectors
Deterministic allow/require_approval/deny verdicts for agent actions, before they happen.
Owner-signed permissions for AI agent actions; ALLOW/BLOCK/REVIEW with request-bound receipts.
The system of record for AI agent authority: playbooks, routed policy questions, reusable rules.
Context and control for any AI. Agent identity, scoped access, and proof across tools.
Related MCP Servers
- AlicenseAqualityBmaintenanceDefault-deny action registry, append-only spend ledger, and human sign-off audit trail (MCP tools).6MIT
- AlicenseNot gradedqualityBmaintenanceEnforces identity-based access control and audit logging for MCP servers, letting you grant fine-grained tool permissions to users and systems while failing secure by default.MIT
- AlicenseNot gradedqualityBmaintenanceProvides permission gates and tamper-evident audit logging for AI agent tool executions, with declarative policies, consent ladders, and hash-chained verification.MIT
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd
Glama MCP Gateway
Add one secure layer between your agents and this server.