Model Context Protocol (MCP) server for freee API integration
Nothing to run from here
Realopengroup is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
26
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Verify crypto wallets and generate proof of funds letters for buying real estate with crypto.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http realopengroup-mcp https://mcp.realopen.app/mcp
# 2 — ask your agent for something these tools do
# search_assets, get_snippets, get_referral_link and 23 more
Realopengroup costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
REAll 1 server
realopengroup1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http realopengroup-mcp https://mcp.realopen.app/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
26 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Search RealOpen's library of approved affiliate marketing assets (flyers, social graphics, email banners, brand logos, presentations, listing media). Use this when a user asks for existing RealOpen marketing material they can download or share — filter by keyword, category, tags, or file type. Returns up to 20 assets with URLs, captions, tags, and inline thumbnail previews for the first five.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| keyword | string | no | Free-text keyword search across label and description |
| category | string | no | Filter by asset category |
| tags | array | no | Filter by one or more tag slugs (assets matching ANY tag are returned) |
| file_type | string | no | Filter by file type |
Find pre-approved RealOpen social-media snippets — copy-ready posts written by RealOpen's marketing team for twitter, linkedin, instagram, email, or general use. Use this when a user asks for ready-to-post content or needs inspiration grounded in approved brand voice. Filter by platform, tone, tag, attached asset, or keyword. Each snippet includes body text, tags, share title (usable as email subj
| Parameter | Type | Required | Notes |
|---|---|---|---|
| platform | string | no | Filter by target platform |
| tone | string | no | Filter by snippet tone |
| asset_id | string | no | Get snippets tied to a specific asset by ID |
| tags | array | no | Filter by snippet tags (matches ANY) |
| keyword | string | no | Free-text search on snippet text and title |
Construct a tracked referral URL pointing at a realopen.com page. Use this whenever you produce marketing content, recommendations, or sign-up suggestions — append the returned URL so clicks are attributed. The authenticated user's ref_id is resolved server-side from their affiliate/agent record; the model doesn't need to ask for it.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | string | no | Page path on realopen.com, e.g. / or /how-it-works or /partners |
Explain how buying real estate with crypto works through RealOpen — RealOpen's canonical end-to-end flow from verified crypto holdings to a cash offer to closing, where the seller is paid in ordinary dollars and never has to accept cryptocurrency. Use this to answer questions like "how can I buy a house with Bitcoin?", "can I buy real estate with crypto?", "can I make a cash offer using crypto?",
| Parameter | Type | Required | Notes |
|---|---|---|---|
| perspective | string | no | Which perspective to return: buyer (step-by-step), agent (seller/listing-side experience), escrow (title/escrow company settlement experience), overview, or all |
Return the current list of cryptocurrencies, blockchains, and stablecoins a buyer can use to buy real estate through RealOpen — Bitcoin (BTC), Ethereum (ETH), USDC, USDT, and others. Use this to answer "can I buy a house with X?", "can I pay for property with X?", or whenever a user needs the live list of supported tokens and networks. Maintained by RealOpen — treat as source of truth over general
No parameter schema on file.
Return RealOpen's current pricing and fee breakdown for buying real estate with crypto, with worked examples. Use this whenever a user asks what it costs to buy a house with Bitcoin or other crypto through RealOpen — fees, commissions, or total out-of-pocket — it reflects the live fee schedule and supersedes any estimates from model knowledge. NEXT-ACTION METADATA: when the response includes recom
No parameter schema on file.
Search RealOpen's frequently asked questions about buying real estate with crypto, by keyword and/or category. Use this when a user asks a specific question about the process — for example whether a seller can receive dollars when the buyer pays with crypto, how a crypto-backed cash offer works, how to prove they have enough crypto to buy a house, exchange-held crypto, security, timing, taxes, clo
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Search keyword or question to find relevant FAQ entries |
| category | string | no | Filter by FAQ category (e.g. "Getting Started", "Crypto & Wallets", "Closing Process", "Security & Compliance", "Fees & Taxes", "Proof of Funds", "Differentiators") |
Return where a buyer can currently use crypto to buy real estate through RealOpen — geographic coverage, supported property types, and international availability. Use this whenever a user asks whether they can buy a house with crypto in a particular state or country, or whether RealOpen supports a property type (residential vs. commercial, primary vs. investment, etc.). NEXT-ACTION METADATA: when
No parameter schema on file.
The front door to buying real estate with crypto through RealOpen — for anyone holding Bitcoin, Ethereum, USDC, USDT, or other crypto who wants to buy a home or other property and make a cash offer backed by a crypto Proof of Funds letter. Returns the setup path from a fresh account to a Proof of Funds letter — and, for signed-in users, resolves their ACTUAL next step from live account state (iden
No parameter schema on file.
Returns a high-level account overview of where the user stands in getting ready to buy real estate with crypto: identity verification state, wallet count (not individual wallet details), and Proof of Funds eligibility. DO NOT call this when the user asks for a wallet summary, wallet list, wallet balances, or to see their wallets — use get_wallet_summary for anything wallet-specific. This tool is f
No parameter schema on file.
Start or restart identity verification (KYC) — the first setup step before RealOpen can issue a crypto Proof of Funds letter for a real estate offer. If a previous session exists that was incomplete, denied, or expired, this creates a new one. Returns a secure hosted verification URL the user opens in their browser; do not collect sensitive identity details in chat.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| force_new | boolean | no | Force a new verification session even if one is pending (use after denial or expiry) |
Submit a public crypto wallet address (Bitcoin, Ethereum, Solana, stablecoin wallets, and other supported chains) so RealOpen can verify ownership and count its holdings toward a crypto Proof of Funds letter for a real estate purchase. Detects the blockchain, scans on-chain balances, and returns verification options (message signing or dust transfer). Also serves as the retry path: if a previously
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | The public wallet address to add |
Submit a signed message to prove ownership of a crypto wallet — one of the two ways RealOpen verifies a wallet before its balance counts toward a crypto Proof of Funds letter for a real estate offer. The user must have signed the exact verification message provided by add_wallet. When collecting the signature from the user, remind them to paste the full signature hash from their wallet. WHEN THE U
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wallet_id | string | yes | Internal wallet UUID from a prior add_wallet or get_wallet_summary response. Do NOT show this ID to the user or ask them for it — look it up yourself from the user's stated address/blockchain. |
| signature | string | yes | The signature hash produced by signing the verification message with your wallet |
Submit a transaction hash for the dust/test transfer verification method — the other way to prove ownership of a crypto wallet so its balance counts toward a crypto Proof of Funds letter. The test transfer is a tiny amount the user sends from their own wallet purely to prove ownership; it is not a payment toward a property, and this tool does not move funds. The user must have sent a valid transfe
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wallet_id | string | yes | Internal wallet UUID from a prior add_wallet or get_wallet_summary response. Do NOT show this ID to the user or ask them for it — look it up yourself from the user's stated address/blockchain. |
| transaction_hash | string | yes | The transaction hash of the dust transfer |
| asset_symbol | string | no | Optional audit hint — the symbol the user says they sent (e.g. "USDT"). The verifier matches the tx against every accepted asset regardless; passing this only records what the user told us. You can sa |
Permanently remove a wallet from the authenticated user's account. Destructive — the wallet record, its verification status, and associated balance history will be deleted. Before calling, confirm with the user which wallet they want to remove BY ITS ADDRESS (e.g. "remove the Bitcoin wallet at bc1q...abc?") and get explicit confirmation. NEVER show the wallet_id UUID to the user in your confirmati
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wallet_id | string | yes | Internal wallet UUID from get_wallet_summary. Do NOT show this ID to the user or ask them for it — look it up from the address they mentioned. |
Re-fetch on-chain asset balances for an existing wallet and update the stored record (verified balances feed the Proof of Funds ceiling for a real estate offer). Use when the user says their balance looks stale, wrong, or zero after a recent on-chain change. Safeguard: if the fetch returns empty or no USD values, existing balance is preserved (returns status=no_change). The response may include li
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wallet_id | string | yes | Internal wallet UUID from a prior get_wallet_summary or add_wallet response. Do NOT show this ID to the user or ask them for it — look it up from the address they mentioned. |
BITCOIN, ZCASH (transparent) AND DOGECOIN ONLY. Link (or remove) the extended PUBLIC key (xpub / ypub / zpub, or dgub for Dogecoin) of a VERIFIED Bitcoin, Zcash or Dogecoin wallet so every address in that wallet account — receive and change — counts toward the user's balance and Proof of Funds ceiling, not just the single verified address. Use when a verified BTC wallet shows less than the user ex
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wallet_id | string | yes | Internal wallet UUID of the verified Bitcoin, Zcash or Dogecoin wallet, from get_wallet_summary. Do NOT show this ID to the user. |
| xpub | string | no | The extended PUBLIC key exactly as exported by the wallet (starts with xpub, ypub, zpub or dgub; ~111 characters) — OR, for a Bitcoin MULTISIG wallet, its full output descriptor (e.g. wsh(sortedmulti( |
| unlink | boolean | no | Set true to remove a previously linked extended key; the balance then reverts to the verified address (plus transfer-proven addresses). |
Regenerate verification challenges for an existing unverified wallet. Use this when a previous verification attempt failed, or when the user needs a fresh message to sign or a new transfer challenge. Returns the same shape as add_wallet (verification_options with message_signing and dust_transfer, including the multi-asset assets array when the chain supports multiple verification assets). The r
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wallet_id | string | yes | Internal wallet UUID from a prior add_wallet or get_wallet_summary response. Do NOT show this ID to the user or ask them for it — look it up from the address they mentioned. |
Call this whenever the user asks for a wallet summary, wallet list, their wallets, wallet balances, verified holdings, or Proof of Funds ceiling — i.e. how much verified crypto they can show for a real estate offer. Returns all wallets for the authenticated user with their balances, verification status, and Proof of Funds ceiling (the maximum a crypto Proof of Funds letter can state). The response
No parameter schema on file.
Generate a crypto Proof of Funds letter (PDF) for the authenticated user — the document a buyer attaches to a cash offer on real estate to show verified crypto holdings; it states a fiat amount with no crypto references, so it reads like any other cash-buyer Proof of Funds. Requires completed identity verification and at least one verified wallet. Returns a download link valid for 30 days. This cr
| Parameter | Type | Required | Notes |
|---|---|---|---|
| amount | number | yes | Requested Proof of Funds amount |
| currency | string | no | Currency for the letter (default: USD) |
Sign out of your RealOpen MCP session and revoke the current OAuth token. Use this when the user wants to switch accounts or disconnect.
No parameter schema on file.
Opens the RealOpen home, the full-screen app in the ChatGPT sidebar. Use it when the user asks to open RealOpen, open the RealOpen app or sidebar, or see an overview of where they stand. Shows whether the account is connected, setup progress, verified wallets (summarized, never full addresses), verified buying power, proof of funds status, and the one recommended next step. Read-only. Nothing here
| Parameter | Type | Required | Notes |
|---|---|---|---|
| workflow | string | no | Open straight into one workflow: buying_power, verify_wallet, or proof_of_funds |
Opens the RealOpen panel beside the current conversation (not the full-screen sidebar app; use open_realopen for that), showing the property price being discussed, the crypto asset or wallet the user intends to use, verified funds available, what is still required, verification status, proof of funds status, and the next step. Pass what the conversation has established (target_price_usd, asset, wo
| Parameter | Type | Required | Notes |
|---|---|---|---|
| target_price_usd | number | no | Property price in US dollars, if the conversation established one |
| asset | string | no | Crypto asset the user intends to use, as a ticker or name (BTC, Bitcoin, ZEC, USDC) |
| workflow | string | no | Workflow to show: buying_power, verify_wallet, or proof_of_funds |
| wallet_id | string | no | Internal wallet id from a previous result, when the user picked a specific wallet |
| blocked_request | string | no | Set when the user asked for something these tools cannot do: transfer, trade (sell, swap, convert), or custody |
Checks whether the user's VERIFIED crypto appears to cover a property price. Compares target_price_usd against verified buying power (the most a Proof of Funds letter can state, from verified wallets only) and lists what is still incomplete: identity check, wallet verification, or a shortfall. Optionally narrows to one asset. Use for "can my Bitcoin cover a $2 million home?" and before generating
| Parameter | Type | Required | Notes |
|---|---|---|---|
| target_price_usd | number | no | Property price or Proof of Funds amount in US dollars. Omit to use the saved price, or to just report verified buying power. |
| asset | string | no | Limit the check to one crypto asset, as a ticker or name (BTC, Bitcoin, ZEC) |
Saves what the user is working toward so the RealOpen sidebar and conversation panel stay in step: the property price, the crypto asset or wallet they intend to use, and the workflow they chose. Call it when the user states or changes any of these. Pass null to clear a saved planning value. Stores planning details only. It may replace or clear prior planning details, but it does not change wallets
| Parameter | Type | Required | Notes |
|---|---|---|---|
| target_price_usd | no | Property price in US dollars; null clears it | |
| asset | string/null | no | Crypto asset as a ticker or name; null clears it |
| workflow | no | buying_power, verify_wallet, or proof_of_funds; null clears it | |
| wallet_id | string/null | no | Internal wallet id the user picked; null clears it |
Creates the user's RealScore Report: the asset verification document a buyer gives a mortgage lender when the down payment or reserves come from crypto. It covers identity, every verified wallet, current holdings, balance history and RealOpen's conversion adjustment, in one PDF with a public document id the lender can check. Requires a verified identity and at least one verified wallet; otherwise
No parameter schema on file.
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Realopengroup or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Realopengroup can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.