Anpheros FHIR vs Runno
A side-by-side look at the Anpheros FHIR and Runno MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
A
Anpheros FHIRCode Execution · Remote HTTP/SSEHL7 FHIR R4 health-data API for AI agents: free sandbox, 30 synthetic patients, AI-ready context.25EmergingAuth: not declaredVerdict: choose Anpheros FHIR for code execution work over a hosted endpoint; choose Runno for code execution as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
AChoose Anpheros FHIR when
- You need dedicated capabilities in the Code Execution domain.
- You prefer a remote HTTP/SSE transport.
Choose Runno when
- You need dedicated capabilities in the Code Execution domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | A Anpheros FHIR | |
|---|---|---|
| Category | Code Execution | Code Execution |
| Quality signal | 25/100 · Emerging | 48/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 773 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Anpheros FHIR | View Runno |
Tools & capabilities
Anpheros FHIR tools
No tool names declared yet. Check the project README from the listing page.
Runno tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Anpheros FHIR
{
"mcpServers": {
"anpheros-fhir": {
"url": "https://developers.anpheros.com/guides/mcp"
}
}
}
Runno
{
"mcpServers": {
"runno": {
"command": "npx",
"args": [
"@runno/mcp"
]
}
}
}
Frequently asked questions
Anpheros FHIR is categorized under Code Execution and uses a remote HTTP/SSE transport. Runno belongs to Code Execution and uses a local stdio subprocess. Pick Anpheros FHIR for code execution work and Runno for code execution.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Anpheros FHIR has no declared pricing — check the project's own site. Runno has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add anpheros-fhir and runno as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Anpheros FHIR has a quality signal of 25/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars. Runno has 48/100 (Fair) with 0 views, 0 installs and 773 GitHub stars.