com.phasefolio/phasefolio

REMOTE · APP.PHASEFOLIO.COM · 2 COMPONENTS · SCANNED AUG 3

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

Available components

remote · app.phasefolio.com 71 npm · @phasefolio/mcp 30

+7 this week 71 71 Trust /100

Trust breakdown (6 categories)

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. How we score →

Endpoint Security80

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability68

AI-judged instruction clarity (excellent).Pass
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. See how to fix → Fail
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass
Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass

Capabilities20

Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · app.phasefolio.com

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

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

# ~/.codex/config.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
    }
  }
}

# add to OpenClaw

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

# ~/.hermes/config.yaml

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

// mcp.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 we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

3 Aug 26 +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.
1 Aug 26 +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.
31 Jul 26 +3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
28 Jul 26 +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.
27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
26 Jul 26 63

First indexed and scored.

Show 6 earlier entries Hide earlier entries

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://app.phasefolio.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=*.phasefolio.com	CN=YR2,O=Let's Encrypt,C=US	28 Jul 2026	26 Oct 2026	RSA 2048	SHA256-RSA	60d18c2575121d865dcee84ddff1e476f10
SANs: *.phasefolio.com, phasefolio.com
CN=YR2,O=Let's Encrypt,C=US (CA)	CN=Root YR,O=ISRG,C=US	3 Sept 2025	2 Sept 2028	RSA 2048	SHA256-RSA	4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA)	CN=ISRG Root X1,O=Internet Security Research Group,C=US	13 May 2026	2 Sept 2032	RSA 4096	SHA256-RSA	f24b6d17f9d9ad7cb1c9fea78782699f

DNSSEC insecure

Validation of app.phasefolio.com. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
com.	present	19718	13	Verified
phasefolio.com.	absent			Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation

Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result	No authorisation required
HTTP status	200

Header	Value
strict-transport-security	max-age=63072000; includeSubDomains; preload
x-content-type-options	nosniff
x-frame-options	SAMEORIGIN
referrer-policy	strict-origin-when-cross-origin
permissions-policy	camera=(), microphone=(), geolocation=(), interest-cohort=()

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://app.phasefolio.com/api/mcp	Verified	200
http (plaintext)	http://app.phasefolio.com/api/mcp	HTTPS enforced	308	https://app.phasefolio.com/api/mcp

MCP tools — 13 exposed · ~2,041 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

get_dossier ~81

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 Output Examples

Name	Type	Req	Description
scenario_id	string	yes	UUID of the scenario to fetch the IC dossier payload for.

Name	Type	Req	Description
data	—	yes	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('…

No examples provided.

get_evidence ~68

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 Output Examples

Name	Type	Req	Description
scenario_id	string	yes	UUID of the scenario whose evidence register entries to fetch.

Name	Type	Req	Description
data	array	yes	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.

No examples provided.

get_methodology ~561

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 Output Examples

Name	Type	Req	Description
section	string	yes	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…

Name	Type	Req	Description
data	object	yes	—

No examples provided.

get_project ~87

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 Output Examples

Name	Type	Req	Description
project_id	string	yes	UUID of the PhaseFolio project. Get from the project URL in the dashboard or from a prior list_scenarios call.

Name	Type	Req	Description
data	object	yes	—

No examples provided.

get_scenario ~99

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 Output Examples

Name	Type	Req	Description
scenario_id	string	yes	UUID of the scenario. Get from list_scenarios or the scenario URL in the dashboard.

Name	Type	Req	Description
data	object	yes	—

No examples provided.

list_scenarios ~102

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 Output Examples

Name	Type	Req	Description
limit	integer	yes	Maximum number of scenarios to return (1–200). Defaults to 50; raise for projects with many what-if branches.
project_id	string	yes	UUID of the parent project whose scenarios to list.

Name	Type	Req	Description
data	array	yes	Scenarios in the project, newest first.

No examples provided.

query_benchmarks ~170

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 Output Examples

Name	Type	Req	Description
indication	string	yes	Indication name (e.g. 'NSCLC', 'Rheumatoid Arthritis', 'Atopic Dermatitis'). Free-form; the engine fuzz-matches to the canonical indication taxonomy.
metric	string	yes	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.

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

No examples provided.

query_drug_risk ~87

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 Output Examples

Name	Type	Req	Description
project_id	string	yes	UUID of the project whose reviewed drug-specific clinical-risk signals should be queried.

Name	Type	Req	Description
data	object	yes	Drug-specific clinical-risk substrate for a project. Returns reviewed signals only; pending rows are counted but excluded from scoring.

No examples provided.

query_evidence_atlas ~173

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 Output Examples

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

Name	Type	Req	Description
data	object	yes	Evidence Atlas payload for one published sub-indication.

No examples provided.

query_landscape ~175

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 Output Examples

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

Name	Type	Req	Description
data	—	yes	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…

No examples provided.

query_sec_deal_terms ~193

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 Output Examples

Name	Type	Req	Description
deal_type	string	—	Optional deal type filter.
include_needs_review	boolean	yes	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	yes	Maximum rows to return, 1-500. Defaults to 100.
min_confidence	number	yes	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.

Name	Type	Req	Description
data	object	yes	—

No examples provided.

triage_asset ~141

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 Output Examples

Name	Type	Req	Description
fields	object	—	Pre-confirmed structured fields.
text	string	—	Unstructured asset text; triggers extraction (inputs_unconfirmed=true).

Name	Type	Req	Description
data	—	yes	—

No examples provided.

verify_export ~104

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 Output Examples

Name	Type	Req	Description
hash	string	yes	64-character hex SHA-256 of the signed artifact's content. Embedded in every signed PhaseFolio PDF (footer) and Excel (cover tab).

Name	Type	Req	Description
data	—	yes	—

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	63
27 Jul	64
28 Jul	65
29 Jul	65
30 Jul	66
31 Jul	69
1 Aug	70
2 Aug	70
3 Aug	71