Last check · No semantic contract change since the previous complete snapshot.
Info
This public timeline shows the latest check, the last 24 hours, and the most recent important change. Watch keeps 30 days.
The notes above are for this connector.
Server-provided content. Tool names, descriptions and schemas below are copied from the MCP server. They may be in another language. Talandor does not translate or verify them.
Tools and declared exposure
Server annotations are declarations, not verified behavior.
Show 14 of 14 server-provided tool definitions
explain_application_step
Declared read-onlyShow server-provided detailsServer description (copied; language not verified)
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 schema (server-provided preview — do not copy)
Declared read-onlyShow server-provided detailsServer description (copied; language not verified)
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 schema (server-provided preview — do not copy)
Declared read-onlyShow server-provided detailsServer description (copied; language not verified)
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 (server-provided preview — do not copy)
Declared read-onlyShow server-provided detailsServer description (copied; language not verified)
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 schema (server-provided preview — do not copy)
Your agent depends on this MCP. When Watch is active, periodic checks alert you when we observe a change that may affect the client you selected.
Know when it goes downWhen Watch is active, availability is observed about every 5 minutes. An outage is confirmed after two failed checks, so a single miss is not treated as a lasting outage.
Know when its contract changesDeep checks about every hour compare public tool catalogs and authentication surfaces over time.
Know what changed and what to fixAn alert names the observed change and the next step for the client you selected.
Full public-contract coverage: Availability, protocol, auth and public tool contract changes can be compared.
Full WatchAvailability, protocol, auth and public tool contract changes
Surface WatchAvailability, TLS, protocol and auth surface — no private tool diff
Early access currently activates this first endpoint; adding more endpoints up to the planned limit of five is not open in this deployment. Live checkout is open. A Watch activates only after a verified payment event; a browser return never starts monitoring.