Loan My Coins
REMOTE · LOANMYCOINS.COM
Education-only MCP tools for Bitcoin loan illustrations, from Loan My Coins.
Available components
Last scanned (16 hours ago)
Scores higher than 56% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- 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 Usability58
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1140 tokens (~285/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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 Coverage75
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 13% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “find_answer” rewrote its description, which is the text the model reads security
- Schema quality: 257 → 285 ▼ functional
- Tool coverage: 0% → 13% ▲ functional
- Stability: unverified → 0.03 ▲ functional
- “find_answer” reworded the description of “query” cosmetic
- 16 Nov 26 68
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 21 Nov 2026 · Probed https://loanmycoins.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=loanmycoins.com | CN=Amazon RSA 2048 M01,O=Amazon,C=US | 21 Oct 2026 | 6 May 2027 | RSA 2048 | SHA256-RSA | ea4f85f393bddb4e0eb9b6a4fe33bd8 |
| SANs: loanmycoins.com, www.loanmycoins.com | ||||||
| CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 77312380b9d6688a33b1ed9bf9ccda68e0e0f |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of loanmycoins.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| loanmycoins.com. | No DS | 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 |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://loanmycoins.com/mcp | Verified | 200 | |
| http (plaintext) | http://loanmycoins.com/mcp | HTTPS enforced | 301 | https://loanmycoins.com/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. 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 →
evaluate_btc_loan Evaluate a BTC repurchase illustration ~273
States the documented BTC repurchase illustration in bitcoin: transferred, received, paid at repurchase, returned, and the economic cost. Documented example, per 1 BTC: 1 BTC in, 0.95 BTC received, 0.95 BTC paid at repurchase, 0.95 BTC returned, 0.05 BTC cost, scaled from btcTransferred. An optional hypotheticalValueBtc adds a scenario layer: what the deployed proceeds might be worth in BTC at repurchase, shown against the obligation and against simply holding the original amount. The value is supplied by the caller, never forecast. Equivalently, scenarioReturnPct supplies that scenario as a hypothetical BTC-denominated return in percent on the amount received; the result states the break-even return against simply holding. Supply at most one of the two. Illustrative only. It is not an offer of credit, a price forecast, a tax conclusion, or a suitability finding. It names no borrower outcome. It does not submit an enquiry, request an introduction, or start onboarding. Only a person does that, on the Loan My Coins site.
| Name | Type | Req | Description |
|---|---|---|---|
| btcTransferred | number | yes | – |
| hypotheticalValueBtc | number | – | – |
| scenarioReturnPct | number | – | – |
| useOfProceeds | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| assumptions | array | yes | – |
| btcPaidAtRepurchase | number | yes | – |
| btcReceived | number | yes | – |
| btcReturned | number | yes | – |
| btcTransferred | number | yes | – |
| deployment | – | yes | – |
| economicCostBtc | number | yes | – |
| kind | string | yes | – |
| limitations | array | yes | – |
No examples provided.
find_answer Find a published Loan My Coins answer ~154
Searches Loan My Coins's published answers and returns up to five, word for word as the site publishes them, best first, each with its page url (including a stable answer anchor where the page has one). Only approved published content is returned. Quote the answer text word for word. An empty answers list means no published answer matches: check noMatch for the explanation, and handoff when the question belongs on a sister site or a same-site tool. A handoff is never a published answer from this site and never includes another brand's answer text. Deterministic; no model.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Plain-language question or keywords to look up in Loan My Coins's published answers. Up to 200 characters. |
| Name | Type | Req | Description |
|---|---|---|---|
| answers | array | yes | – |
| handoff | – | yes | – |
| noMatch | – | yes | – |
| notice | string | yes | – |
| pages | array | yes | – |
No examples provided.
prepare_introduction Prepare a Loan My Coins introduction request ~100
Returns the programme, enquiry type, and acquisition-source context for the Loan My Coins introduction form, and where a person can complete it. Programme is always lmc and the enquiry type is always bitcoin_loan_referral. An LMC introduction never creates a TBA advisory commission. It does not fill personal fields and does not submit anything. Only a person submits the form.
| Name | Type | Req | Description |
|---|---|---|---|
| referrerSlug | string | – | – |
| source | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| completeAt | string | yes | – |
| enquiryType | string | yes | – |
| form | string | yes | – |
| pageQuery | string | yes | – |
| programme | string | yes | – |
| referrerSlug | string|null | yes | – |
| source | string | yes | – |
| submission | string | yes | – |
No examples provided.
read_reality_check Read the Reality Check dashboard ~187
Returns one curated weekly Reality Check edition: for Strategy (MSTR), Strive (ASST), and Metaplanet (3350), over 1 week, 1 month, 3 months, 6 months, and 12 months, three separate readings: the equity's unlevered performance relative to BTC, the financed deployment result against holding the original 1 BTC after the documented repurchase economics (break-even needs a 1 BTC terminal value), and coverage of the 0.95 BTC repurchase obligation with any shortfall. Prices are sourced adjusted closes in the edition record; Metaplanet is converted from JPY with the recorded USD/JPY rate. Historical, hypothetical, and retrospective only: not a forecast, a recommendation, or evidence of available contract maturities. Shorter windows are hypothetical holding periods.
| Name | Type | Req | Description |
|---|---|---|---|
| weekEnding | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| companies | array | yes | – |
| editions | array | yes | – |
| methodologyVersion | number | yes | – |
| note | string | yes | – |
| publishedAt | string | yes | – |
| standingNote | string | yes | – |
| url | string | yes | – |
| weekEnding | string | yes | – |
No examples provided.
How do I install the Loan My Coins MCP server?
Loan My Coins is a hosted endpoint at https://loanmycoins.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 · loanmycoins.com
claude mcp add --transport http com-loanmycoins-mcp 'https://loanmycoins.com/mcp'
What is the Loan My Coins MCP server?
Loan My Coins is an MCP server listed in the public MCP registry as com.loanmycoins/mcp. Education-only MCP tools for Bitcoin loan illustrations, from Loan My Coins. This page covers its hosted endpoint (https://loanmycoins.com/mcp).
Is the Loan My Coins MCP server safe to use?
Loan My Coins scores 71 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 Loan My Coins MCP server expose?
Loan My Coins exposes 4 tools: evaluate_btc_loan, find_answer, prepare_introduction, read_reality_check. Their descriptions and schemas cost roughly 714 tokens of context every time the server is loaded.
Does the Loan My Coins MCP server require authentication?
No. We connected to Loan My Coins without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Loan My Coins MCP server still maintained?
Loan My Coins is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Loan My Coins MCP server?
VerifyMCP ran 13 checks on Loan My Coins, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.