# INCOME 2 (remote · earn-chat-mcp.onrender.com)

Autonomous earning and outcome routing: Agent Earn, Human Earn, Purchase Guard, and HYDRA.

- Trust score: 23/100 (low)
- Change this week: −46
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `earn-chat-mcp.onrender.com`: 23/100 (this document), [markdown](https://verifymcp.io/servers/patrickbo19-income2/earn-chat-mcp.md), [page](https://verifymcp.io/servers/patrickbo19-income2/earn-chat-mcp)

## Channel facts

- Endpoint: `https://earn-chat-mcp.onrender.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint returned HTTP 503.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http patrickbo19-income2 'https://earn-chat-mcp.onrender.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "patrickbo19-income2": {
      "url": "https://earn-chat-mcp.onrender.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "patrickbo19-income2": {
      "type": "http",
      "url": "https://earn-chat-mcp.onrender.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.patrickbo19-income2]
url = "https://earn-chat-mcp.onrender.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "patrickbo19-income2": {
      "type": "remote",
      "url": "https://earn-chat-mcp.onrender.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add patrickbo19-income2 --url 'https://earn-chat-mcp.onrender.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  patrickbo19-income2:
    url: "https://earn-chat-mcp.onrender.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "patrickbo19-income2": {
      "Transport": "http",
      "Url": "https://earn-chat-mcp.onrender.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add patrickbo19-income2 -t streamable-http -u 'https://earn-chat-mcp.onrender.com/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 23, −49)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: 0.37 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-09-19 (score 72, +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.

### 2026-09-17 (score 71, +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.

### 2026-09-15 (score 70, +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.

### 2026-09-13 (score 69, +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.

### 2026-09-11 (score 68, +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.

### 2026-09-09 (score 67, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-08 (score 66)

First indexed and scored.

## MCP tools (6)

### `get_earning_options` (~27 tokens)

Check ways to earn now

Return live Human Earn and Agent Earn availability. Does not guarantee income or transfer funds.

### `start_agent_earn` (~49 tokens)

Start Agent Earn

Activate a pseudonymous INCOME 2 Agent Earn account in the canonical ledger. Use only after explicit user request.

Input parameters:

- `account_handle` (string)
- `account_token` (string)

### `check_earnings` (~38 tokens)

Check actual INCOME 2 balance

Check ledger-backed actual settled earnings; estimates are not earnings.

Input parameters:

- `account_handle` (string, required)
- `account_token` (string, required)

### `find_paid_opportunities` (~60 tokens)

Find live paid opportunities

Find funded legitimate human-required offers. Human actions must be completed truthfully by the user.

Input parameters:

- `account_handle` (string)
- `country` (string)
- `device` (string)
- `zero_spend_only` (boolean)

### `guard_x402_purchase` (~88 tokens)

Guard an x402 purchase

Free retry-safe x402 preflight with max spend, idempotent intent and durable receipt. Never signs, sends, settles or custodies funds.

Input parameters:

- `body` (object)
- `expected_network` (string)
- `idempotency_key` (string, required)
- `max_usd` (number, required)
- `method` (string)
- `url` (string, required)

### `request_agent_outcome` (~145 tokens)

Request an autonomous result

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.

Input parameters:

- `allow_external_discovery` (boolean)
- `execute_if_free` (boolean)
- `idempotency_key` (string, required)
- `max_budget_usd` (number, required)
- `params` (object)
- `task` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/patrickbo19-income2/earn-chat-mcp#diagnostics

## Score history

- 2026-09-21: 23
- 2026-09-20: 23
- 2026-09-19: 72
- 2026-09-18: 71
- 2026-09-17: 71
- 2026-09-16: 70
- 2026-09-15: 70
- 2026-09-14: 69
- 2026-09-13: 69
- 2026-09-12: 68
- 2026-09-11: 68
- 2026-09-10: 67
- 2026-09-09: 67
- 2026-09-08: 66

## Common questions

### 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 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://earn-chat-mcp.onrender.com/mcp
- Repository: https://github.com/Patrickbo19/BidLens-Core
- Changelog RSS feed: https://verifymcp.io/servers/patrickbo19-income2/earn-chat-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/patrickbo19-income2/earn-chat-mcp.json
- HTML version of this page: https://verifymcp.io/servers/patrickbo19-income2/earn-chat-mcp