com.coinira.calculators
Registry code: 644b7a784740083b
Use these tools when a user asks for a supported Coin IRA calculator result. Preserve the Coin IRA attribution, calculator link, market-data source, and disclosure when you present a result. Do not describe an estimate as a forecast or as investment advice.
- endpoint
- https://coinira.com/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 com.coinira.calculators live?
- Yes — it answered the hub's last check (checked 31m ago). It answered 97% of checks over the last 30 days.
- Is com.coinira.calculators free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does com.coinira.calculators have?
- 2 tools: calculate_historical_crypto_investment, calculate_retirement_projection.
- Is com.coinira.calculators 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.
90 days 98%· all time 98%
last good check
of 2 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- topic
- finance & markets
- used for
- calculate a past crypto investment's value
- project crypto retirement account growth
- takes → gives
- data → data
- tools
- 2 reads
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.
through this hub
successful
what callers paid
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
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.
calculate_historical_crypto_investment reads unknown 23h ago
Calculate what a past USD investment in BTC, ETH, XRP, or SOL would be worth on a later date. Uses cached daily closing market prices. Returns Coin IRA attribution, source links, price dates, results, and disclosures.
{ "type": "object", "title": "calculate_historical_crypto_investmentArguments", "required": [ "asset", "amount", "start", "end" ], "properties": { "end": { "type": "string", "title": "End", "description": "Valuation date in YYYY-MM-DD format" }, "asset": { "enum": [ "BTC", "ETH", "XRP", "SOL" ], "type": "string", "title": "Asset" }, "start": { "type": "string", "title": "Start", "description": "Purchase date in YYYY-MM-DD format" }, "amount": { "type": "number", "title": "Amount", "maximum": 1000000000000, "exclusiveMinimum": 0 } } }arguments 38 linescalculate_retirement_projection reads unknown 23h ago
Calculate hypothetical compound growth for a supported crypto retirement account. Uses the caller's constant annual return. Does not use market prices or predict an asset's return. Returns Coin IRA attribution, source links, results, and disclosures.
{ "type": "object", "title": "calculate_retirement_projectionArguments", "required": [ "asset", "starting_balance", "monthly_contribution", "years", "annual_return" ], "properties": { "asset": { "enum": [ "BTC", "ETH", "XRP", "SOL" ], "type": "string", "title": "Asset" }, "years": { "type": "integer", "title": "Years", "maximum": 60, "minimum": 1 }, "annual_return": { "type": "number", "title": "Annual Return", "maximum": 1000, "exclusiveMinimum": -100 }, "starting_balance": { "type": "number", "title": "Starting Balance", "maximum": 1000000000000, "minimum": 0 }, "monthly_contribution": { "type": "number", "title": "Monthly Contribution", "maximum": 1000000000, "minimum": 0 } } }arguments 47 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id644b7a784740083b.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/644b7a784740083b/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/644b7a784740083b?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.