13-Week Cash Flow Plan
REMOTE · MCP.CHIRIBA.IT · SCANNED SEP 18
13-week cash flow plan with a live Excel workbook, not just an answer in chat.
Available components
Deleted
This server was marked deleted in the MCP registry on 2026-09-17 06:30:23.436599+00.
Its details are retained for reference, and this page is not indexed.
The registry records this reason: Project discontinued; endpoint decommissioned 2026-09-17.
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC not yet verified: we couldn't validate it against a resolver. View diagnostics → Unverified
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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 −4
The score moved with no change recorded against any check. We would rather say so than guess.
- 17 Sept 26 −75
- Endpoint reachability: reachable → unreachable ▼ security
- DNSSEC: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 4 Sept 26 +1
- Stability: 0.97 → pass security
- 2 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 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
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 18 Sept 2026 · Probed https://mcp.chiriba.it/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC inconclusive
Validation of mcp.chiriba.it. — Inconclusive
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| mcp.chiriba.it. | Error no A/AAAA/CNAME RRset answered for the name |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.chiriba.it/mcp | Unreachable | ||
| http (plaintext) | http://mcp.chiriba.it/mcp | HTTPS enforced |
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 →
build_cashflow_plan 13-Week Cash Flow Plan ~504
Build a 13-week cash flow forecast and return a live Excel workbook. Use this when someone asks when they will run out of cash, how long their runway is, how much funding they need to bridge a gap, or wants a short-term liquidity or treasury forecast. Takes opening cash balance, expected receipts (or revenue and DSO), supplier payments (or purchases and DPO), payroll, loan instalments and taxes due. Returns the week-by-week grid, the first week cash goes negative, the peak funding need, and levers such as collecting earlier or paying later. Ask the user for the figures one at a time; call the tool once you have the opening balance plus receipts and supplier payments — payroll, loans and taxes default to zero if not given.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | Currency label, e.g. EUR. Label only. |
| dpoDays | number | – | Days payable outstanding, used with purchases. |
| dsoDays | number | – | Days sales outstanding, used with revenue. |
| loanRepayments | – | – | Loan and lease instalments. One number for every week, or 13 weekly values. |
| locale | string | – | – |
| openingBalance | number | – | Cash in the bank on day one. Required. |
| openingPayables | number | – | Payables open on day one. Optional. |
| openingReceivables | number | – | Receivables open on day one. Optional; sharpens the DSO conversion. |
| payroll | – | – | Wages and salaries. One number for every week, or 13 weekly values. |
| purchases | – | – | Purchases, if payments are not known directly (needs dpoDays). One number for every week, or 13 weekly values. |
| receipts | – | – | Cash expected in from customers. One number for every week, or 13 weekly values. |
| revenue | – | – | Revenue, if receipts are not known directly (needs dsoDays). One number for every week, or 13 weekly values. |
| startDate | string | – | First day of the plan, YYYY-MM-DD. Defaults to today. |
| supplierPayments | – | – | Cash out to suppliers. One number for every week, or 13 weekly values. |
| taxes | – | – | VAT and taxes falling due. One number for every week, or 13 weekly values. |
| weekEndsOn | integer | – | Day weeks close on: 0=Sunday … 5=Friday (default), 6=Saturday. |
No output schema declared.
No examples provided.
health Health ~32
Report server status, version and supported languages.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | Language for human-readable labels. Defaults to English. |
No output schema declared.
No examples provided.
What is the 13-Week Cash Flow Plan MCP server?
13-Week Cash Flow Plan is an MCP server listed in the public MCP registry as it.chiriba/cashflow13. 13-week cash flow plan with a live Excel workbook, not just an answer in chat. This page covers its hosted endpoint (https://mcp.chiriba.it/mcp).
Is the 13-Week Cash Flow Plan MCP server safe to use?
13-Week Cash Flow Plan scores 0 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 13-Week Cash Flow Plan MCP server expose?
13-Week Cash Flow Plan exposes 2 tools: health, build_cashflow_plan. Their descriptions and schemas cost roughly 536 tokens of context every time the server is loaded.
Does the 13-Week Cash Flow Plan MCP server require authentication?
Its publisher declares no required credentials for 13-Week Cash Flow Plan. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the 13-Week Cash Flow Plan MCP server still maintained?
13-Week Cash Flow Plan has been deleted from the MCP registry. We last reached this channel on 17 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.