yieldprobe: DeFi intel for agents
REMOTE · YIELDPROBE.COM · SCANNED SEP 25
Paid DeFi data for agents via x402 on Base: yields, APY moves, stablecoin pegs, token risk.
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 446 tokens (~89/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 76% 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 5 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the yieldprobe: DeFi intel for agents MCP server?
yieldprobe: DeFi intel for agents is a hosted endpoint at https://yieldprobe.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 · yieldprobe.com
claude mcp add --transport http com-yieldprobe-defi-intel 'https://yieldprobe.com/mcp'
{
"mcpServers": {
"com-yieldprobe-defi-intel": {
"url": "https://yieldprobe.com/mcp"
}
}
} {
"servers": {
"com-yieldprobe-defi-intel": {
"type": "http",
"url": "https://yieldprobe.com/mcp"
}
}
} [mcp_servers.com-yieldprobe-defi-intel] url = "https://yieldprobe.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-yieldprobe-defi-intel": {
"type": "remote",
"url": "https://yieldprobe.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-yieldprobe-defi-intel --url 'https://yieldprobe.com/mcp' --transport streamable-http
mcp_servers:
com-yieldprobe-defi-intel:
url: "https://yieldprobe.com/mcp" {
"McpServers": {
"com-yieldprobe-defi-intel": {
"Transport": "http",
"Url": "https://yieldprobe.com/mcp"
}
}
} assistant mcp add com-yieldprobe-defi-intel -t streamable-http -u 'https://yieldprobe.com/mcp'
{
"mcpServers": {
"com-yieldprobe-defi-intel": {
"type": "http",
"url": "https://yieldprobe.com/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.
- 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 66
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 25 Sept 2026 · Probed https://yieldprobe.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=yieldprobe.com | CN=YE2,O=Let's Encrypt,C=US | 23 Sept 2026 | 22 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 696a364e5f5065dc9e88428f11581b51ce8 |
| SANs: *.yieldprobe.com, yieldprobe.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of yieldprobe.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| yieldprobe.com. | 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=31536000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://yieldprobe.com/mcp | Verified | 200 | |
| http (plaintext) | http://yieldprobe.com/mcp | HTTPS enforced | 301 | https://yieldprobe.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 →
defi_top_yields Top DeFi yields ~157
Top DeFi pools by APY with 30d mean, volatility, IL risk and forecast; filter by chain, project, stablecoin, TVL. Signed and timestamped. $0.002 per call.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Chain name: Ethereum, Base, Arbitrum, Solana... |
| limit | integer | – | Default 20 |
| maxSigma | number | – | Max APY volatility |
| minTvl | number | – | Minimum TVL in USD, default 1e6 |
| project | string | – | Protocol slug, e.g. aave-v3 |
| stable | boolean | – | Only stablecoin pools |
| symbol | string | – | Substring match on pool symbol |
No output schema declared.
No examples provided.
defi_yield_movers APY movers ~90
Pools with the largest APY change over 1d or 7d, up and down. Anomaly feed. $0.002 per call.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | – |
| limit | integer | – | Pools per side, default 10 |
| minTvl | number | – | Minimum TVL in USD, default 5e6 |
| window | string | – | – |
No output schema declared.
No examples provided.
stablecoin_peg_monitor Stablecoin peg monitor ~114
Every depegged USD stablecoin plus the largest by supply, with price deviation and 1d/7d supply change. $0.002 per call.
| Name | Type | Req | Description |
|---|---|---|---|
| full | boolean | – | Return every tracked coin (large) |
| limit | integer | – | Largest stablecoins to include, default 20 |
| minCirculating | number | – | USD floor, default 1e7 |
| threshold | number | – | Abs deviation from 1.0 to flag, default 0.005 |
No output schema declared.
No examples provided.
token_security_check Token contract risk ~56
Honeypot, taxes, mintable, proxy, owner powers and holder concentration with a 0-100 risk score. $0.003 per call.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| chainId | string | yes | – |
No output schema declared.
No examples provided.
yieldprobe_info Service info (free) ~29
Free. Prices, payment network, HTTP endpoints and how to pay. Call this first if unsure.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the yieldprobe: DeFi intel for agents MCP server?
yieldprobe: DeFi intel for agents is an MCP server listed in the public MCP registry as com.yieldprobe/defi-intel. Paid DeFi data for agents via x402 on Base: yields, APY moves, stablecoin pegs, token risk. This page covers its hosted endpoint (https://yieldprobe.com/mcp).
Is the yieldprobe: DeFi intel for agents MCP server safe to use?
yieldprobe: DeFi intel for agents scores 66 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 yieldprobe: DeFi intel for agents MCP server expose?
yieldprobe: DeFi intel for agents exposes 5 tools: defi_top_yields, defi_yield_movers, stablecoin_peg_monitor, token_security_check, yieldprobe_info. Their descriptions and schemas cost roughly 446 tokens of context every time the server is loaded.
Does the yieldprobe: DeFi intel for agents MCP server require authentication?
No. We connected to yieldprobe: DeFi intel for agents without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the yieldprobe: DeFi intel for agents MCP server still maintained?
yieldprobe: DeFi intel for agents is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.