INDIVIDUAL MCP TOOL

license_activate

Turn Pro on for this connection with key, an MCPL1.

zovo.onenone authenticationAvailability not checked

LIVE ENDPOINT

https://mcp.zovo.one/mcp/dunning-letters

No auth detected

Connect to this endpoint to inspect the live schema for license_activate and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

zovo.one

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.mcp-dunning-letters]
url = "https://mcp.zovo.one/mcp/dunning-letters"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "mcp-dunning-letters": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/dunning-letters"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: mcp-dunning-letters
Remote MCP URL: https://mcp.zovo.one/mcp/dunning-letters

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "mcp-dunning-letters": {
      "url": "https://mcp.zovo.one/mcp/dunning-letters"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "mcp-dunning-letters": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/dunning-letters"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "mcp-dunning-letters",
  "transport": "streamable-http",
  "url": "https://mcp.zovo.one/mcp/dunning-letters"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

invoice_register — Start chasing an unpaid invoice: register the client, the invoice reference, the amount in integer cents, the currency and the due date, and get the three-letter escalation schedule (reminder 1, reminder 2, final notice) with the date each falls due.
payment_record — Record money received against a chased invoice, in whole MINOR units: a part payment lowers what is still chased, a payment that covers the balance closes the ladder and frees the free-tier slot.
letter_render — Chase an unpaid invoice: generate the letter for the current stage of the ladder -- reminder 1 (polite), reminder 2 (firm, with the late fees note) or the final notice (before-action wording) -- as Markdown or as self-contained printable HTML.
letter_sent — Record that a chase letter was actually sent, with its date, so the ladder advances to the next stage.
overdue_list — Every unpaid invoice past its due date: how many days late, what is still owed, which letters have gone out, and what is due next and when.
aging_summary — The aging summary across every unpaid invoice: current, 1-30, 31-60, 61-90 and 91+ day buckets, with counts and totals in integer cents, per currency.
chase_today — The day's chase list: which invoices cross an escalation threshold today, which letter to send each and how long it has been waiting, what falls due in the next few days, and which invoices have had all three letters and need a decision outside this server.
invoice_status — One chased invoice in full: what was billed, what has been paid and what is still owed, every letter sent with its date, the escalation schedule with each stage's state, and what happens next and when.