_ registry / mcp streamable-http · checked 19m ago

krosos

https://app.krosos.com

Registry code: b3f141a7232e6796

api record

Your accounting ledger as typed tools: net worth, holdings, history, tax estimates, trade logging.

from a public catalogue that lists it, not from the operator

endpoint
https://app.krosos.com/api/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is krosos live?
Yes — it answered the hub's last check (checked 19m ago). It answered 100% of checks over the last 30 days.
Is krosos free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does krosos have?
12 tools: sync_connections, get_dashboard, list_transactions, get_reference_data, refresh_prices, get_net_worth_history, get_tax_report, get_projection_config, ….
Is krosos safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
145ms

last good check

priced tools
0

of 12 tools

_ answered our checks, 90 days 327 checks · signed record
  • degraded → live
  • unknown → live
_ what it is for
topic
finance & markets accounting & tax
used for
  • get net worth and holdings
  • get net worth history
  • estimate capital gains tax
  • log a trade in the ledger
  • sync linked accounts
takes → gives
data → data
tools
8 reads4 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 12 tools
12 auth-required 12 of 12 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • sync_connections changes data auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {}
}
    arguments 5 lines
  • get_dashboard reads auth-required 18h ago

    Net worth, balance sheet and current holdings, in the ledger's base currency.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {}
}
    arguments 5 lines
  • list_transactions reads auth-required 11h ago

    Transaction history as a human-friendly list, newest first.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {}
}
    arguments 5 lines
  • get_reference_data reads auth-required 3h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {}
}
    arguments 5 lines
  • refresh_prices changes data auth-required never probed

    Fetch fresh market prices now. With no ticker this refreshes every priced holding; with one it refreshes just that ticker.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "symbol": {
      "type": "string",
      "description": "Provider symbol when it differs from the ticker"
    },
    "ticker": {
      "type": "string",
      "description": "Omit to refresh every ticker"
    }
  }
}
    arguments 14 lines
  • get_net_worth_history reads auth-required 11h ago

    Historical net-worth snapshots (one point per day where recorded).

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {}
}
    arguments 5 lines
  • get_tax_report reads auth-required 18h ago

    Capital-gains / income tax estimate for a year: gains, losses, exemption (including any carried-forward amount), taxable base and estimated tax.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "year": {
      "type": "string",
      "description": "Defaults to the current year"
    },
    "account": {
      "type": "string",
      "description": "One portfolio; absent sums every configured one"
    }
  }
}
    arguments 14 lines
  • get_projection_config reads auth-required 11h ago

    The forecast/FIRE plan's assumptions (salary, expenses, inflation, retirement dates, tax mode). The projection itself is computed client-side.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {}
}
    arguments 5 lines
  • get_prices reads auth-required 3h ago

    Current price per ticker with its source, quote currency and recent change, plus any manual overrides.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {}
}
    arguments 5 lines
  • list_connections reads auth-required 18h ago

    Linked exchange, bank and wallet connections, each with its sync mode (balance updates, or transactions staged for review) and when it last synced.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {}
}
    arguments 5 lines
  • log_trade changes data auth-required never probed

    Log a trade (buy / sell / swap), expressed as from-asset to to-asset. Same body and validation as POST /api/transactions.

    mcp-tool

    {
  "type": "object",
  "required": [
    "tx_date",
    "from_account",
    "from_provider",
    "from_ticker",
    "from_asset",
    "from_amount",
    "to_account",
    "to_provider",
    "to_ticker",
    "to_asset",
    "to_amount",
    "overall_eur_value"
  ],
  "properties": {
    "to_risk": {
      "type": "integer",
      "maximum": 4,
      "minimum": 0
    },
    "tx_date": {
      "type": "string",
      "format": "date",
      "example": "2026-06-17",
      "description": "Today or tomorrow at the latest (the user's own calendar day); later dates are rejected"
    },
    "tx_time": {
      "type": "string",
      "example": "14:30",
      "description": "Optional HH:MM on the user's own clock; orders rows within the same day. Omitted: an edit keeps the stored time, a new row takes the current time"
    },
    "to_asset": {
      "type": "string"
    },
    "from_risk": {
      "type": "integer",
      "maximum": 4,
      "minimum": 0
    },
    "to_amount": {
      "type": "number",
      "example": 8.5
    },
    "to_ticker": {
      "type": "string"
    },
    "from_asset": {
      "type": "string"
    },
    "to_account": {
      "type": "string"
    },
    "description": {
      "type": "string"
    },
    "from_amount": {
      "type": "number",
      "example": 1000
    },
    "from_ticker": {
      "type": "string"
    },
    "to_category": {
      "type": "string"
    },
    "to_provider": {
      "type": "string"
    },
    "from_account": {
      "type": "string"
    },
    "from_category": {
      "type": "string"
    },
    "from_provider": {
      "type": "string"
    },
    "to_description": {
      "type": "string"
    },
    "allow_new_values": {
      "type": "boolean",
      "description": "Create accounts/providers/tickers not yet in reference-data. Default false."
    },
    "from_description": {
      "type": "string"
    },
    "overall_eur_value": {
      "type": "number",
      "example": 1000,
      "description": "The trade's total value in the ledger's base currency (the field name is historical: EUR was the only base)"
    }
  }
}
    arguments 96 lines
  • record_balance_adjustment changes data auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "tx_date",
    "account",
    "provider",
    "ticker",
    "asset",
    "quantity_delta"
  ],
  "properties": {
    "asset": {
      "type": "string"
    },
    "ticker": {
      "type": "string"
    },
    "account": {
      "type": "string"
    },
    "tx_date": {
      "type": "string",
      "format": "date",
      "description": "Today or tomorrow at the latest (the user's own calendar day); later dates are rejected"
    },
    "tx_time": {
      "type": "string",
      "example": "14:30",
      "description": "Optional HH:MM on the user's own clock; orders rows within the same day. Omitted: an edit keeps the stored time, a new row takes the current time"
    },
    "provider": {
      "type": "string"
    },
    "quantity_delta": {
      "type": "number",
      "description": "Signed quantity change (non-zero)"
    },
    "allow_new_values": {
      "type": "boolean"
    }
  }
}
    arguments 42 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id b3f141a7232e6796.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/b3f141a7232e6796/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/b3f141a7232e6796/badge.svg)](https://brick.blue/agent/b3f141a7232e6796?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.