Maven Bio MCP server icon

Maven Bio

by Maven Bio

HIPAA CompliantSOC2 ReadyISO 27001 Ready
Healthcare16 tools

Query structured biopharma data from your AI assistant: drugs, trials, indications, deals, financings and the source documents behind them. 16 tools, all read-only, OAuth 2.1 sign-in.

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.

Connect Maven Bio via MCP

https://mcp.mavenbio.com/

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

Use in Agentman

Connect Maven Bio once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio

Maven Bio Tools & Capabilities (16)

aggregate_records
fetch_related
get_artifact
get_deals
get_financials
get_financings
get_monitors
get_recent_events
list_artifacts
match_entity
read_document
research_bio_evidence
research_entity
research_landscape
search_documents
search_entities

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • Not medical advice, and not a clinical tool. These tools retrieve records about drugs, trials and indications. Nothing here interprets a trial result, assesses a mechanism, or supports a decision about a patient's care. Maven Bio's own privacy policy frames the connector as intended for professional research on publicly available biopharma information and asks users not to send patient-identifiable health information through it.
  • Not investment advice. 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.
  • Accuracy is disclaimed by the vendor. Maven Bio's terms of use provide the service "AS IS", disclaim all warranties including fitness for a particular purpose, and state expressly that the company makes no warranty as to the results that may be obtained from use of the services. On a connector whose output feeds analysis, that disclaimer is the operative accuracy limit.
  • Verify high-value claims against the source. Maven Bio's own guidance is that discovery and landscape tools return structured baselines and should be paired with document search and read to confirm high-value claims against primary sources. Treat a landscape as a starting inventory, not a finished answer.
  • Usage is metered and rate-limited. Tool calls draw on your organization's Maven Bio credits and are subject to per-organization rate limits. Neither the per-call credit cost nor the rate-limit ceiling is published.
  • An account is required, and it is a sales-led purchase. There is no anonymous or free tier; the connector 401s without a token, and Maven Bio routes new users to a contact form.
  • Literature coverage is open-access-weighted. Maven Bio describes its scientific literature coverage as full-text open access plus abstracts. Paywalled full text is not claimed, so a document search will reach the abstract of a subscription-only paper rather than its body.
  • Your queries reach third parties. Maven Bio's MCP privacy policy names Anthropic, OpenAI, Google and OpenRouter as language-model providers that receive query text to interpret requests and resolve entity names, and Exa, Firecrawl and Jina for web search and retrieval. Sentry receives truncated request parameters on unexpected errors. Infrastructure is in the United States.
  • Tool call records are retained for as long as your account is. Maven Bio records the tool name, inputs, responses, timings and outcome of every call, and retains them while the account or organization is active, because they underpin billing and audit history. Deletion is by request.
  • No scope granularity. Both the RFC 9728 resource descriptor and the authorization server publish an empty 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.
  • We could not read tool schemas or annotations. The endpoint requires OAuth, so parameter-level detail and machine-readable safety hints are not published here. Tool names come from Anthropic's directory listing, and the read-only claim comes from Maven Bio's documentation.
  • The 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.

Frequently asked questions

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.

Sources

Server Info

Category
Healthcare
Developer
Maven Bio
Tools
16
Domain
mcp.mavenbio.com

Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.

Ready to connect Maven Bio?

Connect Maven Bio once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.