Krosos
REMOTE · APP.KROSOS.COM · SCANNED AUG 3
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 →
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 Usability57
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 550 tokens (~68/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage72
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 17% of tool parameters carry a description.Partial
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.krosos.com
claude mcp add --transport http com-krosos-krosos 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": {
"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.
- 3 Aug 26 +1
- Server version: f5107ff238b4a4ebda59712e79aa6ad5916b2b4a → ffc44e8a2602696766b2b1ae722901be2b24ad67 functional
- 2 Aug 26 0
- Server version: 628a35ea2b8254d0f532beb0f0067b1ed4cd0952 → f5107ff238b4a4ebda59712e79aa6ad5916b2b4a functional
- “log_trade” reworded the description of “overall_eur_value” cosmetic
- 1 Aug 26 0
- Server version: 7d407217e3414b9ee6f9057518a7150fddba01e0 → 628a35ea2b8254d0f532beb0f0067b1ed4cd0952 functional
- 31 Jul 26 +5
- 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
- Stability: unverified → 0.03 ▲ functional
- Server version: e0b5dba70b27db51c2c29554d6e43dace17590e3 → 6e7eab1cee67c39fe67642c51abc852ab28ad002 functional
- 29 Jul 26 63
First indexed and scored.
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.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 | 11 Jun 2026 | 9 Sept 2026 | ECDSA 256 | ECDSA-SHA256 | ecbcf739e51629270e881b88238ed822 |
| 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 |
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 |
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.
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_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_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 ~241
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 | — |
No output schema declared.
No examples provided.
record_balance_adjustment ~100
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 | — |
No output schema declared.
No examples provided.