1uphealth-fhir
One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.
Endpoint
Hosted endpoint · transport http
Connect
This is a remote MCP server — point an MCP client at the endpoint URL. Clients with native remote support (Claude, Cursor, VS Code, …):
For stdio-only clients (older Claude Desktop, etc.), bridge with mcp-remote:
If the server requires authentication, add the provider's token/header (e.g. an X-API-Key) per its docs. A quick reachability check:
Tool quality observed · not scored
tools with readOnly / destructive hints
parameters described (7 total)
state-changing tools without destructiveHint
tool-list tokens (3 tools)
tools over ~1,200 tokens
From an anonymous initialize + tools/list capture measured 2026-10-27; tokens are chars/3.6 of each tool definition. Recorded for the Kin Score's agent readiness as an observed signal — it contributes no points yet.
Tools
execute— Run JavaScript in a sandbox against the documentation tools on the global `tools` object. The only extra global is `tools` - there is no `fetch`, `console`, `setTimeout`, `require`, or Node.js API; all I/O goes through `tools`. Workflow - minimize round-trips; one `describe-tools` call plus one `execute` call covers most requests: 1. Analyze the request and decide which sandbox tools it needs. 2. Call `describe-tools` with those names to get their exact TypeScript signatures - inputs, result shapes, and a worked example. NEVER call `execute` with guessed method names, parameter names, enum values, or result field names: read fields off the declared return types, not from assumptions. 3. Batch everything into a SINGLE script: chain tool calls, pass one call's output into the next, process results in plain JavaScript, and `return` only what the request needs. Available tools (exact signatures come from `describe-tools`): - listApis — Lists the APIs documented in this project - getEndpoints — Get all endpoints for a specific API. When several definiti… - getEndpointInfo — Get comprehensive information about specific endpoint inclu… - getSecuritySchemes — Get the security schemes for a specific API. When several d… - getFullApiDescription — Get the complete OpenAPI description. When several definiti… - search — Search across the documentation to fetch relevant content f… - submitFeedback — Report a documentation page that is wrong or incompletedescribe-tools— Get the exact TypeScript signatures of the sandbox tools available to `execute`. Analyze the user request first, then pass `tools` with only the tool names the request needs (every name is listed in this input schema / description); omit `tools` only when you cannot tell which tools apply. Always call this before your first `execute` and never guess signatures. Request every tool the task may need in ONE call instead of calling this repeatedly.
About MCP
The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.
Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.
Work with this as data
Every MCP server here is available over the APIs.io API and to AI agents over MCP.