Easy Labs MCP Server
REMOTE · MCP.ITSEASY.CO · 3 COMPONENTS
Payments data, revenue workflows, and merchant-application guidance for AI agents, by Easy Labs.
Available components
Last scanned (2 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 429, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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, or could read only part of its tool list.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, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.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.
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.
- 30 Sept 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- HTTPS: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- 28 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
- 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
- 27 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “revenue_summary” rewrote its description, which is the text the model reads security
- Schema quality: 34 → 42 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Server version: 0.2.0 → 0.5.0 functional
- 26 Aug 26 0
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 5 Nov 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 | 24 Oct 2026 | 22 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 79ba9cc757c987dd0e76a2c440f12b0a |
| 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 Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| 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://mcp.itseasy.co/mcp | HTTP error | 503 | |
| http (plaintext) | http://mcp.itseasy.co/mcp | Inconclusive | 429 |
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.
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'
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 18 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?
Its publisher declares that Easy Labs MCP Server requires credentials, so you will need to authorise it in your MCP client. We have not been able to confirm that against the live endpoint.
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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.