# Easy Labs MCP Server (remote · mcp.itseasy.co)

Payments data, revenue workflows, and merchant-application guidance for AI agents, by Easy Labs.

- Trust score: 72/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `www.itseasy.co`: 80/100, [markdown](https://verifymcp.io/servers/co-itseasy-easy-mcp/api-mcp.md), [page](https://verifymcp.io/servers/co-itseasy-easy-mcp/api-mcp)
- remote · `mcp.itseasy.co`: 72/100 (this document), [markdown](https://verifymcp.io/servers/co-itseasy-easy-mcp/mcp.md), [page](https://verifymcp.io/servers/co-itseasy-easy-mcp/mcp)
- npm · `@easylabs/mcp-server`: 33/100, [markdown](https://verifymcp.io/servers/co-itseasy-easy-mcp/easylabs-mcp-server.md), [page](https://verifymcp.io/servers/co-itseasy-easy-mcp/easylabs-mcp-server)

## Channel facts

- Endpoint: `https://mcp.itseasy.co/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.5.0`

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

- **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 call this server, and 14 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - 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**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 765 tokens (~42/item across 18 items; 14 tools + 4 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 83/100
  - Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 70/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 10% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "get_transfer" implies "transfer" and declares readOnlyHint instead, contradicting what its own name says it does.
  - An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Easy Labs MCP Server server?

Easy Labs MCP Server is a hosted endpoint at https://mcp.itseasy.co/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 co-itseasy-easy-mcp 'https://mcp.itseasy.co/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "co-itseasy-easy-mcp": {
      "url": "https://mcp.itseasy.co/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "co-itseasy-easy-mcp": {
      "type": "http",
      "url": "https://mcp.itseasy.co/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.co-itseasy-easy-mcp]
url = "https://mcp.itseasy.co/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "co-itseasy-easy-mcp": {
      "type": "remote",
      "url": "https://mcp.itseasy.co/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add co-itseasy-easy-mcp --url 'https://mcp.itseasy.co/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  co-itseasy-easy-mcp:
    url: "https://mcp.itseasy.co/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "co-itseasy-easy-mcp": {
      "Transport": "http",
      "Url": "https://mcp.itseasy.co/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add co-itseasy-easy-mcp -t streamable-http -u 'https://mcp.itseasy.co/mcp'
```

### Other

```json
{
  "mcpServers": {
    "co-itseasy-easy-mcp": {
      "type": "http",
      "url": "https://mcp.itseasy.co/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-19 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 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 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 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 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 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 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 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 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

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

### 2026-09-06 (score 66, +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-04 (score 65, +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.

## MCP tools (14)

### `revenue_summary` (~80 tokens)

Revenue summary for a period (7d, 30d, 90d, 6m, 12m, or mtd): gross volume, transfer counts by status, average ticket, and change versus the previous equal-length period. Use this before reaching for list_transfers when the question is about overall performance.

Input parameters:

- `period` (string)

### `find_customer` (~63 tokens)

Find a customer by email or name (case-insensitive substring match) and show the best match's profile with recent payment activity. Use get_customer only when you already have a customer id.

Input parameters:

- `query` (string, required): Email address or (partial) name to search for

### `merchant_application_checklist` (~73 tokens)

Everything a business needs to gather before applying for an Easy merchant account — the 7 application steps with required information for each. Use this to prepare someone so the application takes ~10 minutes in one sitting. Do NOT collect SSN/EIN/bank details in conversation; the checklist explains where those are entered securely.

### `explain_application_step` (~83 tokens)

Explains one step of the Easy merchant application in plain English: what's asked, why it's required (KYB/underwriting context), and what to have ready. Steps 1-7: business details, business type, tax details, owners, merchant settings, processing volume, review & terms.

Input parameters:

- `step` (integer, required): Application step number (1-7)

### `list_transfers` (~37 tokens)

List recent transfers with optional filters.

Input parameters:

- `limit` (integer)
- `offset` (integer)
- `status` (string)

### `get_transfer` (~23 tokens)

Get a single transfer by ID.

Input parameters:

- `transfer_id` (string, required)

### `list_disputes` (~38 tokens)

List disputes with optional state filter.

Input parameters:

- `limit` (integer)
- `offset` (integer)
- `state` (string)

### `get_dispute` (~24 tokens)

Get a single dispute by ID.

Input parameters:

- `dispute_id` (string, required)

### `list_settlements` (~29 tokens)

List settlements with pagination.

Input parameters:

- `limit` (integer)
- `offset` (integer)

### `get_settlement` (~24 tokens)

Get a single settlement by ID.

Input parameters:

- `settlement_id` (string, required)

### `list_customers` (~28 tokens)

List customers with pagination.

Input parameters:

- `limit` (integer)
- `offset` (integer)

### `get_customer` (~22 tokens)

Get a customer by ID.

Input parameters:

- `customer_id` (string, required)

### `list_balance_transfers` (~28 tokens)

List balance transfers.

Input parameters:

- `limit` (integer)
- `offset` (integer)

### `get_balance_transfer` (~25 tokens)

Get a balance transfer by ID.

Input parameters:

- `balance_transfer_id` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/co-itseasy-easy-mcp/mcp#diagnostics

## Score history

- 2026-09-20: 72
- 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
- 2026-09-07: 66
- 2026-09-06: 66
- 2026-09-05: 65
- 2026-09-04: 65
- 2026-09-03: 64
- 2026-09-02: 64
- 2026-09-01: 63
- 2026-08-31: 63
- 2026-08-30: 62
- 2026-08-29: 62
- 2026-08-28: 61
- 2026-08-27: 61
- 2026-08-26: 60

## Common questions

### What is the Easy Labs MCP Server server?

Easy Labs MCP Server is listed in the public MCP registry as co.itseasy/easy-mcp. Payments data, revenue workflows, and merchant-application guidance for AI agents, by Easy Labs. This page covers its hosted endpoint (https://mcp.itseasy.co/mcp).

### Is the Easy Labs MCP Server server safe to use?

Easy Labs MCP Server scores 72 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 Easy Labs MCP Server server expose?

Easy Labs MCP Server exposes 14 tools: revenue_summary, find_customer, merchant_application_checklist, explain_application_step, list_transfers, and 9 more. Their descriptions and schemas cost roughly 577 tokens of context every time the server is loaded.

### Does the Easy Labs MCP Server server require authentication?

No. We connected to Easy Labs MCP Server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Easy Labs MCP Server server still maintained?

Easy Labs MCP Server 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.

## Links

- Remote endpoint: https://mcp.itseasy.co/mcp
- Authorisation metadata: https://mcp.itseasy.co/.well-known/oauth-protected-resource/mcp
- Website: https://docs.itseasy.co/docs/sdks/mcp
- Changelog RSS feed: https://verifymcp.io/servers/co-itseasy-easy-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/co-itseasy-easy-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/co-itseasy-easy-mcp/mcp