Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Haven Financing

REMOTE · APP.HAVEN.FINANCE

Read-only Haven portfolio financing rates, simulations, debt comparisons and onboarding links.

+3 this week 76 Trust /100

Last scanned (21 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 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 → Why this is hard to 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1040 tokens (~173/item across 6 items; 6 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 Management30
  • Stability observed for 9 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 20 Nov 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.

  • 18 Nov 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.

  • 16 Nov 26 +1

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

  • 14 Nov 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.

  • 13 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 12 Nov 26 72

    First indexed and scored.

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 21 Nov 2026 · Probed https://app.haven.finance/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=app.haven.finance CN=YR2,O=Let's Encrypt,C=US 27 Oct 2026 25 Jan 2027 RSA 2048 SHA256-RSA 6b3423ae5712e438d20cc8651a4490067d7
SANs: app.haven.finance, ops.haven.finance
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

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of app.haven.finance. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
finance. DS published 46861 8 Verified
haven.finance. No DS 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
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' https://cdn.plaid.com https://challenges.cloudflare.com https://www.googletagmanager.com https://www.googleadservices.com https://googleads.g.doubleclick.net https://www.google.com https://tagmanager.google.com; style-src 'self' 'unsafe-inline' https://www.googletagmanager.com https://tagmanager.google.com https://fonts.googleapis.com; img-src 'self' data: blob: https://cdn.prod.website-files.com https://www.googletagmanager.com https://*.doubleclick.net https://www.google.com https://*.google.com https://www.gstatic.com https://ssl.gstatic.com https://fonts.gstatic.com; font-src 'self' data: https://fonts.gstatic.com; connect-src 'self' https://iuqcasxvkdfqdlmgqejv.supabase.co wss://iuqcasxvkdfqdlmgqejv.supabase.co https://*.plaid.com https://challenges.cloudflare.com https://www.googletagmanager.com https://*.googletagmanager.com https://www.googleadservices.com https://*.doubleclick.net https://www.google.com https://*.google.com https://*.google-analyt
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=(), usb=(), browsing-topics=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://app.haven.finance/api/mcp Verified 200
http (plaintext) http://app.haven.finance/api/mcp HTTPS enforced 308 https://app.haven.finance/api/mcp
MCP tools · 6 exposed · ~756 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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
compare_existing_debt ~154

Compares an existing loan (margin, SBLOC, HELOC, mortgage, personal loan, credit card) with Haven's all-in cost on every term: annual cost, savings, the lowest-cost option and the collateral Haven would need.

NameTypeReqDescription
balancenumberyesOutstanding balance of the existing loan, in USD.
collateralValuenumber–Market value of the brokerage portfolio that would secure Haven financing, in USD.
currentRatePercentnumberyesThe existing loan's annual interest rate, in percent (e.g. 8.25).
debtTypestring–Kind of existing debt: margin, sbloc, heloc, mortgage, personal_loan, credit_card or other.

No output schema declared.

No examples provided.

create_onboarding_link ~183

Builds a link that opens Haven's financing simulator prefilled with a scenario, where the investor can review it and apply. Creates nothing and submits nothing; the link carries no personal data.

NameTypeReqDescription
collateralValuenumberyesMarket value of the eligible brokerage portfolio pledged as collateral, in USD.
drawAmountnumberyesCash to borrow, in USD. Minimum $50,000.
rateTypestring–fixed: rate set for the term at execution. variable: resets monthly at the 1M rate.
sourcestring–Optional short label for the client creating the link, e.g. chatgpt. Recorded as utm_source.
termstring–Fixed-rate term: 3M, 6M, 12M (or 1Y) or 2Y. Ignored for variable financing.

No output schema declared.

No examples provided.

fetch ~31

Returns the full text of a document found with search.

NameTypeReqDescription
idstringyesA document id returned by search.

No output schema declared.

No examples provided.

get_current_rates ~63

Haven's current financing rates for each fixed term (3M, 6M, 1Y, 2Y) and the monthly variable rate: financing rate, Haven fee, all-in rate, illustrative after-tax rate, as-of time and rate-lock eligibility.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search ~62

Searches Haven's reference documents (current rates, fees, collateral limits, rate locks, savings method, risks). Returns ids to pass to fetch.

NameTypeReqDescription
querystringyesWhat to look for, e.g. 'advisory fee' or 'loan to value'.

No output schema declared.

No examples provided.

simulate_financing ~263

Calculate indicative financing costs for users considering borrowing against an investment portfolio. Accept portfolio value, requested financing amount, and selected term. When users have authorized access to connected financial information, relevant portfolio values and existing borrowing details may be used as calculation inputs, subject to applicable permissions and user consent. Return current Haven rates, advisory fees, estimated financing costs, loan-to-value ratios, and applicable eligibility and collateral risk disclosures. Do not request account credentials or unnecessarily detailed personal holdings.

NameTypeReqDescription
collateralValuenumberyesMarket value of the eligible brokerage portfolio pledged as collateral, in USD.
comparisonRatePercentnumber–Annual rate to compare against, in percent (default 7.5, an approximate brokerage margin rate).
drawAmountnumberyesCash to borrow, in USD. Minimum $50,000.
existingHavenBalancenumber–Haven financing already outstanding against the same collateral, in USD. Default 0.
rateTypestring–fixed: rate set for the term at execution. variable: resets monthly at the 1M rate.
termstring–Fixed-rate term: 3M, 6M, 12M (or 1Y) or 2Y. Ignored for variable financing.

No output schema declared.

No examples provided.

Install

How do I install the Haven Financing MCP server?

Haven Financing is a hosted endpoint at https://app.haven.finance/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · app.haven.finance

# add to Claude Code
claude mcp add --transport http finance-haven-financing 'https://app.haven.finance/api/mcp'
Common questions

What is the Haven Financing MCP server?

Haven Financing is an MCP server listed in the public MCP registry as finance.haven/financing. Read-only Haven portfolio financing rates, simulations, debt comparisons and onboarding links. This page covers its hosted endpoint (https://app.haven.finance/api/mcp).

Is the Haven Financing MCP server safe to use?

Haven Financing scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Haven Financing MCP server expose?

Haven Financing exposes 6 tools: get_current_rates, simulate_financing, compare_existing_debt, create_onboarding_link, search, fetch. Their descriptions and schemas cost roughly 756 tokens of context every time the server is loaded.

Does the Haven Financing MCP server require authentication?

No. We connected to Haven Financing without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Haven Financing MCP server still maintained?

Haven Financing is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Haven Financing MCP server?

VerifyMCP ran 13 checks on Haven Financing, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.