YieldLord · 包租公
REMOTE · BAOZUGONG.APP · SCANNED OCT 4
RENT-ranked covered-call, CSP & wheel income ideas, your positions & Greeks. Never places orders.
Available components
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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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 Usability77
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1524 tokens (~190/item across 8 items; 4 tools + 4 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 Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage85
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 55% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the YieldLord · 包租公 MCP server?
YieldLord · 包租公 is a hosted endpoint at https://baozugong.app/api/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 · baozugong.app
claude mcp add --transport http app-baozugong-landlord 'https://baozugong.app/api/mcp'
{
"mcpServers": {
"app-baozugong-landlord": {
"url": "https://baozugong.app/api/mcp"
}
}
} {
"servers": {
"app-baozugong-landlord": {
"type": "http",
"url": "https://baozugong.app/api/mcp"
}
}
} [mcp_servers.app-baozugong-landlord] url = "https://baozugong.app/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"app-baozugong-landlord": {
"type": "remote",
"url": "https://baozugong.app/api/mcp",
"enabled": true
}
}
} openclaw mcp add app-baozugong-landlord --url 'https://baozugong.app/api/mcp' --transport streamable-http
mcp_servers:
app-baozugong-landlord:
url: "https://baozugong.app/api/mcp" {
"McpServers": {
"app-baozugong-landlord": {
"Transport": "http",
"Url": "https://baozugong.app/api/mcp"
}
}
} assistant mcp add app-baozugong-landlord -t streamable-http -u 'https://baozugong.app/api/mcp'
{
"mcpServers": {
"app-baozugong-landlord": {
"type": "http",
"url": "https://baozugong.app/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Oct 26 +1
- Tool “connect_my_account” rewrote its description, which is the text the model reads security
- Schema quality: 164 → 190 ▼ functional
- Tool coverage: 47% → 55% ▲ functional
- “connect_my_account” added an optional parameter “agent_name” cosmetic
- “connect_my_account” added an optional parameter “pickup” cosmetic
- “connect_my_account” added an optional parameter “start_link” cosmetic
- “connect_my_account” reworded the description of “start_authorization” cosmetic
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 +7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 0
- Tool “connect_my_account” rewrote its description, which is the text the model reads security
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
- Tool “connect_my_account” rewrote its description, which is the text the model reads security
- Schema quality: 138 → 159 ▼ functional
- Tool coverage: 40% → 47% ▲ functional
- “connect_my_account” added an optional parameter “confirm” cosmetic
- “connect_my_account” added an optional parameter “start_trial” cosmetic
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 8 Oct 2026 · Probed https://baozugong.app/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=baozugong.app | CN=YR2,O=Let's Encrypt,C=US | 1 Oct 2026 | 30 Dec 2026 | RSA 2048 | SHA256-RSA | 5d2f420176e1d85f38c1d399ce74f881911 |
| SANs: baozugong.app | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of baozugong.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| baozugong.app. | 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 |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://baozugong.app/api/mcp | Verified | 200 | |
| http (plaintext) | http://baozugong.app/api/mcp | HTTPS enforced | 308 | https://baozugong.app/api/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 →
connect_my_account ~620
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, and this explains what connecting unlocks and gives the link. Called with no arguments it returns text and a URL only. Call it again with start_authorization=true once the user has an account, to begin the OAuth flow — or, if you can't receive a browser redirect, with start_link=true (a link the user approves, then pickup=<pickup> gives you the token; nothing to copy back). A connected free account can also start its free Gold trial here (start_trial=true — always a two-step confirm with the user) or get the link to buy Gold. Call it again right after the user finishes signing in: for a connected account the reply lists every tool the connection unlocked (the tool list you fetched before sign-in only has the public ones — re-list tools after connecting).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_name | string | – | With start_link: your name as the user knows you (shown on the approval page). |
| confirm | string | – | The confirm_token from the previous start_trial call, sent only after the user said yes. |
| pickup | string | – | The pickup from start_link. Returns pending until the user approves, then the access token (once). |
| start_authorization | boolean | – | 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 cli… |
| start_link | boolean | – | 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 —… |
| start_trial | boolean | – | 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,… |
No output schema declared.
No examples provided.
explain_option ~216
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 collateral per contract, annualized yield, the chance it expires worthless (the SELLER's side), and the RENT score. If we cannot price it (no open interest, no bid, strike does not exist) it says so and why, rather than substituting a different contract. Output is analysis, not a recommendation to trade.
| Name | Type | Req | Description |
|---|---|---|---|
| expiry | string | yes | YYYY-MM-DD |
| intent | string | – | defaults to csp for a put, covered_call for a call |
| lang | string | – | – |
| risk | string | – | – |
| strike | number | yes | – |
| ticker | string | yes | – |
| type | string | yes | – |
No output schema declared.
No examples provided.
find_recommendations ~223
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.
| Name | Type | Req | Description |
|---|---|---|---|
| defined_risk | boolean | – | 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 p… |
| direction | string | – | – |
| intent | string | – | – |
| risk | string | – | – |
| ticker | string | yes | – |
| timeframe | string | – | target DTE in days, e.g. 21/30/45 (default 30) |
| wing | string | – | Spread width, only meaningful with defined_risk=true: tight = least buying power, wide = more credit. |
No output schema declared.
No examples provided.
get_market_climate ~42
Current rent climate (market regime + VIX/IV env + macro proximity → seller-friendliness read). Output is analysis, not a recommendation to trade.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the YieldLord · 包租公 MCP server?
YieldLord · 包租公 is an MCP server listed in the public MCP registry as app.baozugong/landlord. RENT-ranked covered-call, CSP & wheel income ideas, your positions & Greeks. Never places orders. This page covers its hosted endpoint (https://baozugong.app/api/mcp).
Is the YieldLord · 包租公 MCP server safe to use?
YieldLord · 包租公 scores 76 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 YieldLord · 包租公 MCP server expose?
YieldLord · 包租公 exposes 4 tools: find_recommendations, get_market_climate, explain_option, connect_my_account. Their descriptions and schemas cost roughly 1,101 tokens of context every time the server is loaded.
Does the YieldLord · 包租公 MCP server require authentication?
No. We connected to YieldLord · 包租公 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the YieldLord · 包租公 MCP server still maintained?
YieldLord · 包租公 is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.