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.

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
- 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