mcp-who-am-i
MCP, Who am I?
claude mcp add --transport stdio hyprmcp-mcp-who-am-i npx -y @hyprmcp/mcp-who-am-i@latest
How to use
This MCP server, mcp-who-am-i, reports information from the Authorization header by decoding the JWT and returning selected payload fields related to authentication. It can be used to quickly inspect who a request claims to be by exposing the decoded JWT contents via the MCP endpoint. You can run it locally with npx or via Docker, and then connect to its HTTP MCP endpoint to send requests with an Authorization header containing a JWT. The server responds with structured data about the decoded token, making it easy to verify claims like subject, issuer, expiration, and custom JWT fields. If you are using the public version, you can also access pre-built endpoints such as /who-am-i-public/mcp for unauthenticated usage, or /who-am-i/mcp for authenticated usage, depending on the deployment.
How to install
Prerequisites:
- Node.js and npm (for npx usage) or Docker (for container usage).
- Internet access to fetch the MCP server package from the registry.
Option A: Install and run with npx
-
Ensure Node.js is installed on your system.
-
Run the MCP server with:
npx @hyprmcp/mcp-who-am-i@latest
This will fetch and start the MCP server in your environment.
Option B: Run with Docker
-
Ensure Docker is installed and running.
-
Start the server container:
docker run --rm -p 3000:3000 ghcr.io/hyprmcp/mcp-who-am-i
The container exposes the MCP endpoint on port 3000.
Note: The repository README also mentions optional integration through various editors and tools by pointing to the same MCP endpoint; ensure you use the appropriate URL (for example, https://demo.hyprmcp.cloud/who-am-i/mcp) when using remote/demo deployments.
Additional notes
Tips and caveats:
- If you are decoding JWTs, ensure the Authorization header is set to: Authorization: Bearer <your_jwt_token>.
- For local testing, you can map the server's port to 3000 as shown in the Docker example or adjust the port if needed.
- If you encounter CORS or schema issues, verify the MCP endpoint path (e.g., /mcp) and confirm whether the deployment requires authentication or exposes a public variant (as shown in the README with /who-am-i-public/mcp).
- The npm package name for the Node.js-based server is @hyprmcp/mcp-who-am-i; use the exact tag if you rely on a specific release.
- When using npx with @latest, you’ll get the most recent release; pin versions if you want reproducible setups.
Related MCP Servers
context7
Context7 MCP Server -- Up-to-date code documentation for LLMs and AI code editors
MiniMax -JS
Official MiniMax Model Context Protocol (MCP) JavaScript implementation that provides seamless integration with MiniMax's powerful AI capabilities including image generation, video generation, text-to-speech, and voice cloning APIs.
pluggedin-app
The Crossroads for AI Data Exchanges. A unified, self-hostable web interface for discovering, configuring, and managing Model Context Protocol (MCP) servers—bringing together AI tools, workspaces, prompts, and logs from multiple MCP sources (Claude, Cursor, etc.) under one roof.
js
🔐 Plug-and-play auth for Node.js MCP servers.
mcp-install-instructions-generator
Generate MCP Server Installation Instructions for Cursor, Visual Studio Code, Claude Code, Claude Desktop, Windsurf, ChatGPT, Gemini CLI and more
mcp-bundler
Is the MCP configuration too complicated? You can easily share your own simplified setup!