canada-health-infoway-terminology
Candidate MCP server derived from the Terminology Gateway OpenAPI operations. Canada Health Infoway does not publish an official hosted MCP server; this is a proposed tool surface an integrator could stand up over the read/terminology operations. Each tool inherits its input contract from the backing OpenAPI operation. All content tools require an authenticated Infoway session (see authentication/).
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.
Descriptor
Candidate descriptor · transport http
Tools
lookup_concept— FHIR $lookup — return properties/display for a code in a code system.expand_valueset— FHIR $expand — expand a ValueSet into its member codes.validate_code— FHIR $validate-code — check whether a code is a member of a ValueSet.translate_concept— FHIR $translate — map a code through a ConceptMap.find_code_systems— Search FHIR CodeSystem resources.find_value_sets— Search FHIR ValueSet resources.get_capability_statement— Fetch the FHIR CapabilityStatement (anonymous).browse_codesystems— RESTful browse of Canadian code systems.browse_subsets— RESTful browse of terminology subsets (value sets).browse_maps— RESTful browse of concept maps.browse_packages— RESTful browse of terminology packages.
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.