AdisInsight
Query Springer Nature's drug-pipeline and trial database from an AI agent.
Query structured biopharma data: drugs, trials, indications, deals, financings and the documents behind them.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Maven Bio MCP server connects Maven Bio's biopharma data layer to Claude, ChatGPT and any MCP-compatible agent. Its sixteen tools resolve drug and company names, pull records on trials, indications, deals and financings, and read the filings behind them. Maven Bio documents every tool as read-only. Sign-in is OAuth 2.1 against an existing Maven Bio account.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
get_deals, get_financings and get_financials return deal and financial records that investors use. They return records, not judgements. Neither Maven Bio nor this page draws a conclusion about any company's prospects, and Maven Bio's terms disclaim any warranty as to the results obtained from the service.scopes_supported array, so a consent screen cannot offer a narrower grant and an issued token cannot be audited for one. Access is scoped by your Maven Bio account and organization instead.research_ tools' output shape is undocumented. Maven Bio's connector documentation names no individual tool, so whether research_entity, research_landscape and research_bio_evidence return structured records or synthesised prose is not stated anywhere we could find.No. Maven Bio's connector documentation states the connector exposes sixteen read-only tools and that nothing done through it modifies your Maven Bio data. Every one of the sixteen tool names Anthropic's directory lists is a retrieval verb. We could not read the live safety annotations, because the endpoint requires a token.
Yes. Maven Bio documents an active Maven Bio account as a prerequisite and routes new users to its contact page. Sign-in uses OAuth, so no API keys or passwords reach your MCP client. Monitors, saved artifacts and account data are scoped to your own account and organization rather than to the whole platform.
Yes, indirectly. Maven Bio states that tool calls draw on your organization's Maven Bio credits and are subject to per-organization rate limits. Neither the credit cost per call nor the rate-limit ceiling is published, so budget effects are not predictable from the documentation alone. Usage is metered per organization for billing.
Four source families, per Maven Bio's documentation: FDA filings, SEC filings, clinical papers, press releases and conference abstracts, returned as full text, structured sections or extracted citations. Its own site describes a database of over 20 million documents covering nearly 70,000 drugs. Scientific literature coverage is full-text open access plus abstracts.
No. Maven Bio's MCP privacy policy states it does not receive, collect or store your conversations, chat history, or shared files, only the parameters of each tool call. It does record tool names, inputs, responses and timings for billing and support. Query text may reach third-party language-model providers to resolve entity names.
No. Maven Bio's MCP privacy policy asks users not to submit patient-identifiable health information or other sensitive personal data through connector tool calls, and describes the connector as intended for professional research on publicly available biopharma information. Tool call parameters are logged and may be shared with third-party processors.
No. Maven Bio publishes one remote endpoint using Streamable HTTP, and Anthropic's directory records the same transport. There is no local stdio option and nothing to install on your own machine. We probed eight other paths on the same host and only the documented one and a slash-mcp alias answered; the rest returned 404.
llms.txt machine index (retrieved 2026-09-08; corpus figures of over 20 million documents and nearly 70,000 drugs) · retrieved 2026-09-08research_ tools) · retrieved 2026-09-08initialize against https://mcp.mavenbio.com/ returned HTTP 401 with a WWW-Authenticate: Bearer challenge naming OAuth 2.1 and a resource_metadata pointer (2026-09-08) · retrieved 2026-09-08https://mcp.mavenbio.com/.well-known/oauth-protected-resource (2026-09-08); an invented server name at the same path returned 404, so the descriptor discriminates · retrieved 2026-09-08https://auth.mavenbio.com/.well-known/oauth-authorization-server/oauth/2.1 (2026-09-08; empty scopes_supported, PKCE S256, dynamic registration) · retrieved 2026-09-08robots.txt at (retrieved 2026-09-08): Allow: / with narrow exclusions, no Content-Signal line, sitemap named · retrieved 2026-09-08Connect Maven Bio once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.