Cortellis MCP Server

Created By
uh-joana year ago
An MCP server enabling AI assistants to search and analyze pharmaceutical data through Cortellis. Features comprehensive drug search and ontology exploration.
Overview

What is Cortellis MCP Server?

Cortellis MCP Server is a production-ready server that enables AI assistants to search and analyze pharmaceutical data through Cortellis, providing comprehensive drug search, ontology exploration, and real-time clinical trial data access.

How to use Cortellis MCP Server?

To use the Cortellis MCP Server, clone the repository from GitHub, install the necessary packages, set up your environment variables with your Cortellis API credentials, and then interact with the server using natural language prompts or API calls.

Key features of Cortellis MCP Server?

  • 🔍 Comprehensive Drug Search: Search by indication, phase, company, and access real-time drug development statuses.
  • 🧬 Ontology Exploration: Explore standardized medical terminology and navigate drug classifications.
  • 🔐 Secure Authentication: Environment-based credential management and secure API communication.
  • 🛠 Developer-Friendly: Clear API documentation and easy integration with AI assistants.

Use cases of Cortellis MCP Server?

  1. Drug discovery and development analysis.
  2. Clinical trial data retrieval and analysis.
  3. Pharmaceutical market research and competitive intelligence.

FAQ from Cortellis MCP Server?

  • Can I use Cortellis MCP Server for all pharmaceutical queries?

Yes! It supports a wide range of queries related to drug development and clinical trials.

  • Is there a cost associated with using Cortellis MCP Server?

The server is open-source and free to use, but you will need valid Cortellis API credentials.

  • How secure is the data handled by Cortellis MCP Server?

The server employs secure authentication, HTTPS encryption, and regular security audits to ensure data safety.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
uh-joan
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

20 hours ago
Gpt Scrambler

2 days ago