Tune Therapeutics

Tune Therapeutics is a clinical-stage epigenetic editing biotechnology company headquartered in Durham, North Carolina with a second site in Seattle, Washington. Founded in 2021 by Charles Gersbach, Fyodor Urnov and Dan McHugh, the company develops its TEMPO platform for tunable epigenome editing — programmable DNA-binding modulation of gene expression that does not cut or permanently alter the underlying DNA sequence. Its lead program, TUNE-401, is an investigational epigenetic silencing therapy for chronic hepatitis B cleared by New Zealand Medsafe for a Phase 1b trial. Tune publishes no product API and operates no developer program; the only machine-readable surface it exposes is the WordPress REST API and a pair of OAuth-gated Model Context Protocol servers shipped by plugins on its corporate marketing site.

Tune Therapeutics publishes 1 API on the APIs.io network. Tagged areas include Company, Biotechnology, Life Sciences, Therapeutics, and Genomics.

Tune Therapeutics’ developer surface includes engineering blog, support, authentication, and 10 more developer resources.

23.6/100 emerging ▬ flat Agent 20/100 agent aware Full breakdown ↓
scored 2026-08-17 · rubric v0.11.0
1 APIs 1 MCP Servers
CompanyBiotechnologyLife SciencesTherapeuticsGenomicsEpigeneticsGene TherapyClinical StageResearch

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-17 · rubric v0.11.0
Composite quality — 23.6/100 · emerging
Contract Quality 0.0 / 21
Developer Ergonomics 4.4 / 17
Commercial Clarity 3.6 / 17
Operational Transparency 0.0 / 11
Governance 1.3 / 10
Discoverability 6.5 / 9
Regulatory Posture 7.9 / 15
Agent readiness — 20/100 · agent aware
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 10
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
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.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% 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/. This rating is computed from github.com/api-evangelist/tune-therapeutics: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 1

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

Tune Therapeutics Website MCP Server

Two Model Context Protocol servers exposed from the Tune Therapeutics corporate WordPress site via the WordPress MCP Adapter plugin, backed by the WordPress Abilities API. Both ...

MCP Servers 1

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

Security Posture 2

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

Tune Therapeutics Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Tune Therapeutics Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Resources

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

Access & Security 3

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: tune-therapeutics
name: Tune Therapeutics
description: Tune Therapeutics is a clinical-stage epigenetic editing biotechnology company headquartered in Durham, North
  Carolina with a second site in Seattle, Washington. Founded in 2021 by Charles Gersbach, Fyodor Urnov and Dan McHugh, the
  company develops its TEMPO platform for tunable epigenome editing — programmable DNA-binding modulation of gene expression
  that does not cut or permanently alter the underlying DNA sequence. Its lead program, TUNE-401, is an investigational epigenetic
  silencing therapy for chronic hepatitis B cleared by New Zealand Medsafe for a Phase 1b trial. Tune publishes no product
  API and operates no developer program; the only machine-readable surface it exposes is the WordPress REST API and a pair
  of OAuth-gated Model Context Protocol servers shipped by plugins on its corporate marketing site.
url: https://raw.githubusercontent.com/api-evangelist/tune-therapeutics/refs/heads/main/apis.yml
image: https://tunetx.com/wp-content/uploads/2022/10/TuneTx_Meta.png
x-type: company
x-source: harvest:secondary-market
x-tier: profiled
x-tier-reason: enrichment
specificationVersion: '0.20'
created: '2026-08-05'
modified: '2026-08-05'
tags:
- Company
- Biotechnology
- Life Sciences
- Therapeutics
- Genomics
- Epigenetics
- Gene Therapy
- Clinical Stage
- Research
apis:
- aid: tune-therapeutics:website-mcp
  name: Tune Therapeutics Website MCP Server
  description: 'Two Model Context Protocol servers exposed from the Tune Therapeutics corporate WordPress site via the WordPress
    MCP Adapter plugin, backed by the WordPress Abilities API. Both endpoints are live and answer JSON-RPC over HTTP, and
    both are protected: an unauthenticated tools/list returns HTTP 401 with a spec-conformant WWW-Authenticate Bearer challenge
    pointing at RFC 9728 protected-resource metadata. Discovery metadata (RFC 8414 authorization-server, RFC 9728 protected-resource)
    is served anonymously and was captured verbatim. This is a content-management-platform surface, not a first-party Tune
    Therapeutics product API — recorded because it is a real, live, agent-reachable endpoint on the company domain, not because
    the company markets it.'
  humanURL: https://tunetx.com/
  baseURL: https://tunetx.com/wp-json/mcp/
  tags:
  - MCP
  - Model Context Protocol
  - OAuth
  - WordPress
  x-origin: platform-default
  x-origin-note: Provided by the WordPress MCP Adapter plugin, not authored or marketed by Tune Therapeutics.
  properties:
  - type: MCPServer
    url: mcp/tune-therapeutics-mcp.yml
  - type: Authentication
    url: authentication/tune-therapeutics-authentication.yml
  - type: OAuthScopes
    url: scopes/tune-therapeutics-scopes.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: DomainSecurity
  url: security/tune-therapeutics-domain-security.yml
- type: Website
  url: https://tunetx.com/
- type: Blog
  url: https://tunetx.com/news-and-insights/
- type: BlogRSS
  url: https://tunetx.com/feed/
- type: Support
  url: https://tunetx.com/contact-us/
- type: TermsOfService
  url: https://tunetx.com/terms-and-conditions/
- type: PrivacyPolicy
  url: https://tunetx.com/privacy-policy/
- type: WellKnown
  url: well-known/tune-therapeutics-well-known.yml
- type: MCPServer
  url: mcp/tune-therapeutics-mcp.yml
- type: Authentication
  url: authentication/tune-therapeutics-authentication.yml
- type: OAuthScopes
  url: scopes/tune-therapeutics-scopes.yml
- type: Conformance
  url: conformance/tune-therapeutics-conformance.yml
- type: LLMsTxt
  url: llms/tune-therapeutics-llms.txt
x-enrichment:
  date: '2026-08-05'
  status: enriched
  artifacts_added: 10
  pass: local-v1
x-coverage:
  state: covered
  reason: platform-surface-only
  detail: Tune Therapeutics is a clinical-stage biotech with no product API and no developer program — /openapi.json, /swagger.json,
    /api-docs, /graphql, /docs and /developers all 404 and no api./docs./developer. subdomain resolves — but its corporate
    WordPress site exposes two live OAuth 2.1-gated Model Context Protocol servers under /wp-json/mcp/ with RFC 8414 and RFC
    9728 discovery metadata served anonymously, which is what this profile captures.
  evidence:
  - url: https://tunetx.com/openapi.json
    status: 404
  - url: https://tunetx.com/.well-known/oauth-protected-resource
    status: 200
  - url: https://tunetx.com/wp-json/mcp
    status: 200
  - url: https://tunetx.com/wp-json/mcp/mcp-oauth-server
    status: 401
  - url: https://tunetx.com/.well-known/agent-card.json
    status: 404
  checked: '2026-08-05'