DispatchHealth MCP Server

An OAuth 2.1-protected Model Context Protocol (MCP) server exposed on DispatchHealth's own host by the WordPress MCP adapter running on www.dispatchhealth.com. Discovery is fully machine-readable: RFC 8414 authorization-server metadata and RFC 9728 protected-resource metadata are both served anonymously, the endpoint returns a conformant WWW-Authenticate Bearer challenge, and a single coarse `mcp` scope is advertised. The tool list is auth-gated — an anonymous tools/list returns 401 — so no tool manifest is asserted. This surface fronts the marketing site's content and WordPress abilities; DispatchHealth's clinical/partner platform (CESIA, Dispatch Express) publishes no public API.

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/dispatchhealth-mcp-server"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

A second provider on the same verified email joins the account you already have.

API entry from apis.yml

apis.yml Raw ↑
name: DispatchHealth MCP Server
description: 'An OAuth 2.1-protected Model Context Protocol (MCP) server exposed on DispatchHealth''s
  own host by the WordPress MCP adapter running on www.dispatchhealth.com. Discovery is fully machine-readable:
  RFC 8414 authorization-server metadata and RFC 9728 protected-resource metadata are both served anonymously,
  the endpoint returns a conformant WWW-Authenticate Bearer challenge, and a single coarse `mcp` scope
  is advertised. The tool list is auth-gated — an anonymous tools/list returns 401 — so no tool manifest
  is asserted. This surface fronts the marketing site''s content and WordPress abilities; DispatchHealth''s
  clinical/partner platform (CESIA, Dispatch Express) publishes no public API.'
humanURL: https://www.dispatchhealth.com/
baseURL: https://www.dispatchhealth.com/wp-json/mcp/mcp-oauth-server
tags:
- MCP
- Agents
- Authentication
- Healthcare
tags_raw:
- MCP
- Agents
- OAuth
- Healthcare
properties:
- type: MCPServer
  url: mcp/dispatchhealth-mcp.yml
- type: Authentication
  url: authentication/dispatchhealth-authentication.yml
- type: OAuthScopes
  url: scopes/dispatchhealth-scopes.yml
- type: WellKnown
  url: well-known/dispatchhealth-well-known.yml