Harbinger Health MCP Server

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