cimd-reader
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@cimd-readershow me the latest CIMD validation results"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
CIMD Validator
A Next.js App Router application for validating whether MCP OAuth clients use Client ID Metadata Documents (CIMD), fall back to Dynamic Client Registration (DCR), or send static client IDs.
Stack
Next.js App Router and Vercel route handlers
TypeScript
Tailwind CSS
Turso/libSQL
Drizzle ORM
Related MCP server: mcp-oauth-dcr
Local Setup
Install dependencies:
npm installCreate local environment variables:
cp .env.example .env.localCreate and seed the local libSQL database:
npm run db:setupRun the app:
npm run devOpen http://localhost:3000.
Turso Setup
Create a Turso database and set these variables locally and in Vercel:
TURSO_DATABASE_URL=libsql://YOUR_DATABASE.turso.io
TURSO_AUTH_TOKEN=YOUR_TURSO_TOKEN
NEXT_PUBLIC_BASE_URL=https://YOUR_DOMAINThen run:
npm run db:migrate
npm run db:seedFor Vercel, add the same environment variables in the project settings before deploying.
OAuth Test Endpoints
/.well-known/oauth-authorization-server/authorize/token/register/mcp
MCP Client Setup
Add this Streamable HTTP MCP server URL to the client being tested:
https://cimd-reader.akxen.tech/mcpCodex CLI:
codex mcp add cimd_reader \
--url https://cimd-reader.akxen.tech/mcp \
--oauth-resource https://cimd-reader.akxen.tech/mcp
codex mcp login cimd_readerClaude Code:
claude mcp add --transport http \
cimd_reader \
https://cimd-reader.akxen.tech/mcpVS Code mcp.json:
{
"servers": {
"cimd_reader": {
"type": "http",
"url": "https://cimd-reader.akxen.tech/mcp",
"oauth": {
"clientId": "https://vscode.dev/oauth/client-metadata.json"
}
}
}
}The authorization server advertises CIMD support. /authorize logs the request, classifies the client behavior, validates HTTPS URL client_id values as CIMD metadata documents, stores the result, then redirects to redirect_uri with a fake authorization code. /token returns a fake bearer token. /register logs DCR attempts and returns a fake client registration.
Dashboard
/shows MCP client cards with claimed support, observed behavior, and latest CIMD validation./clients/[id]shows known metadata, latest OAuth attempt, raw metadata JSON, validation errors, and warnings./sessionslists validation sessions./sessions/[id]shows an OAuth request timeline./api/clientsreturns client data as JSON./api/sessionsreturns session data as JSON.
SSRF Protections
The CIMD metadata fetcher:
Requires HTTPS.
Rejects localhost hostnames.
Rejects private, loopback, link-local, carrier-grade NAT, multicast, and metadata IP ranges.
Resolves hostnames and blocks unsafe DNS results.
Limits redirects.
Uses a request timeout.
Caps response body size.
Sends no credentials or cookies.
Parses and validates JSON only after the fetch checks pass.
Seed Data
The seed script creates placeholder cards for:
Visual Studio Code.
Claude Code.
MCPJam.
Cursor.
Codex CLI.
GitHub Copilot.
Windsurf.
This server cannot be deployed
Maintenance
Related MCP Connectors
Experimental MCP server for current empirical verification of explicit public HTTPS endpoint claims.
Preflight MCP OAuth compatibility with structured evidence and remediation guidance.
Mock REST APIs, fake OAuth2/OIDC provider, uptime monitors + heartbeats, live badge/QR images.
Self-hosted federated MCP gateway: one OAuth 2.1 MCP server in front of N apps, user-level scopes.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceA configurable OAuth 2.0 authorization server and OAuth-protected MCP server for end-to-end testing of OAuth-protected MCP flows, including failure injection and control plane.-
- AlicenseNot gradedqualityCmaintenanceA demo MCP server protected by OAuth (DCR), enabling hands-on exploration of OAuth flow for local MCP servers.MIT
- FlicenseNot gradedqualityCmaintenanceAn MCP authorization server implementing OAuth2/OIDC flows, supporting dynamic client registration, PKCE, consent screens, and client ID metadata documents for MCP authorization.-
- AlicenseAqualityCmaintenanceMCP server that provides a hello world tool and implements server-side CIMD (Client ID Metadata Documents) processing, enabling OAuth authorization servers to fetch and validate client metadata documents with SSRF protections.4MIT