Hosted MCP server/Other Official

Official Cortellis Regulatory Intelligence MCP server

Hosted at api.clarivate.com·Streamable HTTP

Cortellis Regulatory Intelligence is Clarivate’s database of global drug regulatory guidance, requirements and agency correspondence. Its remote MCP server gives life-sciences teams assistant access to regulatory documents and intelligence for research and compliance work. Every option requires a Clarivate account with an active Cortellis Regulatory Intelligence subscription; contact [email protected] for access. Server-to-server use uses a Clarivate API key. The provider documents claude.ai, Claude Desktop and mobile, Microsoft 365 Copilot Chat, Copilot Studio and the API; other client snippets on this page are generic Streamable HTTP patterns, not provider-supported setups.

api.clarivate.com Streamable HTTP Clarivate account + active subscription; API key for server-to-server Source checked Oct 31, 2026 Server not checked yet Reviewed 2026-11-16
About

Where it fits

Regulatory affairs and life-sciences teams researching drug guidance and agency correspondence.

  • Find regulatory guidance for a drug in a given market.
  • Check agency correspondence for a specific drug.
  • Gather requirements for a compliance review.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Setup

Install it in your client

Choose a client, run the command or use the one-click install, then verify the connection. The endpoint uses Streamable HTTP.

All client guides
  1. 01

    Run this command in your terminal

    This adds Cortellis Regulatory Intelligence as a remote Streamable HTTP server in Claude Code.

    Claude Code
    claude mcp add --transport http cortellis-regulatory-intelligence https://api.clarivate.com/lifesciences/mcp-regulatory/mcp --scope project
  2. 02

    Verify the connection

    Run claude mcp list, or open /mcp in a Claude Code session.

    Learn more about MCP in Claude Code

More clients, including project and global config files, are in the sidebar.

Connection

Endpoint and configuration

Endpoint
https://api.clarivate.com/lifesciences/mcp-regulatory/mcp
Host
api.clarivate.com · /lifesciences/mcp-regulatory/mcp
Transport
Streamable HTTP
Authentication
Clarivate account + active subscription; API key for server-to-server
Server name
cortellis-regulatory-intelligence
Listing type
Official provider listing

The installer uses the server name cortellis-regulatory-intelligence. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that cortellis-regulatory-intelligence appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Find regulatory guidance for a drug in a given market. Check the result before you give the server more access.

  3. 3
    Check permissions.

    Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.

Server not checked yet

We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. The provider page blocked our automated check. Open it in a browser to confirm the setup.

Provider page blocked our check on Oct 31, 2026. A response does not guarantee the server is safe or that sign-in and tools will work.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • Authentication returns 401 or 403. Check the key, its environment variable, and the permissions attached to it.
  • The key works in the provider dashboard but not in the client. Confirm the client sends it in the header the provider expects.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

Cortellis Regulatory Intelligence documentationhttps://clarivate.com/products/cortellis/