Loan My Coins MCP server
com.loanmycoins/mcploanmycoins.comstreamable-httpv0.1.0Scanned
Education-only MCP tools for Bitcoin loan illustrations, from Loan My Coins.
4 tools: 1 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Loan My Coins MCP server can do
The Loan My Coins MCP server is published by loanmycoins.com, a domain the MCP Registry verified. It has 4 tools. It can create or change data (1 tool: evaluate_btc_loan), but cannot delete data. 3 tools only read.
1 tool brings in text other people can write (find_answer).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 16, 2026, version 0.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Changes things 1Claude Code: ask
evaluate_btc_loanStates the documented BTC repurchase illustration in bitcoin: transferred, received, paid at repurchase, returned, and the economic cost.1 finding
Why it is in this group
- The name "evaluate_btc_loan" says "evaluate": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "evaluate_btc_loan" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "evaluate_btc_loan" says "evaluate": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- title: Evaluate a BTC repurchase illustration
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 3Show 3 read-only tools
find_answerSearches 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.Reads text others writeNo findings
Why it is in this group
- The name "find_answer" says "find": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "search" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it 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. Only approved published content is returned; an empty answers list means no published answer matches. Deterministic; no model.
Annotations the server declares
- title: Find a published Loan My Coins answer
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
prepare_introductionReturns the programme, enquiry type, and acquisition-source context for the Loan My Coins introduction form, and where a person can complete it.No findings
Why it is in this group
- The description's first verb is "return": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Prepare a Loan My Coins introduction request
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
read_reality_checkReturns 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…No findings
Why it is in this group
- The name "read_reality_check" says "read": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Read the Reality Check dashboard
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 16, 2026, 14:19 UTC, unchanged since Nov 16, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://loanmycoins.com/mcp: tools/list returned 4 tools to an anonymous client, including evaluate_btc_loan (write)
Findings
Matches of fixed checks, with the text they matched.
The server marks "evaluate_btc_loan" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "evaluate_btc_loan" says "evaluate": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http loanmycoins https://loanmycoins.com/mcpclaude mcp add --transport http loanmycoins https://loanmycoins.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__loanmycoins__find_answer",
"mcp__loanmycoins__prepare_introduction",
"mcp__loanmycoins__read_reality_check"
],
"ask": [
"mcp__loanmycoins__evaluate_btc_loan"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as loanmycoins. Review it before you use it.
Capability tags behind 1 rule
- mcp__loanmycoins__find_answer untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.loanmycoins/mcp/verify?hash=abc84790b43be350cde9f492997bd88926d294a98e1c84450586520e0c2443d4" | jq -e '.changed == false'Pinned hash abc84790b43b, from Nov 16, 2026, 02:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.loanmycoins/mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.loanmycoins/mcp)Source: MCP Registry. Synced Nov 16, 2026, 02:17 UTC.
Loan My Coins MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Loan My Coins MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 1 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Loan My Coins MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Loan My Coins MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Loan My Coins MCP server have?
- 4 tools: 1 write, 3 read. evaluate_btc_loan, find_answer, prepare_introduction and read_reality_check.
Does the Loan My Coins MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Loan My Coins MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Loan My Coins MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.