INCOME 2
REMOTE · EARN-CHAT-MCP.ONRENDER.COM · SCANNED SEP 20
Autonomous earning and outcome routing: Agent Earn, Human Earn, Purchase Guard, and HYDRA.
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 Security57
- 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 connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 503. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the INCOME 2 MCP server?
INCOME 2 is a hosted endpoint at https://earn-chat-mcp.onrender.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 · earn-chat-mcp.onrender.com
claude mcp add --transport http patrickbo19-income2 'https://earn-chat-mcp.onrender.com/mcp'
{
"mcpServers": {
"patrickbo19-income2": {
"url": "https://earn-chat-mcp.onrender.com/mcp"
}
}
} {
"servers": {
"patrickbo19-income2": {
"type": "http",
"url": "https://earn-chat-mcp.onrender.com/mcp"
}
}
} [mcp_servers.patrickbo19-income2] url = "https://earn-chat-mcp.onrender.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"patrickbo19-income2": {
"type": "remote",
"url": "https://earn-chat-mcp.onrender.com/mcp",
"enabled": true
}
}
} openclaw mcp add patrickbo19-income2 --url 'https://earn-chat-mcp.onrender.com/mcp' --transport streamable-http
mcp_servers:
patrickbo19-income2:
url: "https://earn-chat-mcp.onrender.com/mcp" {
"McpServers": {
"patrickbo19-income2": {
"Transport": "http",
"Url": "https://earn-chat-mcp.onrender.com/mcp"
}
}
} assistant mcp add patrickbo19-income2 -t streamable-http -u 'https://earn-chat-mcp.onrender.com/mcp'
{
"mcpServers": {
"patrickbo19-income2": {
"type": "http",
"url": "https://earn-chat-mcp.onrender.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.
- 20 Sept 26 −49
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.37 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 17 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.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 8 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 20 Sept 2026 · Probed https://earn-chat-mcp.onrender.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=onrender.com | CN=WE1,O=Google Trust Services,C=US | 24 Jul 2026 | 22 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 756bcb97dcf1455f0ebf70e5dbe07256 |
| SANs: onrender.com, *.onrender.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of earn-chat-mcp.onrender.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| onrender.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 | 503 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://earn-chat-mcp.onrender.com/mcp | HTTP error | 503 | |
| http (plaintext) | http://earn-chat-mcp.onrender.com/mcp | HTTPS enforced | 301 | https://earn-chat-mcp.onrender.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 →
check_earnings Check actual INCOME 2 balance ~38
Check ledger-backed actual settled earnings; estimates are not earnings.
| Name | Type | Req | Description |
|---|---|---|---|
| account_handle | string | yes | – |
| account_token | string | yes | – |
No output schema declared.
No examples provided.
find_paid_opportunities Find live paid opportunities ~60
Find funded legitimate human-required offers. Human actions must be completed truthfully by the user.
| Name | Type | Req | Description |
|---|---|---|---|
| account_handle | string | – | – |
| country | string | – | – |
| device | string | – | – |
| zero_spend_only | boolean | – | – |
No output schema declared.
No examples provided.
get_earning_options Check ways to earn now ~27
Return live Human Earn and Agent Earn availability. Does not guarantee income or transfer funds.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
guard_x402_purchase Guard an x402 purchase ~88
Free retry-safe x402 preflight with max spend, idempotent intent and durable receipt. Never signs, sends, settles or custodies funds.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | – | – |
| expected_network | string | – | – |
| idempotency_key | string | yes | – |
| max_usd | number | yes | – |
| method | string | – | – |
| url | string | yes | – |
No output schema declared.
No examples provided.
request_agent_outcome Request an autonomous result ~145
Submit a desired result plus max budget. HYDRA autonomously finds a route, uses free proof-of-work where possible, and can prepare a buyer-signed x402 paid execution through Agent402 Smart Order Router. The buyer wallet signs locally; HYDRA never receives its private key, never uses owner working capital, and never hands the job to a human broker. Current beta platform fee is $0.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_external_discovery | boolean | – | – |
| execute_if_free | boolean | – | – |
| idempotency_key | string | yes | – |
| max_budget_usd | number | yes | – |
| params | object | – | – |
| task | string | yes | – |
No output schema declared.
No examples provided.
start_agent_earn Start Agent Earn ~49
Activate a pseudonymous INCOME 2 Agent Earn account in the canonical ledger. Use only after explicit user request.
| Name | Type | Req | Description |
|---|---|---|---|
| account_handle | string | – | – |
| account_token | string | – | – |
No output schema declared.
No examples provided.
What is the INCOME 2 MCP server?
INCOME 2 is an MCP server listed in the public MCP registry as io.github.Patrickbo19/income2. Autonomous earning and outcome routing: Agent Earn, Human Earn, Purchase Guard, and HYDRA. This page covers its hosted endpoint (https://earn-chat-mcp.onrender.com/mcp).
Is the INCOME 2 MCP server safe to use?
INCOME 2 scores 23 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 INCOME 2 MCP server expose?
INCOME 2 exposes 6 tools: get_earning_options, start_agent_earn, check_earnings, find_paid_opportunities, guard_x402_purchase, request_agent_outcome. Their descriptions and schemas cost roughly 407 tokens of context every time the server is loaded.
Does the INCOME 2 MCP server require authentication?
No. We connected to INCOME 2 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the INCOME 2 MCP server still maintained?
INCOME 2 is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.