engrail-therapeutics-mcp.yml
engrail.com runs two live Model Context Protocol servers on its WordPress-backed corporate site, registered under the `mcp` REST namespace and fronted by RFC 8414 / RFC 9728 OAuth discovery documents at the apex. Both servers are OAuth-protected: an anonymous `tools/list` returns HTTP 401 (`mcp_unauthorized` on the OAuth server, `rest_forbidden` on the adapter default server), so the live tool manifest and its inputSchemas could not be read and NO tool list is recorded here. The companion WordPress Abilities API (`wp-abilities/v1`), which is what backs MCP tools on this plugin stack, is likewise 401 for anonymous callers. This is a real, discoverable agent surface on a clinical-stage pharmaceutical company's marketing site — not a product API.
One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.
Documentation
Documentation link · transport
About MCP
The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.
Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.
Work with this as data
Every MCP server here is available over the APIs.io API and to AI agents over MCP.