MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications
{
"mcpServers": {
"fhir": {
"args": [
"-y",
"mcp-remote",
"http://localhost:8000/mcp"
],
"command": "npx"
}
}
}MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications
Is it safe?
No known CVEs for @modelcontextprotocol/inspector. 2 previously resolved.
No authentication — any process on your machine can connect.
License not specified.
Is it maintained?
Last commit 5 days ago. 104 stars. 135,265 weekly downloads.
Will it work with my client?
Transport: stdio, sse, http. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
Context cost
5 tools. ~200 tokens (0.1% of 200K).
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y @modelcontextprotocol/inspector 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
search_fhir_resourcesSearch FHIR resources by type and parameters
retrieve_fhir_resourceRetrieve a specific FHIR resource by ID
create_fhir_resourceCreate a new FHIR resource
update_fhir_resourceUpdate an existing FHIR resource
delete_fhir_resourceDelete a FHIR resource
This server is missing a description.If you've used it, help the community.
Add informationNo open vulnerabilities. 2 fixed CVEs.
CVE-2025-58444FixedMCP Inspector is Vulnerable to Potential Command Execution via XSS When Connecting to an Untrusted MCP Server
An XSS flaw exists in the MCP Inspector local development tool when it renders a redirect URL returned by a remote MCP server. If the Inspector connects to an untrusted server, a crafted redirect can inject script into the Inspector context and, via the built-in proxy, be leveraged to trigger arbitrary command execution on the developer machine. Version 0.16.6 hardens URL handling/validation and prevents script execution. > Thank you to the following researchers for their reports and contributi
CVE-2025-49596FixedMCP Inspector proxy server lacks authentication between the Inspector client and proxy
Versions of MCP Inspector below 0.14.1 are vulnerable to remote code execution due to lack of authentication between the Inspector client and proxy, allowing unauthenticated requests to launch MCP commands over stdio. Users should immediately upgrade to version 0.14.1 or later to address these vulnerabilities. Credit: Rémy Marot <bughunters@tenable.com>
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.