OIDC provider for MCP servers with pluggable identity providers. Works with any OIDC-compliant identity provider (Auth0, Clerk, Okta, Keycloak, Azure AD, Google, etc.)
This is NOT a conventional MCP server with user-facing tools. It is an OIDC authentication provider library/framework. The two tools listed ('whoami' x2) are examples from the reference implementation, not production tools. The actual server code in src/ provides authentication infrastructure (OidcServerOptions, OidcServerResult, token validation) but does NOT expose conventional agent tools for LLM consumption. Scoring is severely depressed because: (1) Tool definitions are not visible in the actual library code, they exist only in example files; (2) Both tool instances are named identically ('whoami'), violating naming uniqueness; (3) Input schemas are empty objects {}, providing no parameter guidance; (4) Descriptions are minimal (under 50 chars) and generic; (5) No output schema documentation; (6) This appears to be authentication middleware, not an agentic tool provider. If the intent is to expose authentication state to agents, the tool design is incomplete.
Get information about the currently authenticated user
Get current user info from session
Duplicate tool name 'whoami', tool names must be unique. Identical names cause tool selection ambiguity for LLMs.
Empty input schemas {} for both tools, no parameter type information, constraints, or descriptions provided. LLMs cannot reason about what parameters are accepted or required.
No output schema documented for either tool. LLMs cannot determine what fields to expect in the response or plan downstream tool chaining.
Tool definitions exist only in example files (example/mcp-integrated-oidc/src/index.ts), not in the main library code (src/). If these are meant to be reference examples, they should not be counted as production tools. If the library is meant to provide these tools, they must be in the core library.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 19 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 20 | - | v1 |
Descriptions are under 50 characters and generic ('Get information about the currently authenticated user' and 'Get current user info from session'). Do not clearly distinguish between the two instances or explain when to call each.
Server is an OIDC authentication framework/middleware, not a conventional agentic tool provider. The tools appear to be demonstration examples rather than the core value proposition. Architecture mismatch between server purpose and tool design.