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

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/website-mcp"
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.

GitHub Google LinkedIn

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

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
- Authentication
- WordPress
tags_raw:
- 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