Tune Therapeutics

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

GitHub

Documentation

📖
Authentication
https://raw.githubusercontent.com/api-evangelist/tune-therapeutics/refs/heads/main/authentication/tune-therapeutics-authentication.yml

Other Resources

🔗
MCPServer
https://raw.githubusercontent.com/api-evangelist/tune-therapeutics/refs/heads/main/mcp/tune-therapeutics-mcp.yml
🔗
OAuthScopes
https://raw.githubusercontent.com/api-evangelist/tune-therapeutics/refs/heads/main/scopes/tune-therapeutics-scopes.yml
🔗
APIsJSON
https://raw.githubusercontent.com/api-evangelist/tune-therapeutics/refs/heads/main/apis.yml

API entry from apis.yml

apis.yml Raw ↑ 
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