Krosos
REMOTE · APP.KROSOS.COM · SCANNED SEP 20
Your accounting ledger as typed tools: net worth, holdings, history, tax estimates, trade logging.
Available components
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- 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 Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 757 tokens (~63/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage76
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 29% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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
How do I install the Krosos MCP server?
Krosos is a hosted endpoint at https://app.krosos.com/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.krosos.com
claude mcp add --transport http com-krosos-krosos 'https://app.krosos.com/api/mcp'
{
"mcpServers": {
"com-krosos-krosos": {
"url": "https://app.krosos.com/api/mcp"
}
}
} {
"servers": {
"com-krosos-krosos": {
"type": "http",
"url": "https://app.krosos.com/api/mcp"
}
}
} [mcp_servers.com-krosos-krosos] url = "https://app.krosos.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-krosos-krosos": {
"type": "remote",
"url": "https://app.krosos.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-krosos-krosos --url 'https://app.krosos.com/api/mcp' --transport streamable-http
mcp_servers:
com-krosos-krosos:
url: "https://app.krosos.com/api/mcp" {
"McpServers": {
"com-krosos-krosos": {
"Transport": "http",
"Url": "https://app.krosos.com/api/mcp"
}
}
} assistant mcp add com-krosos-krosos -t streamable-http -u 'https://app.krosos.com/api/mcp'
{
"mcpServers": {
"com-krosos-krosos": {
"type": "http",
"url": "https://app.krosos.com/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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 Sept 26 0
- Server version: bf58b13f4495f343e5f4208c1c6030529c41f331 → 780ec3d643c14d2681be967c845ef1ef0f386f59 functional
- 18 Sept 26 0
- Server version: d839944b8f48cce343974934bd0d00cf23934d12 → bf58b13f4495f343e5f4208c1c6030529c41f331 functional
- 16 Sept 26 0
- Server version: 5507e385ea4b7bd04e243a80f0c2ce32d606a439 → d839944b8f48cce343974934bd0d00cf23934d12 functional
- 12 Sept 26 0
- Server version: 2c295745604b3ab7f193c165ec0bc329dfe5bc39 → 5507e385ea4b7bd04e243a80f0c2ce32d606a439 functional
- 10 Sept 26 0
- Server version: f6640457813d77ea97e07475777ea295202a4f32 → 2c295745604b3ab7f193c165ec0bc329dfe5bc39 functional
- 9 Sept 26 0
- Server version: 05109d787fa9134ccd3736ab66d9b91ffa010474 → f6640457813d77ea97e07475777ea295202a4f32 functional
- 8 Sept 26 0
- Tool coverage: 23% → 29% ▲ functional
- Server version: 770b67795996d8dd120b10a8bcea6a9ad26dce37 → 05109d787fa9134ccd3736ab66d9b91ffa010474 functional
- “log_trade” reworded the description of “tx_date” cosmetic
- “record_balance_adjustment” reworded the description of “tx_date” cosmetic
- 4 Sept 26 0
- Server version: abafd6e4c9cf03878397681a34264607b82c706c → 770b67795996d8dd120b10a8bcea6a9ad26dce37 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 20 Sept 2026 · Probed https://app.krosos.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=krosos.com | CN=WE1,O=Google Trust Services,C=US | 9 Aug 2026 | 7 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | e8beee1252ff8be5134650baca1f2c64 |
| SANs: krosos.com, *.krosos.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of app.krosos.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| krosos.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| content-security-policy | script-src 'self'; frame-ancestors 'none'; base-uri 'self'; object-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://app.krosos.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://app.krosos.com/api/mcp | HTTPS enforced | 301 | https://app.krosos.com/api/mcp |
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 →
get_dashboard ~24
Net worth, balance sheet and current holdings, in the ledger's base currency.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_net_worth_history ~23
Historical net-worth snapshots (one point per day where recorded).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_prices ~27
Current price per ticker with its source, quote currency and recent change, plus any manual overrides.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_projection_config ~37
The forecast/FIRE plan's assumptions (salary, expenses, inflation, retirement dates, tax mode). The projection itself is computed client-side.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_reference_data ~41
Valid accounts, providers, tickers, asset classes and categories. Read this before writing: trades and adjustments must use these values unless allow_new_values is set.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_tax_report ~65
Capital-gains / income tax estimate for a year: gains, losses, exemption (including any carried-forward amount), taxable base and estimated tax.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | One portfolio; absent sums every configured one |
| year | string | – | Defaults to the current year |
No output schema declared.
No examples provided.
list_connections ~37
Linked exchange, bank and wallet connections, each with its sync mode (balance updates, or transactions staged for review) and when it last synced.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_transactions ~19
Transaction history as a human-friendly list, newest first.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
log_trade ~258
Log a trade (buy / sell / swap), expressed as from-asset to to-asset. Same body and validation as POST /api/transactions.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_new_values | boolean | – | Create accounts/providers/tickers not yet in reference-data. Default false. |
| description | string | – | – |
| from_account | string | yes | – |
| from_amount | number | yes | – |
| from_asset | string | yes | – |
| from_category | string | – | – |
| from_description | string | – | – |
| from_provider | string | yes | – |
| from_risk | integer | – | – |
| from_ticker | string | yes | – |
| overall_eur_value | number | yes | The trade's total value in the ledger's base currency (the field name is historical: EUR was the only base) |
| to_account | string | yes | – |
| to_amount | number | yes | – |
| to_asset | string | yes | – |
| to_category | string | – | – |
| to_description | string | – | – |
| to_provider | string | yes | – |
| to_risk | integer | – | – |
| to_ticker | string | yes | – |
| tx_date | string | yes | Today or tomorrow at the latest (the user's own calendar day); later dates are rejected |
No output schema declared.
No examples provided.
record_balance_adjustment ~117
Record a signed quantity change on one holding (a balance update that is not a trade). Same body and validation as POST /api/position-adjustments.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | – |
| allow_new_values | boolean | – | – |
| asset | string | yes | – |
| provider | string | yes | – |
| quantity_delta | number | yes | Signed quantity change (non-zero) |
| ticker | string | yes | – |
| tx_date | string | yes | Today or tomorrow at the latest (the user's own calendar day); later dates are rejected |
No output schema declared.
No examples provided.
refresh_prices ~61
Fetch fresh market prices now. With no ticker this refreshes every priced holding; with one it refreshes just that ticker.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | – | Provider symbol when it differs from the ticker |
| ticker | string | – | Omit to refresh every ticker |
No output schema declared.
No examples provided.
sync_connections ~48
Sync every linked connection in one pass: push the latest balance into each linked holding, and stage new transactions into the review queue. Reports what was written, what was staged and any per-provider errors.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the Krosos MCP server?
Krosos is an MCP server listed in the public MCP registry as com.krosos/krosos. Your accounting ledger as typed tools: net worth, holdings, history, tax estimates, trade logging. This page covers its hosted endpoint (https://app.krosos.com/api/mcp).
Is the Krosos MCP server safe to use?
Krosos scores 88 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 Krosos MCP server expose?
Krosos exposes 12 tools: get_dashboard, get_net_worth_history, list_transactions, get_reference_data, get_tax_report, and 7 more. Their descriptions and schemas cost roughly 757 tokens of context every time the server is loaded.
Does the Krosos MCP server require authentication?
Yes. Krosos asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Krosos MCP server still maintained?
Krosos 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.