mcp-registry/com.krosos/krosos · v47138908edbef764ce6d610b975ef66c16ef99cc
As of 2026-10-25 09:02 UTC, the Krosos MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Your accounting ledger as typed tools: net worth, holdings, history, tax estimates, trade logging.
Claude Code
claude mcp add --transport http krosos-mcp-server https://app.krosos.com/api/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"krosos-mcp-server": {
"type": "http",
"url": "https://app.krosos.com/api/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
12 of 12 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
22 parameter(s) across 2 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
In the last 30 days: 0 tool(s) removed and 2 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 2 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.krosos%2Fkrosos/fixes
{
"name": "get_dashboard",
"description": "Net worth, balance sheet and current holdings, in the ledger's base currency.",
"inputSchema": {
"type": "object",
"required": [],
"properties": {}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_net_worth_history",
"description": "Historical net-worth snapshots (one point per day where recorded).",
"inputSchema": {
"type": "object",
"required": [],
"properties": {}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_prices",
"description": "Current price per ticker with its source, quote currency and recent change, plus any manual overrides.",
"inputSchema": {
"type": "object",
"required": [],
"properties": {}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.krosos/krosos"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.krosos/krosos"}) over MCP.
log_trade ~470 tokensrecord_balance_adjustment ~254 tokensget_tax_report ~114 tokensrefresh_prices ~108 tokenssync_connections ~89 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.krosos%2Fkrosos?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.krosos%2Fkrosos?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.krosos%2Fkrosos.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.krosos%2Fkrosos.svg :target: https://glimind.com/server/mcp-registry%2Fcom.krosos%2Fkrosos?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:9bcbfd01901901e6…, first seen 2026-10-17, included at leaf 4150 of 65,003. Version history · verify what your client received.
Compare: most reliable finance servers · most reliable data servers · most reliable knowledge servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-25 09:02 UTC, the Krosos MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Krosos MCP server advertises 12 tools, including get_dashboard, get_net_worth_history, get_prices, get_projection_config, get_reference_data.
Point your MCP client at this streamable-http endpoint: https://app.krosos.com/api/mcp
Glimind scanned all 12 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.