# com.phasefolio/phasefolio (remote · app.phasefolio.com)

Biotech rNPV/PoS engine for AI agents. Signed exports, evidence register, asset landscape.

- Trust score: 71/100 (medium)
- Change this week: +7
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `app.phasefolio.com`: 71/100 (this document), [markdown](https://verifymcp.io/servers/com-phasefolio-phasefolio/api-mcp.md), [page](https://verifymcp.io/servers/com-phasefolio-phasefolio/api-mcp)
- npm · `@phasefolio/mcp`: 30/100, [markdown](https://verifymcp.io/servers/com-phasefolio-phasefolio/phasefolio-mcp.md), [page](https://verifymcp.io/servers/com-phasefolio-phasefolio/phasefolio-mcp)

## Channel facts

- Endpoint: `https://app.phasefolio.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.4`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2041 tokens (~157/item across 13 items; 13 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-phasefolio-phasefolio https://app.phasefolio.com/api/mcp
```

### Codex

```toml
[mcp_servers.com-phasefolio-phasefolio]
url = "https://app.phasefolio.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-phasefolio-phasefolio": {
      "type": "remote",
      "url": "https://app.phasefolio.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-phasefolio-phasefolio --url https://app.phasefolio.com/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-phasefolio-phasefolio:
    url: "https://app.phasefolio.com/api/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-phasefolio-phasefolio": {
      "type": "http",
      "url": "https://app.phasefolio.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 69, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 66, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 64, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 63)

First indexed and scored.

## MCP tools (13)

### `get_project` (~87 tokens)

Fetch a PhaseFolio project's metadata: indication, sub-indication, modality, biomarker, asset name, and stage at entry. Use this when you need to ground an analysis question in the project's clinical context before fetching scenarios.

Input parameters:

- `project_id` (string, required): UUID of the PhaseFolio project. Get from the project URL in the dashboard or from a prior list_scenarios call.

Output parameters:

- `data` (object)

### `list_scenarios` (~102 tokens)

List all scenarios in a PhaseFolio project. Returns scenario IDs, names, created/updated timestamps, and top-line eNPV/rNPV. Use this to discover what scenarios exist before fetching one in detail.

Input parameters:

- `limit` (integer, required): Maximum number of scenarios to return (1–200). Defaults to 50; raise for projects with many what-if branches.
- `project_id` (string, required): UUID of the parent project whose scenarios to list.

Output parameters:

- `data` (array): Scenarios in the project, newest first.

### `get_scenario` (~99 tokens)

Fetch a PhaseFolio scenario's complete inputs (stage costs, durations, PoS, commercial assumptions, IRA settings) and computed outputs (eNPV, rNPV, cumulative PoS, per-stage breakdown, top sensitivity drivers). This is the authoritative engine output — every signed export ties back to this payload.

Input parameters:

- `scenario_id` (string, required): UUID of the scenario. Get from list_scenarios or the scenario URL in the dashboard.

Output parameters:

- `data` (object)

### `get_evidence` (~68 tokens)

Fetch the evidence register entries for a scenario — the citations, sources, and supporting documents the analyst attached to back the assumptions. Use this when an analysis question references 'what's the evidence for X?'

Input parameters:

- `scenario_id` (string, required): UUID of the scenario whose evidence register entries to fetch.

Output parameters:

- `data` (array): Array of evidence-register entries. Each entry has fields like assumption_path, source_url, source_date, excerpt, freshness, confidence — see /methodology/evidence-standards for the canonical schema.

### `get_dossier` (~81 tokens)

Fetch the structured dossier JSON for a scenario — the same content rendered in the IC Dossier PDF/Excel exports, in machine-readable form. Includes verdict, drivers, assumptions, evidence summary, and (if available) signed-export hashes pointing to the latest signed artifacts.

Input parameters:

- `scenario_id` (string, required): UUID of the scenario to fetch the IC dossier payload for.

Output parameters:

- `data`: Structured dossier payload mirroring the IC Dossier PDF/Excel exports. Top-level keys include verdict, drivers, assumptions, evidence, and (when available) signed_export hashes. See get_methodology('…

### `query_landscape` (~175 tokens)

Fetch the asset-anchored competitive landscape for a project — comparable trials, competing programs, sponsor activity, and biomarker overlap. Sourced from CT.gov + FDA + PhaseFolio's curated enrichment. Use when an analysis question asks 'who else is working on this?' or 'what's the competitive context?'

Input parameters:

- `phase_filter` (array, required): Optional list of clinical phases to include (e.g. ['PHASE2','PHASE3']). Empty array means all phases.
- `project_id` (string, required): UUID of the project to anchor the landscape on. Indication × modality × biomarker filters derive from the project.
- `recency_years` (integer, required): How many years back to look (1–50). Defaults to 10 — broad enough to catch development-stage peers without polluting with stale failures.

Output parameters:

- `data`: Asset-anchored landscape payload: kpis (sponsor counts, trial counts, etc.), comparable_trials[] (NCT-keyed), competing_programs[], biomarker_overlap. Filtered by the project's indication × modality…

### `query_evidence_atlas` (~173 tokens)

Fetch the published Evidence Atlas program universe for a sub-indication. Defaults to source-verified rows from public CT.gov + FDA; agent-labeled rows require include_unverified=true and remain explicitly labeled. Pending AI-serviced event_links are human_verified=false and review_status=pending_human_review until reviewed. Trial summaries and financial_links are source-derived facts; interpreted efficacy, PoS, and verdicts are not returned.

Input parameters:

- `include_unverified` (boolean, required): When true, include agent-labeled-not-verified rows in addition to source_verified rows. Rejected rows are never returned.
- `limit` (integer, required): Maximum number of programs to return, 1-328. Defaults to 100.
- `sub_indication` (string, required): Evidence Atlas sub-indication slug, e.g. 'ipf'.

Output parameters:

- `data` (object): Evidence Atlas payload for one published sub-indication.

### `query_drug_risk` (~87 tokens)

Fetch human-reviewed drug-specific clinical-risk signals for a project, including biomarker quality, Phase 1 ORR flag-only data, provenance, extractor versions, and pending-review counts. Use this before interpreting engine 2.6.0 drug-specific multipliers or flags.

Input parameters:

- `project_id` (string, required): UUID of the project whose reviewed drug-specific clinical-risk signals should be queried.

Output parameters:

- `data` (object): Drug-specific clinical-risk substrate for a project. Returns reviewed signals only; pending rows are counted but excluded from scoring.

### `query_benchmarks` (~170 tokens)

Query PhaseFolio benchmark availability. Source-backed PoS benchmarks are available separately; network cost distributions and duration percentiles are planned but currently return coming_soon with null estimates rather than PhaseFolio's manual planning defaults.

Input parameters:

- `indication` (string, required): Indication name (e.g. 'NSCLC', 'Rheumatoid Arthritis', 'Atopic Dermatitis'). Free-form; the engine fuzz-matches to the canonical indication taxonomy.
- `metric` (string, required): Which benchmark family to request. Cost and duration network benchmarks are currently coming_soon and return no estimate; manual wizard defaults are not returned as benchmarks.
- `modality` (string): Optional modality filter ('Antibody', 'Small Molecule', 'Cell Therapy', 'Gene Therapy', etc.). Omit to return cross-modality stats.

Output parameters:

- `data` (object): L1 (no-auth) returns a versioned headline set; L3 (bearer) will return granular slices once enough orgs are on the network.

### `verify_export` (~104 tokens)

Verify a signed PhaseFolio export by content hash. Returns verification status (valid/tampered/unknown), issued timestamp, methodology version, and an anonymized originating-org identifier. Use this when a user shares a PhaseFolio dossier and you want to confirm it's authentic before citing the analysis.

Input parameters:

- `hash` (string, required): 64-character hex SHA-256 of the signed artifact's content. Embedded in every signed PhaseFolio PDF (footer) and Excel (cover tab).

Output parameters:

- `data`

### `query_sec_deal_terms` (~193 tokens)

Query SEC EDGAR deal-term extractions by indication, deal type, date range, confidence, and review state. Returns per-deal rows with source quotes and accession URLs for verification; aggregate engine medians use the separate backend aggregate function.

Input parameters:

- `deal_type` (string): Optional deal type filter.
- `include_needs_review` (boolean, required): Whether to include rows flagged needs_review. Defaults to true so admin users can see flags.
- `indication` (string): Optional indication filter, e.g. 'antimicrobial'.
- `limit` (integer, required): Maximum rows to return, 1-500. Defaults to 100.
- `min_confidence` (number, required): Minimum extraction confidence threshold. Defaults to 0.5.
- `since` (string): Optional inclusive effective_date lower bound in YYYY-MM-DD format.
- `until` (string): Optional inclusive effective_date upper bound in YYYY-MM-DD format.

Output parameters:

- `data` (object)

### `triage_asset` (~141 tokens)

Produce a transparent, provenance-linked CONDITIONAL READ on a drug asset for deal triage. Pass either `text` (a teaser/abstract — fields are machine-extracted and the result is marked inputs_unconfirmed) or pre-confirmed `fields`. Returns a reasoning chain (each claim grounded or marked insufficient_evidence), mechanism-plausibility flags, PoS + landscape metrics, and a meta block with engine/methodology/synthesis versions. Does NOT compute rNPV. Not an autonomous verdict.

Input parameters:

- `fields` (object): Pre-confirmed structured fields.
- `text` (string): Unstructured asset text; triggers extraction (inputs_unconfirmed=true).

Output parameters:

- `data`

### `get_methodology` (~561 tokens)

Fetch a PhaseFolio methodology section's full content (rNPV engine, backtest, PoS calibration, IRA framework, development paths, clinical stage normalization, evidence standards, network benchmarks, COGS benchmark, SG&A benchmark, tax benchmark, SEC EDGAR deal-term extraction). Designed for citation: each section has a stable URL and a methodology version identifier you can reference in analysis output.

Input parameters:

- `section` (string, required): Which methodology section to fetch. 'rnpv' covers the core risk-adjusted NPV calculation: cumulative PoS, midpoint-discounted risk-adjusted development costs, the S-curve ramp/plateau/LOE revenue lif…

Output parameters:

- `data` (object)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-phasefolio-phasefolio/api-mcp#diagnostics

## Score history

- 2026-08-03: 71
- 2026-08-02: 70
- 2026-08-01: 70
- 2026-07-31: 69
- 2026-07-30: 66
- 2026-07-29: 65
- 2026-07-28: 65
- 2026-07-27: 64
- 2026-07-26: 63

## Links

- Remote endpoint: https://app.phasefolio.com/api/mcp
- Website: https://app.phasefolio.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-phasefolio-phasefolio/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-phasefolio-phasefolio/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-phasefolio-phasefolio/api-mcp