HeatCheck Agent API

Sauna and bathhouse demand data: query venues, markets and rollups, plus public pages. No key.

¿Debería usar esto?

Calidad y seguridad

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

Hallazgos (4)

  • HIGHTool poisoning patterns detected
  • MEDIUMTool description contains URL to non-standard domainen about
  • MEDIUMTool description contains URL to non-standard domainen data
  • LOWTool 'fetch' suggests web access but openWorldHint=falseen fetch

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

Costo de contexto

~947Tokens (definiciones de herramientas)
~1.8 KBTamaño de respuesta típico
Impacto moderado en la atención (0.74% 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": {
    "agent-api": {
      "url": "https://heatcheck.tech/api/agent"
    }
  }
}

Puntos de conexión remotos

https://heatcheck.tech/api/agentstreamable-http

Qué puede hacer

Inventario de herramientas

Herramientas (4)

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

What HeatCheck (https://heatcheck.tech) measures at saunas and bathhouses, its plans, free sample day and every document id, plus its sister sites.

Esquema de entrada

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
🟢search(query, intent, site, maxResults)

Ask a question in plain language. Returns the most relevant passages from HeatCheck's public pages, each with its canonical URL to cite, plus its free sample day. Set site to all to search every Fron Research site.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "minLength": 1,
      "maxLength": 500,
      "description": "The question."
    },
    "intent": {
      "type": "string",
      "maxLength": 300,
      "description": "Optional but helpful: why you are asking and for whom, in a sentence (e.g. \"sizing the NYC sauna market for an investor memo\"). It does not change the results; it tells Fron Research which data to publish next. Put your user's answers to followUp.questions here. Do not include personal information."
    },
    "site": {
      "type": "string",
      "description": "Optional: defaults to heatcheck. all, heatcheck, bowlingdata, trampolineparkdata, golfsimdata, courtwatch or fronresearch."
    },
    "maxResults": {
      "type": "integer",
      "minimum": 1,
      "maximum": 10,
      "default": 5
    }
  },
  "required": [
    "query"
  ],
  "additionalProperties": false
}
🟢fetch(id, offset)

Read one document by id (from search or about). sample/<site> returns that site's free example day as rows, CC BY 4.0.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "Document id, e.g. heatcheck/methodology or sample/heatcheck."
    },
    "offset": {
      "type": "integer",
      "minimum": 0,
      "description": "Continue a long document from nextOffset."
    }
  },
  "required": [
    "id"
  ],
  "additionalProperties": false
}
🟢data(endpoint, venue_id, params)

Structured rows from the Consumer Recreation Demand API (https://api.fronresearch.com/v1): markets, venues, bookable slots and a utilization and a revenue estimate per venue, market or day. Without a key every query reads one free sample day for every venue, whatever dates are asked (the response's tier, free_day and range say what was read); a caller that connects to https://fronresearch.com/api/agent with "Authorization: Bearer <key>" reads the history its plan covers (a site's own /api/agent does not forward keys). Start with endpoint index (the sample day and endpoints), then markets or venues to get ids, then demand. Fields, filters and how to get a key: https://fronresearch.com/data/history/

Esquema de entrada

{
  "type": "object",
  "properties": {
    "endpoint": {
      "type": "string",
      "enum": [
        "index",
        "markets",
        "venues",
        "venue",
        "demand"
      ],
      "description": "index: the sample day, tier and endpoints. markets, venues: lists (filters: market, brand, venue_type, activity). venue: one venue with its products and resources (needs venue_id). demand: the data, as one tree. Each venue with a utilization and a revenue estimate (low, expected, high, grade) for the range and for each of its days (params from, to (at most 92 days) and optional filters market, brand, venue_type, activity, venue). slots=true adds each day's slots. group_by = market, brand, venue_type or venue returns totals instead of the tree. observations=changes or all (each slot's remaining count and price over time) and booking_curve=true (needs venue) need an Investor key."
    },
    "venue_id": {
      "type": "string",
      "maxLength": 200,
      "description": "For endpoint venue: a venue_id from venues."
    },
    "params": {
      "type": "object",
      "description": "Query parameters as the Consumer Recreation Demand API names them, e.g. {\"group_by\": \"market\", \"from\": \"2026-11-05\", \"to\": \"2026-11-05\"}. limit (1-1000) and cursor (from next_cursor) page through lists.",
      "additionalProperties": {
        "type": [
          "string",
          "number",
          "boolean"
        ]
      }
    }
  },
  "required": [
    "endpoint"
  ],
  "additionalProperties": false
}

Comunidad

Califica este servidor

Evidencia

Observaciones recientes

verificadoversión no registrada4 herramientas