VentriLinksVentrilinks
Login

MCP · Beta

Biotech diligence from the AI client you already use

MCP (Model Context Protocol) is an open standard. It connects an AI application to an outside service.

With VentriLinks MCP, an AI client such as Claude Code or Cursor sends a focused biotech diligence question to the VentriLinks agent. The answer comes back with public source links. You do not have to open the VentriLinks website for that request.

Open MCP settings

How it works

1

Your AI client

Claude Code, Cursor, Claude Desktop, or another MCP client.

2

VentriLinks MCP

A secure connection. Your API key authenticates it.

3

VentriLinks agent

The agent does one focused diligence run.

4

Result

The answer, with the public sources behind it.

What you can do

VentriLinks MCP gives focused, evidence-backed diligence to an outside application. Each request starts one VentriLinks diligence run.

Ask a focused question

Write one complete question in plain language. Name the company, asset, or target that you evaluate.

Choose a module

Apply one diligence module, for example scientific validation, IP and freedom to operate, regulatory, market, valuation, or catalysts.

Monitor progress

See if a run is queued, running, completed, or stopped, with the progress information that is available.

Stop a run early

End a run that you do not need. The bill shows the work up to that point.

Receive the result

Get the diligence answer and the public source links from the VentriLinks agent.

Use case documents

The agent can use the documents that are pinned in the case of the API key.

Ask a good question

A strong request stands alone. It names the subject and the analytical lens. Treat each run as a focused diligence assignment, not as a chat message.

Request template
Evaluate [company / asset / target] using the [VentriLinks module] module.
Decision context: [what I am trying to decide].
Focus on: [2-5 specific questions or concerns].
Use information available through [date, if important].
Identify supporting and contradictory evidence, key uncertainties, and the most decision-relevant risks. Return source links.

Scientific validation

“Evaluate the scientific and technology validity of [Asset] for [Indication]. Focus on target/mechanism support, human evidence, translational relevance, contradictory evidence, and the experiments that would most reduce uncertainty.”

Regulatory

“Assess the likely U.S. regulatory pathway and principal regulatory risks for [Asset] in [Indication]. Identify relevant precedents, unresolved evidence requirements, and questions that should be confirmed with the agency.”

Competitive differentiation

“Compare [Asset] with the most relevant current and emerging competitors. Focus on efficacy, safety, patient selection, development timing, convenience, and what would constitute meaningful differentiation.”

Public-company valuation

“For [Company/Ticker], analyze the major drivers of its current valuation, cash/runway and financing needs, pipeline value assumptions, key sensitivities, and catalysts that could materially change the thesis.”

Caution: short follow-ups

Do not expect the next run to understand a short follow-up such as “What about the IP?” Each run starts a new session. Repeat the company, asset, or target, the module, and the decision question.

Key-specific private memory can keep some deal context. It does not replace a complete request.

After you submit

Six stages take a question from your client to an answer with sources.

  1. 01

    Authentication

    VentriLinks checks the API key and finds the account and the case of the key.

  2. 02

    Account check

    VentriLinks checks the account balance before the run starts.

  3. 03

    Run start

    VentriLinks starts the agent and returns a run ID immediately.

  4. 04

    Research

    The diligence agent does the research. A run can take several minutes.

  5. 05

    Status and result checks

    The client checks progress and asks for the result. The server tells the client to wait approximately 20 seconds between checks.

  6. 06

    Completion

    VentriLinks returns the answer and the public source links. The run also shows in the case of the key.

Tools available to the client

ToolPurposeTypical use
run_diligenceStart a diligence runSend one complete diligence question.
get_diligence_resultGet the answerCheck until the result is ready.
get_run_statusCheck progressSee the run state and the progress information.
stop_runEnd a run earlyCancel a run that you do not need.

Keys, cases, and documents

The API key is an authentication secret and also a routing mechanism. Make its design part of your access-control model.

One key, one case

Every run from a key goes into one VentriLinks case. The case has the name of the key.

Pinned documents are visible

The agent can use the documents that are pinned in the case of the key. Give a key only to a person or system that you trust with those documents.

Separate partners and workflows

Make a different key for each partner, team, laptop, or integration when separation is important. Each key keeps its runs in its own case.

Refresh rotates the secret

Refresh replaces the secret. The key keeps its case and its continuity.

Revoke disables the key

Revoke stops all future use of the key.

Billing follows the account

VentriLinks bills each run to the account that owns the key, at the same rate as a comparable run in the product.

Key hygiene

Treat a VentriLinks API key like a password. Do not paste it into shared documents, screenshots, public tickets, or source-code repositories.

If a key is possibly exposed, refresh it to rotate the secret. Revoke it if the integration must not have access.

Current scope

Limits during the Beta

  • No Full Report through MCP. Use MCP for one focused question per run. Use the VentriLinks web product for a Full Report.
  • No continuous chat. Each question starts a new session, so write complete requests.
  • No document output. The MCP returns diligence analysis. It is not a document-generation endpoint at this time.
  • No browser sign-in. The client must support API-key authentication.

What the outside application does not get

  • Direct access to the VentriLinks knowledge graph.
  • Direct access to the VentriLinks dataroom or to the internal work of the agent.
  • Permission to change the knowledge graph. The agent can add qualified public evidence during its own research, under the platform rules.

Troubleshooting

Software that implements the MCP protocol over authenticated HTTP can use the VentriLinks endpoint. There is no separate REST request schema. Follow the current VentriLinks technical interface, and do not assume request formats that are not documented.

Ask a question
The client cannot connect

Make sure that the client supports remote HTTP MCP and custom Authorization headers. Copy the setup snippet again from Settings > MCP.

The client shows an authentication error

Make sure that the key is active and that the full "Bearer ..." header is present. If you are not sure, refresh the key and update the client configuration.

The run does not start

Make sure that the VentriLinks account has a sufficient balance, and that the question is in the current MCP scope.

The result does not agree with the question

Make the next request self-contained. Repeat the company, asset, or target, the module, the decision context, and the specific concerns.

I must stop a run

Use the stop_run tool in your client, or a stop or cancel action if your client shows one.