Model Context Protocol (MCP) server for freee API integration
Nothing to run from here
YieldLord · Rent Collector 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.
93/100
tool-list score
4
tools declared
remote
at its publisher
—
calls last 7d
What it does
RENT-ranked covered-call, CSP & wheel income ideas, your positions & Greeks. Never places orders.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http yieldlord-mcp https://baozugong.app/api/mcp
# 2 — ask your agent for something these tools do
# find_recommendations, get_market_climate, explain_option and 1 more
YieldLord · Rent Collector costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
BAAll 1 server
baozugong1 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 yieldlord-mcp https://baozugong.app/api/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
4 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.
Find RENT-ranked option income candidates (candidates only, not advice) for a ticker. Set defined_risk=true for CREDIT SPREADS (bull put / bear call) instead of single-leg naked selling; omit it and we default to whatever this user actually trades. Output is analysis, not a recommendation to trade.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticker | string | yes | — |
| intent | string | no | — |
| risk | string | no | — |
| direction | string | no | — |
| defined_risk | boolean | no | true = attach a protective long leg → CREDIT SPREAD (bull put / bear call). false = single-leg naked selling. Omit to use what this user actually trades (inferred from their open positions and last pi |
| wing | string | no | Spread width, only meaningful with defined_risk=true: tight = least buying power, wide = more credit. |
| timeframe | string | no | target DTE in days, e.g. 21/30/45 (default 30) |
Current rent climate (market regime + VIX/IV env + macro proximity → seller-friendliness read). Output is analysis, not a recommendation to trade.
No parameter schema on file.
Explain ONE specific option contract the user named — ticker + put/call + strike + expiry. Unlike explain_score and compare_candidates, which can only explain contracts the engine already picked, this prices and scores the exact contract you ask about, including strikes the screener would never surface (deep in the money, far out of the money). Returns the live quote, Greeks, premium and collatera
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticker | string | yes | — |
| type | string | yes | — |
| strike | number | yes | — |
| expiry | string | yes | YYYY-MM-DD |
| intent | string | no | defaults to csp for a put, covered_call for a call |
| risk | string | no | — |
| lang | string | no | — |
Account status: whether this session is connected to a 包租公 · YieldLord account, which tier it is on, how many credits are left, and for Gold whether it is a trial or paid and when it ends. Call this when the user asks "am I connected" or "how many credits do I have left", and when they ask about THEIR OWN positions, portfolio, morning brief or realized history — anonymous access cannot see those,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start_authorization | boolean | no | Begin the OAuth flow now. The call answers HTTP 401 with a WWW-Authenticate header pointing at this server's protected-resource metadata; follow it (dynamic client registration, PKCE S256, public clie |
| start_link | boolean | no | Easiest way to connect if you can't receive a browser redirect (you run on a server): returns a link and a code to give the user, plus a pickup for you. The user signs in and approves on that page — n |
| agent_name | string | no | With start_link: your name as the user knows you (shown on the approval page). |
| pickup | string | no | The pickup from start_link. Returns pending until the user approves, then the access token (once). |
| start_trial | boolean | no | Connected free accounts only: start the free Gold trial. Without confirm nothing is started — it returns a question for the user and a confirm_token. Ask the user; only after they clearly say yes, c |
| confirm | string | no | The confirm_token from the previous start_trial call, sent only after the user said yes. |
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 YieldLord · Rent Collector 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: —
ATool-list grade · score 93 / 100
Release 1.2.0 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
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.
Threat score100
Client score93
Findings0 threat · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest752a396f9d4772dad568007019610837c5c1901f010edc69ffb2a391c1be0c04
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| find_recommendations | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_market_climate | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| explain_option | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| connect_my_account | state-write | state-write: declares readOnlyHint: false |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest752a396f9d4772da
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
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.2.0.
1.2.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 YieldLord · Rent Collector 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.