site

Payroll Dates: the site's own MCP server — calculator, enquiry (enquiry = a human handoff, not a...

Sollte ich dies verwenden

Qualität und Sicherheit

B
Qualität der Beschreibung
100%
Vollständigkeit des Schemas
56%
Qualität der Benennung
88%
Risiko der Vergiftung
100%
Übereinstimmung der Berechtigungen
100%
Einhaltung des Protokolls
100%

Basierend auf einer automatisierten Analyse der Tool-Definitionen und der Einhaltung des Protokolls.

Kontextkosten

~735Tokens (Tool-Definitionen)
~812 BTypische Antwortgröße
Mittlere Auswirkung auf die Aufmerksamkeit (0.57% von 128k Kontext)

Dies ist die ungefähre Anzahl der Tokens, die jedes Mal verbraucht werden, wenn die Tools des Servers in den Kontext eines Modells geladen werden. Höhere Werte verringern die Aufmerksamkeit, die für andere Aufgaben verfügbar ist.

Installieren

Installation mit einem Klick

Fügen Sie dies Ihrer Datei `claude_desktop_config.json` hinzu:

{
  "mcpServers": {
    "site": {
      "url": "https://payrolldates.co.uk/mcp"
    }
  }
}

Remote-Endpunkte

https://payrolldates.co.uk/mcpstreamable-http

Was es kann

Tool-Inventar

Tools (5)

🟢 Nur lesen🟡 Schreiben🔴 Löschen⚪ Unbekannt
🟢calculator_describe

The inputs this calculator takes (with units, ranges and defaults), the outputs it returns, and the assumptions and tables behind it.

Eingabe-Schema

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟡calculate(payMonth, payDay, payMethod)

Run the PAYE deadline calculator, 2026/27 calculator: Pay HMRC by; Send your Full Payment Submission (FPS); Tax month this payday falls in; Employer Payment Summary (EPS) deadline. Missing inputs fall back to their documented defaults.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "payMonth": {
      "type": "string",
      "enum": [
        "apr26",
        "may26",
        "jun26",
        "jul26",
        "aug26",
        "sep26",
        "oct26",
        "nov26",
        "dec26",
        "jan27",
        "feb27",
        "mar27"
      ],
      "description": "Month you pay your staff",
      "default": "aug26"
    },
    "payDay": {
      "type": "number",
      "minimum": 1,
      "maximum": 31,
      "description": "Day of the month you pay them",
      "default": 25
    },
    "payMethod": {
      "type": "string",
      "description": "How you pay HMRC",
      "default": "0"
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟡enquiry_describe

Read first. States plainly what submit_enquiry does on Payroll Dates: it starts an enquiry with human providers who quote directly. Nothing is bought, ordered or paid; no quote is guaranteed; it is free. Also returns who receives the details, the consent wording, and how the person confirms.

Eingabe-Schema

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟡enquiry_fields

Every field of the Payroll Dates enquiry: key, label, type, whether required, help text and the allowed options where there are any. Pass answers to submit_enquiry keyed by field key.

Eingabe-Schema

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟡submit_enquiry(answers, consent, confirmation)

Submits an enquiry to Payroll Dates — NOT a purchase, NOT a guaranteed quote. Step 1: call with the answers (keyed by field key from enquiry_fields) and consent=true; it validates and returns a summary, the consent line and a confirmation token — show the person the summary and the consent line. Step 2: only if the person agrees, call again with the same answers, consent=true and the confirmation token; the enquiry is then submitted, and the person receives an email with a link they must click before any provider sees it. Consent means the person has read and agreed to: "Happy for my details to go to a relevant payroll bureau or accountant, who'll contact me directly."

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "answers": {
      "type": "object",
      "additionalProperties": {
        "type": [
          "string",
          "number",
          "boolean"
        ]
      },
      "description": "the person's answers, keyed by field key"
    },
    "consent": {
      "type": "boolean",
      "description": "true only when the person has agreed to: Happy for my details to go to a relevant payroll bureau or accountant, who'll contact me directly."
    },
    "confirmation": {
      "type": "string",
      "description": "the confirmation token from step 1, after the person has approved the summary"
    }
  },
  "required": [
    "answers",
    "consent"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Community

Diesen Server bewerten

Nachweis

Aktuelle Beobachtungen

verifiziertVersion nicht aufgezeichnet5 Tools
verifiziertVersion nicht aufgezeichnet5 Tools