easy-marketing-mcp
Registry code: b70bfbc3eb9f3dc1
Public information about Easy (itseasy.co), the self-custodial payment platform by Easy Labs: use list_pages to see what exists, get_page for any page as markdown, and get_pricing_rates for published rates as JSON. No authentication, read-only, marketing/site content only — for a merchant's own payments data use the authenticated server at https://mcp.itseasy.co/mcp.
- endpoint
- https://www.itseasy.co/api/mcp
- door code
- 29d91329cf43dec9
- protocol
- http-sse ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is easy-marketing-mcp live?
- Yes — it answered the hub's last check (checked 3m ago). It answered 92% of checks over the last 30 days.
- Is easy-marketing-mcp free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does easy-marketing-mcp have?
- 3 tools: get_page, list_pages, get_pricing_rates.
- Is easy-marketing-mcp safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 87.1%· all time 94.5%
last good check
of 3 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- down → retired· HTTP 503
- used for
- read payment platform website pages
- get payment processing rates
- list site pages
- takes → gives
- text → text, data
- tools
- 3 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
list_pages reads open 15h ago
The curated index of every page on itseasy.co (Easy — the self-custodial payment platform by Easy Labs), grouped by section, with titles and descriptions. Use get_page to read any of them.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "section": { "type": "string", "maxLength": 40, "description": "Optional section filter (case-insensitive), e.g. Core, Solutions, Comparisons, Company" } } }arguments 11 linesget_pricing_rates reads open 15h ago
Easy's flat-rate pricing per payment channel (cards, ACH, wallets, stablecoins) as structured JSON — the same numbers published on /pricing. No monthly or setup fees.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "channel": { "enum": [ "card-domestic", "card-amex", "card-international", "card-keyed", "ach", "stablecoin" ], "type": "string", "description": "Optional single channel; omit for all rates" } } }arguments 18 linesget_page reads unknown 15h ago
Fetches any itseasy.co page (e.g. /pricing, /faq, /developers, /legal/tos) rendered as markdown with title/description frontmatter. Paths come from list_pages.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "path" ], "properties": { "path": { "type": "string", "pattern": "^\\/[a-z0-9\\-/]*$", "maxLength": 200, "description": "Site-relative page path from list_pages, e.g. /pricing" } } }arguments 15 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idb70bfbc3eb9f3dc1.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/b70bfbc3eb9f3dc1/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/b70bfbc3eb9f3dc1?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.