Easy Labs MCP Server
REMOTE · MCP.ITSEASY.CO · 3 COMPONENTS · SCANNED SEP 21
Payments data, revenue workflows, and merchant-application guidance for AI agents, by Easy Labs.
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 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. See how to fix → 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 765 tokens (~42/item across 18 items; 14 tools + 4 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage70
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 10% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 16 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 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.
remote · mcp.itseasy.co
claude mcp add --transport http co-itseasy-easy-mcp 'https://mcp.itseasy.co/mcp'
{
"mcpServers": {
"co-itseasy-easy-mcp": {
"url": "https://mcp.itseasy.co/mcp"
}
}
} {
"servers": {
"co-itseasy-easy-mcp": {
"type": "http",
"url": "https://mcp.itseasy.co/mcp"
}
}
} [mcp_servers.co-itseasy-easy-mcp] url = "https://mcp.itseasy.co/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"co-itseasy-easy-mcp": {
"type": "remote",
"url": "https://mcp.itseasy.co/mcp",
"enabled": true
}
}
} openclaw mcp add co-itseasy-easy-mcp --url 'https://mcp.itseasy.co/mcp' --transport streamable-http
mcp_servers:
co-itseasy-easy-mcp:
url: "https://mcp.itseasy.co/mcp" {
"McpServers": {
"co-itseasy-easy-mcp": {
"Transport": "http",
"Url": "https://mcp.itseasy.co/mcp"
}
}
} assistant mcp add co-itseasy-easy-mcp -t streamable-http -u 'https://mcp.itseasy.co/mcp'
{
"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.
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.
- 19 Sept 26 +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.
- 17 Sept 26 +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.
- 15 Sept 26 +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.
- 13 Sept 26 +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.
- 11 Sept 26 +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.
- 9 Sept 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.
- 6 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.
- 4 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.
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://mcp.itseasy.co/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.itseasy.co | CN=WE1,O=Google Trust Services,C=US | 26 Aug 2026 | 24 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 18b1a9083549ef5413b036977434e1cd |
| SANs: mcp.itseasy.co | ||||||
| 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 mcp.itseasy.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| itseasy.co. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.itseasy.co/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.itseasy.co/mcp | HTTPS enforced | 301 | https://mcp.itseasy.co/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 →
explain_application_step ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| step | integer | yes | Application step number (1-7) |
No output schema declared.
No examples provided.
find_customer ~63
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Email address or (partial) name to search for |
No output schema declared.
No examples provided.
get_balance_transfer ~25
Get a balance transfer by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| balance_transfer_id | string | yes | – |
No output schema declared.
No examples provided.
get_customer ~22
Get a customer by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | yes | – |
No output schema declared.
No examples provided.
get_dispute ~24
Get a single dispute by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| dispute_id | string | yes | – |
No output schema declared.
No examples provided.
get_settlement ~24
Get a single settlement by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| settlement_id | string | yes | – |
No output schema declared.
No examples provided.
get_transfer ~23
Get a single transfer by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| transfer_id | string | yes | – |
No output schema declared.
No examples provided.
list_balance_transfers ~28
List balance transfers.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
No output schema declared.
No examples provided.
list_customers ~28
List customers with pagination.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
No output schema declared.
No examples provided.
list_disputes ~38
List disputes with optional state filter.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
| state | string | – | – |
No output schema declared.
No examples provided.
list_settlements ~29
List settlements with pagination.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
No output schema declared.
No examples provided.
list_transfers ~37
List recent transfers with optional filters.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
| status | string | – | – |
No output schema declared.
No examples provided.
merchant_application_checklist ~73
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
revenue_summary ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| period | string | – | – |
No output schema declared.
No examples provided.
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.