fips_in_process — FIPS 140 certificate tracker MCP Tool
fips_in_process
(fips in process) is one of 6 tools on the
FIPS 140 certificate tracker
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call fips_in_process from your client
- Claude Code FIPS 140 certificate tracker fips_in_process run in your project directory
- Claude Desktop FIPS 140 certificate tracker fips_in_process ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor FIPS 140 certificate tracker fips_in_process ~/.cursor/mcp.json
- VS Code FIPS 140 certificate tracker fips_in_process .vscode/mcp.json
- Zed FIPS 140 certificate tracker fips_in_process ~/.config/zed/settings.json
- Windsurf FIPS 140 certificate tracker fips_in_process ~/.codeium/windsurf/mcp_config.json
- Cline FIPS 140 certificate tracker fips_in_process ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI FIPS 140 certificate tracker fips_in_process ~/.gemini/settings.json
- Grok FIPS 140 certificate tracker fips_in_process .mcp.json (in your project root)
- ChatGPT FIPS 140 certificate tracker fips_in_process Settings → Connectors → Advanced → Developer mode
- Claude.ai FIPS 140 certificate tracker fips_in_process Settings → Connectors → Add custom connector
- LangChain FIPS 140 certificate tracker fips_in_process pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http fips-cmvp https://fips.808bits.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.