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.

FINLY Balance Report Analysis

REMOTE · FINLY.CO.IL · SCANNED SEP 20

Israeli mortgage reports with Hebrew results, 15-minute recovery and authorized external OCR.

Available components

+3 this week 70 Trust /100

Recent critical change

Authorization (17 Sept 2026). See the changelog before you install this server.

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 Security63
Transport & Reachability100
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 446 tokens (~111/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
  • Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage82
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 38% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the FINLY Balance Report Analysis MCP server?

FINLY Balance Report Analysis is a hosted endpoint at https://finly.co.il/mcp/reports, 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 · finly.co.il

# add to Claude Code
claude mcp add --transport http il-co-finly-report-analysis 'https://finly.co.il/mcp/reports'
// .cursor/mcp.json
{
  "mcpServers": {
    "il-co-finly-report-analysis": {
      "url": "https://finly.co.il/mcp/reports"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "il-co-finly-report-analysis": {
      "type": "http",
      "url": "https://finly.co.il/mcp/reports"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.il-co-finly-report-analysis]
url = "https://finly.co.il/mcp/reports"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "il-co-finly-report-analysis": {
      "type": "remote",
      "url": "https://finly.co.il/mcp/reports",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add il-co-finly-report-analysis --url 'https://finly.co.il/mcp/reports' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  il-co-finly-report-analysis:
    url: "https://finly.co.il/mcp/reports"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "il-co-finly-report-analysis": {
      "Transport": "http",
      "Url": "https://finly.co.il/mcp/reports"
    }
  }
}
# add to Vellum
assistant mcp add il-co-finly-report-analysis -t streamable-http -u 'https://finly.co.il/mcp/reports'
// mcp.json
{
  "mcpServers": {
    "il-co-finly-report-analysis": {
      "type": "http",
      "url": "https://finly.co.il/mcp/reports"
    }
  }
}

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.

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

  • 17 Sept 26 +44
    • Authorization: unverified → fail critical
    • Injection markers: unverified → pass security
    • Transport: fail → pass security
    • Endpoint reachability: not serving MCP → reachable functional
    • Tool coverage: unverified → 100 functional
    • Stability: unverified → 0.23 functional
    • MCP protocol: unverified → pass functional
  • 16 Sept 26 −43
    • Endpoint reachability: reachable → not serving MCP security
    • Authorization: fail → unverified security
    • Tool safety: pass → unverified security
    • Stability: 0.17 → unverified security
    • Transport: pass → fail security
    • Capabilities: pass → unverified functional
    • Tool coverage: 100 → unverified functional
    • First check of Schema quality: unverified functional
  • 14 Sept 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.

  • 12 Sept 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.

  • 11 Sept 26 0
    • Stability: unverified → 0.03 functional
  • 10 Sept 26 66

    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 20 Sept 2026 · Probed https://finly.co.il/mcp/reports

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=finly.co.il CN=YR2,O=Let's Encrypt,C=US 3 Aug 2026 1 Nov 2026 RSA 2048 SHA256-RSA 56628b93e013c8fac29ef3306a68aa06593
SANs: finly.co.il, www.finly.co.il
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 finly.co.il. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
il. present 35088 13 Verified
co.il. present 7144 13 Verified
finly.co.il. 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=31536000; includeSubDomains
content-security-policy default-src 'self'; script-src 'self' https://challenges.cloudflare.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob:; font-src 'self' data:; connect-src 'self' https://challenges.cloudflare.com; frame-src https://challenges.cloudflare.com; object-src 'none'; frame-ancestors 'none'; base-uri 'self'; form-action 'self'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer
permissions-policy microphone=(), camera=(), geolocation=(), payment=(), usb=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://finly.co.il/mcp/reports Verified 200
http (plaintext) http://finly.co.il/mcp/reports HTTPS enforced 301 https://finly.co.il/mcp/reports
MCP tools · 4 exposed · ~446 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
analyze_balance_report ~271

Analyze a PDF, JPEG or PNG balance report. Include the pre-issued operation for encrypted result recovery and safe same-payload replay for up to 15 minutes from issuance; restarting the service ends recovery. Omit operation only for legacy immediate-only delivery. Raw reports are not persisted. Returns structured facts and readable Hebrew text/HTML. External OCR sends personal/financial mortgage data to Google Document AI outside Israel only with an agent attestation that the existing task permits this transfer, or legacy separate approval. The supplier notice hash is not evidence a human saw it. Local-only is the default. A terminal failure never restarts the same operation.

NameTypeReqDescription
authorizationobjectDeprecated compatibility field; omit it. FINLY does not use or record it as consent evidence.
content_base64stringyes
external_ocrOptional external OCR selection. Existing-task authority is an agent attestation covering mortgage data sent to Google Document AI outside Israel; its policy hash binds the supplier notice, not proof…
operationobjectOpt into encrypted result recovery for this pre-issued operation. Omit only for legacy immediate-only delivery.
security_challengestringyes
security_proofstringyes
NameTypeReqDescription
as_ofstringyes
assumptionsarrayyes
evidencearray
limitationsarrayyes
next_actionsarrayyes
no_actionobject
receiptobjectyes
request_idstringyes
response_kindyes
result
schema_versionyes
statusstringyes
toolyes

No examples provided.

delete_report_analysis_result ~50

Cancel this operation and delete its encrypted result using its exact capability. A deleted operation cannot be restarted. No raw report, identity or result is placed in the URL.

NameTypeReqDescription
operationobjectyes
NameTypeReqDescription
as_ofstringyes
assumptionsarrayyes
evidencearray
limitationsarrayyes
next_actionsarrayyes
no_actionobject
receiptobjectyes
request_idstringyes
response_kindyes
resultobject
schema_versionyes
statusstringyes
toolyes

No examples provided.

get_report_analysis_requirements ~67

Get the processing notice, external OCR supplier notices for existing-task authority or legacy approval, and a single-use proof-of-work challenge. Normal report analysis requires no additional FINLY approval. Solve SHA-256(challenge_token + ":" + proof) so its first two bytes are zero.

Input schema present but exposes no named parameters.

NameTypeReqDescription
as_ofstringyes
assumptionsarrayyes
evidencearray
limitationsarrayyes
next_actionsarrayyes
no_actionobject
receiptobjectyes
request_idstringyes
response_kindyes
resultobject
schema_versionyes
statusstringyes
toolyes

No examples provided.

get_report_analysis_result ~58

Retrieve the result or pending status using the exact operation capability received before upload. Does not upload, analyze, call OCR, renew expiry or prove Customer identity. An expired or restarted service cannot recover the result.

NameTypeReqDescription
operationobjectyes
NameTypeReqDescription
as_ofstringyes
assumptionsarrayyes
evidencearray
limitationsarrayyes
next_actionsarrayyes
no_actionobject
receiptobjectyes
request_idstringyes
response_kindyes
result
schema_versionyes
statusstringyes
toolyes

No examples provided.

Common questions

What is the FINLY Balance Report Analysis MCP server?

FINLY Balance Report Analysis is an MCP server listed in the public MCP registry as il.co.finly/report-analysis. Israeli mortgage reports with Hebrew results, 15-minute recovery and authorized external OCR. This page covers its hosted endpoint (https://finly.co.il/mcp/reports).

Is the FINLY Balance Report Analysis MCP server safe to use?

FINLY Balance Report Analysis scores 70 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 FINLY Balance Report Analysis MCP server expose?

FINLY Balance Report Analysis exposes 4 tools: analyze_balance_report, delete_report_analysis_result, get_report_analysis_requirements, get_report_analysis_result. Their descriptions and schemas cost roughly 446 tokens of context every time the server is loaded.

Does the FINLY Balance Report Analysis MCP server require authentication?

No. We connected to FINLY Balance Report Analysis without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the FINLY Balance Report Analysis MCP server still maintained?

FINLY Balance Report Analysis is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.