Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Coin IRA Crypto Calculators

REMOTE · COINIRA.COM · SCANNED SEP 20

Historical crypto investment and retirement calculators with cited market data.

Available components

+4 this week 78 Trust /100
Trust breakdown (7 categories)

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 Security74
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 247 tokens (~123/item across 2 items; 2 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
  • Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage74
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 22% 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the Coin IRA Crypto Calculators MCP server?

Coin IRA Crypto Calculators is a hosted endpoint at https://coinira.com/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 · coinira.com

# add to Claude Code
claude mcp add --transport http com-coinira-calculators 'https://coinira.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-coinira-calculators": {
      "url": "https://coinira.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-coinira-calculators": {
      "type": "http",
      "url": "https://coinira.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-coinira-calculators]
url = "https://coinira.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-coinira-calculators": {
      "type": "remote",
      "url": "https://coinira.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-coinira-calculators --url 'https://coinira.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-coinira-calculators:
    url: "https://coinira.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-coinira-calculators": {
      "Transport": "http",
      "Url": "https://coinira.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-coinira-calculators -t streamable-http -u 'https://coinira.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-coinira-calculators": {
      "type": "http",
      "url": "https://coinira.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 5 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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://coinira.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=coinira.com CN=WE1,O=Google Trust Services,C=US 3 Aug 2026 2 Nov 2026 ECDSA 256 ECDSA-SHA256 ea74ff3aade90f4113fc2c0fbe2e3dfc
SANs: coinira.com, *.coinira.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 coinira.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
coinira.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://coinira.com/mcp Verified 200
http (plaintext) http://coinira.com/mcp HTTPS enforced 301 https://coinira.com/mcp
MCP tools · 2 exposed · ~195 tokens

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 →

Tool Tokens
calculate_historical_crypto_investment ~102

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.

NameTypeReqDescription
amountnumberyes
assetstringyes
endstringyesValuation date in YYYY-MM-DD format
startstringyesPurchase date in YYYY-MM-DD format

No output schema declared.

No examples provided.

calculate_retirement_projection ~93

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.

NameTypeReqDescription
annual_returnnumberyes
assetstringyes
monthly_contributionnumberyes
starting_balancenumberyes
yearsintegeryes

No output schema declared.

No examples provided.

Common questions

What is the Coin IRA Crypto Calculators MCP server?

Coin IRA Crypto Calculators is an MCP server listed in the public MCP registry as com.coinira/calculators. Historical crypto investment and retirement calculators with cited market data. This page covers its hosted endpoint (https://coinira.com/mcp).

Is the Coin IRA Crypto Calculators MCP server safe to use?

Coin IRA Crypto Calculators scores 78 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 Coin IRA Crypto Calculators MCP server expose?

Coin IRA Crypto Calculators exposes 2 tools: calculate_historical_crypto_investment, calculate_retirement_projection. Their descriptions and schemas cost roughly 195 tokens of context every time the server is loaded.

Does the Coin IRA Crypto Calculators MCP server require authentication?

No. We connected to Coin IRA Crypto Calculators without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Coin IRA Crypto Calculators MCP server still maintained?

Coin IRA Crypto Calculators 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.