Harbinger Health

Harbinger Health is a Cambridge, Massachusetts biotechnology company founded out of Flagship Pioneering's Flagship Labs in 2018 that is building blood-based early cancer detection on the premise that the earliest phases of oncogenesis are marked by the reactivation of core developmental programs. Its proprietary Harbinger HX platform pairs cell-free DNA methylation assay chemistry tuned for low tumour fraction with machine learning operating under biologically informed constraints, and supports cancer signal detection, tumour content estimation and tissue-of-origin inference. RESOLVE, the company's clinical application of that platform, is positioned to generate clarity in the uncertain window between suspicion of cancer and diagnosis, across cancer types and clinical contexts, and is run out of a CLIA-certified and CAP-accredited high-complexity laboratory. The company raised a 100 million dollar round to expand its blood-based detection suite and is led by CEO Ajit Singh with Chief Innovation Officer Tony Shuber, a co-founder of Exact Sciences. Harbinger Health's API posture is minimal and clinical rather than commercial: there is no developer portal, no published documentation, no OpenAPI, no SDKs, no pricing and no self-serve API access, and the developer., docs., api., portal., status. and trust. subdomains do not resolve. What it does publish is unusual for a company with no developer programme - the corporate site serves a live, anonymously readable WordPress REST API (268 routes across 15 namespaces), an RFC 8414 OAuth 2.1 authorization-server metadata document, an RFC 9728 protected-resource document, and a real Model Context Protocol server namespace gated behind an mcp scope, alongside the WordPress Abilities API. That makes Harbinger Health machine-discoverable at the agent layer while none of its clinical, laboratory or diagnostic capability is exposed programmatically to third parties.

Harbinger Health publishes 2 APIs on the APIs.io network. Tagged areas include Health, Healthcare, Biotechnology, Cancer Detection, and Diagnostics.

Harbinger Health’s developer surface includes engineering blog, support, YouTube channel, authentication, code examples, and 31 more developer resources.

🌐 Visit website 📡 Source on GitHub

24.3/100 emerging ▬ flat Agent 21/100 agent aware Front door AI 1/6 silent saas Full breakdown ↓
scored 2026-09-25 · rubric v0.23.0

AccessFree

1 APIs 1 MCP Servers

Health Healthcare Biotechnology Cancer Detection Diagnostics Genomics Artificial Intelligence Machine Learning Life Sciences Clinical Laboratory Precision Medicine United States Company

Kin Score

Kin Score How this is scored →
scored 2026-09-25 · rubric v0.23.0

Composite quality — 24.3/100 · emerging

Contract Quality 1.2 / 19

Developer Ergonomics 4.6 / 15

Access Clarity 4.3 / 15

Operational Transparency 0.0 / 10

Contract Governance 1.6 / 9

Discoverability 4.5 / 8

Regulatory Posture 5.2 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 21/100 · agent aware

Machine-Readable Contract 0 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 6 / 6

Protected Resource Metadata 5 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Regulatory Posture applies to this provider. Its tags matched the Health regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/harbinger-health: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 2

Individual APIs this provider publishes, each with its own machine-readable definition.

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

Harbinger Health Website (WordPress REST)

The public WordPress REST API (wp-json) of the Harbinger Health website at harbinger-health.com: the route index of the site's content management system, catalogued as one site ...

Open Collections 2

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

API Collection

OPEN COLLECTION

API Collection

OPEN COLLECTION

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Harbinger Health MCP Server

MCP SERVER

Examples 5

Example request and response payloads for these APIs.

Harbinger Health Error 400

3 fields

EXAMPLE

Harbinger Health Error 401

3 fields

EXAMPLE

Harbinger Health Error 404

3 fields

EXAMPLE

Harbinger Health Error No Route

3 fields

EXAMPLE

Harbinger Health Types Response

12 fields

EXAMPLE

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Harbinger Health Authentication

none/http/oauth2 · 3 schemes

SECURITY

Harbinger Health Domain Security

TLSv1.3 · DNSSEC · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Harbinger Health Scopes

1 scope · authorizationCode

1 scopes

SCOPES

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Harbinger Health Agentic Access

236 operations · 130 acting

AGENTIC

Resources

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

WellKnown

MCPServer

LLMsTxt

AgentSkill

AgenticAccess

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Lifecycle

Conformance

DataModel

Build 3

SDKs, sample code, and the tooling you integrate with

ToolCrosswalk

ToolCrosswalk

Packages

Packages

Examples

Examples

Access & Security 4

Authentication, authorization, and security posture

Authentication

OAuthScopes

Compliance

DomainSecurity

Learn 1

Tutorials, courses, talks, and written guidance

YouTube

YouTube

Operate 2

Status, limits, changes, and where to get help

Support

Support

Contact

Contact

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 10

The organization behind the API

Website

About

Blog

Careers

Partners

PressRoom

LinkedIn

Twitter

Twitter

Instagram

Instagram

Facebook

Facebook

Scroll for all 10

Other 4

Properties that don't map to a standard resource type

Product

Product

Sitemap

Overlay

Source (apis.yml)

aid: harbinger-health
name: Harbinger Health
x-enrichment:
  date: '2026-08-04'
  status: enriched
  artifacts_added: 33
  pass: local-v1
url: https://raw.githubusercontent.com/api-evangelist/harbinger-health/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
description: 'Harbinger Health is a Cambridge, Massachusetts biotechnology company founded out of Flagship Pioneering''s Flagship
  Labs in 2018 that is building blood-based early cancer detection on the premise that the earliest phases of oncogenesis
  are marked by the reactivation of core developmental programs. Its proprietary Harbinger HX platform pairs cell-free DNA
  methylation assay chemistry tuned for low tumour fraction with machine learning operating under biologically informed constraints,
  and supports cancer signal detection, tumour content estimation and tissue-of-origin inference. RESOLVE, the company''s
  clinical application of that platform, is positioned to generate clarity in the uncertain window between suspicion of cancer
  and diagnosis, across cancer types and clinical contexts, and is run out of a CLIA-certified and CAP-accredited high-complexity
  laboratory. The company raised a 100 million dollar round to expand its blood-based detection suite and is led by CEO Ajit
  Singh with Chief Innovation Officer Tony Shuber, a co-founder of Exact Sciences. Harbinger Health''s API posture is minimal
  and clinical rather than commercial: there is no developer portal, no published documentation, no OpenAPI, no SDKs, no pricing
  and no self-serve API access, and the developer., docs., api., portal., status. and trust. subdomains do not resolve. What
  it does publish is unusual for a company with no developer programme - the corporate site serves a live, anonymously readable
  WordPress REST API (268 routes across 15 namespaces), an RFC 8414 OAuth 2.1 authorization-server metadata document, an RFC
  9728 protected-resource document, and a real Model Context Protocol server namespace gated behind an mcp scope, alongside
  the WordPress Abilities API. That makes Harbinger Health machine-discoverable at the agent layer while none of its clinical,
  laboratory or diagnostic capability is exposed programmatically to third parties.'
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: free
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: No published developer API; corporate-site content and MCP surfaces only
  confidence: high
  source:
  - probe
  generated: '2026-08-04'
  method: probed
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
tags:
- Health
- Healthcare
- Biotechnology
- Cancer Detection
- Diagnostics
- Genomics
- Artificial Intelligence
- Machine Learning
- Life Sciences
- Clinical Laboratory
- Precision Medicine
- United States
- Company
tags_raw:
- Health
- Healthcare
- Biotechnology
- Cancer Detection
- Diagnostics
- Genomics
- Artificial Intelligence
- Machine Learning
- Life Sciences
- Clinical Laboratory
- Precision Medicine
- United States
- Company
- Machine-Learning
created: '2026-08-04'
modified: '2026-08-04'
specificationVersion: '0.23'
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- 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
  x-surface: platform-generated
  x-platform: wordpress
  x-platform-surface: mcp-plugin
- aid: harbinger-health:harbinger-health-com-website-wordpress-rest
  name: Harbinger Health Website (WordPress REST)
  description: 'The public WordPress REST API (wp-json) of the Harbinger Health website at harbinger-health.com: the route
    index of the site''s content management system, catalogued as one site surface rather than as separate APIs.'
  baseURL: https://harbinger-health.com/wp-json
  tags:
  - WordPress
  x-surface: platform-generated
  properties:
  - type: Documentation
    url: https://harbinger-health.com/wp-json
  x-platform: wordpress
  x-platform-surface: rest
common:
- type: Website
  url: https://harbinger-health.com/
- type: About
  url: https://harbinger-health.com/about/
- type: Blog
  url: https://harbinger-health.com/news-insights/
- type: Support
  url: https://harbinger-health.com/contact/
- type: TermsOfService
  url: https://harbinger-health.com/terms-of-use/
- type: PrivacyPolicy
  url: https://harbinger-health.com/privacy-policy/
- type: Contact
  url: https://harbinger-health.com/contact/
- type: Careers
  url: https://harbinger-health.com/job/
- type: Partners
  url: https://harbinger-health.com/partnerships/
- type: Product
  url: https://harbinger-health.com/resolve/
- type: Product
  url: https://harbinger-health.com/platform-technology/
- type: PressRoom
  url: https://harbinger-health.com/news-insights/
- type: Sitemap
  url: https://harbinger-health.com/sitemap_index.xml
- type: LinkedIn
  url: https://www.linkedin.com/company/harbinger-health
- type: Twitter
  url: https://twitter.com/harbingerhlth
- type: YouTube
  url: https://www.youtube.com/@HarbingerHealth
- type: Instagram
  url: https://www.instagram.com/harbingerhealth/
- type: Facebook
  url: https://www.facebook.com/p/Harbinger-Health-61555320668795/
- type: Authentication
  url: authentication/harbinger-health-authentication.yml
- type: OAuthScopes
  url: scopes/harbinger-health-scopes.yml
- type: WellKnown
  url: well-known/harbinger-health-well-known.yml
- type: MCPServer
  url: mcp/harbinger-health-mcp.yml
- type: ToolCrosswalk
  url: mcp/harbinger-health-tool-crosswalk.yml
- type: LLMsTxt
  url: llms/harbinger-health-llms.txt
- type: Conventions
  url: conventions/harbinger-health-conventions.yml
- type: ErrorCatalog
  url: errors/harbinger-health-problem-types.yml
- type: Lifecycle
  url: lifecycle/harbinger-health-lifecycle.yml
- type: Conformance
  url: conformance/harbinger-health-conformance.yml
- type: Compliance
  url: https://harbinger-health.com/resolve/
- type: DomainSecurity
  url: security/harbinger-health-domain-security.yml
- type: DataModel
  url: data-model/harbinger-health-data-model.yml
- type: Packages
  url: packages/harbinger-health-packages.yml
- type: AgentSkill
  url: skills/_index.yml
- type: AgenticAccess
  url: agentic-access/harbinger-health-agentic-access.yml
- type: Overlay
  url: overlays/harbinger-health-wordpress-wp-v2-overlay.yaml
- type: Examples
  url: examples/_index.yml

Work with this as data

Every provider 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 providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
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 provider

curl "https://apis.io/api/v1/providers/harbinger-health"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/harbinger-health/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/harbinger-health/evidence"

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.

GitHub Google LinkedIn

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