Harbinger Health MCP Server

A live Model Context Protocol server namespace published on Harbinger Health's own host at https://harbinger-health.com/wp-json/mcp/, exposing two servers - mcp-oauth-server and mcp-adapter-default-server - over POST/GET/DELETE. It is protected by a real OAuth 2.1 deployment: https://harbinger-health.com/.well-known/oauth-authorization-server returns RFC 8414 metadata (authorization code with PKCE S256, refresh tokens, public clients, client ID metadata documents) and https://harbinger-health.com/.well-known/oauth-protected-resource returns RFC 9728 metadata naming the MCP server as the protected resource with a single mcp scope. An anonymous tools/list JSON-RPC call returns HTTP 401 mcp_unauthorized, so the tool catalogue and its input schemas require an authenticated introspection; the tool set is almost certainly drawn from the WordPress Abilities API registered at wp-abilities/v1, which is likewise 401 to anonymous callers. This is a site-content agent surface, not a clinical or diagnostic one.

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/harbinger-health-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 form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

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

API entry from apis.yml

apis.yml Raw ↑
aid: harbinger-health:harbinger-health-mcp-server
name: Harbinger Health MCP Server
description: 'A live Model Context Protocol server namespace published on Harbinger Health''s own host
  at https://harbinger-health.com/wp-json/mcp/, exposing two servers - mcp-oauth-server and mcp-adapter-default-server
  - over POST/GET/DELETE. It is protected by a real OAuth 2.1 deployment: https://harbinger-health.com/.well-known/oauth-authorization-server
  returns RFC 8414 metadata (authorization code with PKCE S256, refresh tokens, public clients, client
  ID metadata documents) and https://harbinger-health.com/.well-known/oauth-protected-resource returns
  RFC 9728 metadata naming the MCP server as the protected resource with a single mcp scope. An anonymous
  tools/list JSON-RPC call returns HTTP 401 mcp_unauthorized, so the tool catalogue and its input schemas
  require an authenticated introspection; the tool set is almost certainly drawn from the WordPress Abilities
  API registered at wp-abilities/v1, which is likewise 401 to anonymous callers. This is a site-content
  agent surface, not a clinical or diagnostic one.'
humanURL: https://modelcontextprotocol.io/
baseURL: https://harbinger-health.com/wp-json/mcp/mcp-oauth-server
tags:
- MCP
- Agents
- Authentication
- WordPress
tags_raw:
- MCP
- Agents
- OAuth
- WordPress
properties:
- type: MCPServer
  url: mcp/harbinger-health-mcp.yml
- type: ToolCrosswalk
  url: mcp/harbinger-health-tool-crosswalk.yml
- type: OAuthScopes
  url: scopes/harbinger-health-scopes.yml