site

AI vs Hire: the site's own MCP server — calculator, enquiry (enquiry = a human handoff, not a...

¿Debería usar esto?

Calidad y seguridad

B
Calidad de la descripción
100%
Integridad del esquema
56%
Calidad de los nombres
88%
Riesgo de envenenamiento
100%
Coincidencia de permisos
100%
Cumplimiento del protocolo
100%

Basado en el análisis automatizado de las definiciones de herramientas y el cumplimiento del protocolo.

Costo de contexto

~844Tokens (definiciones de herramientas)
~1.1 KBTamaño de respuesta típico
Impacto moderado en la atención (0.66% del contexto de 128k)

Este es el número aproximado de tokens que se consumen cada vez que las herramientas del servidor se cargan en el contexto de un modelo. Los recuentos más altos reducen la atención disponible para otras tareas.

Instalar

Instalación con un clic

Agrega esto a tu archivo `claude_desktop_config.json`:

{
  "mcpServers": {
    "site": {
      "url": "https://aivshire.com/mcp"
    }
  }
}

Puntos de conexión remotos

https://aivshire.com/mcpstreamable-http

Qué puede hacer

Inventario de herramientas

Herramientas (5)

🟢 Solo lectura🟡 Escritura🔴 Eliminación⚪ Desconocido
🟢calculator_describe

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

Esquema de entrada

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢calculate(salary, onCostPct, equip, recruit, mgmtHrs, ...)

Run the AI against a hire, on the same basis calculator: Full cost of the hire, per year; Hire cost as a multiple of salary; Full cost of the AI route, year one; Full cost of the AI route, year two onward. Missing inputs fall back to their documented defaults.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "salary": {
      "type": "number",
      "description": "Salary for the role",
      "default": 55000
    },
    "onCostPct": {
      "type": "number",
      "description": "Employer costs as a percentage of salary",
      "default": 25
    },
    "equip": {
      "type": "number",
      "description": "Equipment, software and workspace per year",
      "default": 4000
    },
    "recruit": {
      "type": "number",
      "description": "Recruitment cost, spread over expected tenure",
      "default": 4000
    },
    "mgmtHrs": {
      "type": "number",
      "description": "Management hours a week",
      "default": 3
    },
    "mgmtRate": {
      "type": "number",
      "description": "Manager cost per hour",
      "default": 75
    },
    "aiLicence": {
      "type": "number",
      "description": "AI tool annual licence",
      "default": 12000
    },
    "aiSetup": {
      "type": "number",
      "description": "Data and integration, year one",
      "default": 25000
    },
    "superHrs": {
      "type": "number",
      "description": "Hours a week supervising and checking output",
      "default": 5
    },
    "superRate": {
      "type": "number",
      "description": "Cost per hour of whoever checks it",
      "default": 45
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟡enquiry_describe

Read first. States plainly what submit_enquiry does on AI vs Hire: 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.

Esquema de entrada

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

Every field of the AI vs Hire 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.

Esquema de entrada

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

Submits an enquiry to AI vs Hire — 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 automation partners or recruiters, who'll contact me directly."

Esquema de entrada

{
  "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 automation partners or recruiters, 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#"
}

Comunidad

Califica este servidor

Evidencia

Observaciones recientes

verificadoversión no registrada5 herramientas
verificadoversión no registrada5 herramientas