Server definition

Hash: sha256:21fdaf86105868e4c3f941dcb6cbad70c6ea67207c8e6fc238f4a037b22e1b47
What it is: What a remote MCP server returned when asked what it offers: 8 tools

The blob, as servednamed by its sha256

{
  "instructions": "Guest check-in and SES.HOSPEDAJES (police registration) compliance for the signed-in host's short-term rental properties. Tools return status/completeness only — never guest documents, email, phone, or passport/DNI numbers. Read tools need the partelisto:read grant; send_guest_checkin_link and create_booking additionally need partelisto:write, have a real side effect (an email sent, or a new booking), and should be confirmed with the host before calling them. Start with get_attention_required for a daily overview of what needs action.",
  "tools": [
    {
      "description": "Creates a new booking (a check-in workflow) for one of the host's properties. Requires the write permission granted separately during sign-in. Ask the host to confirm the property and dates before calling this. Does not email the guest — call send_guest_checkin_link afterwards if a link should go out now.",
      "inputSchema": {
        "properties": {
          "checkIn": {
            "description": "Check-in date, yyyy-MM-dd.",
            "type": "string"
          },
          "checkOut": {
            "description": "Check-out date, yyyy-MM-dd.",
            "type": "string"
          },
          "guestEmail": {
            "default": null,
            "description": "Guest email, optional.",
            "type": [
              "string",
              "null"
            ]
          },
          "guestName": {
            "default": null,
            "description": "Guest name, optional.",
            "type": [
              "string",
              "null"
            ]
          },
          "guestPhone": {
            "default": null,
            "description": "Guest phone, optional.",
            "type": [
              "string",
              "null"
            ]
          },
          "propertyId": {
            "description": "The property id, from list_properties.",
            "type": "string"
          },
          "templateId": {
            "default": null,
            "description": "Check-in template id. Omit if the property has exactly one active (non-archived) template — it is picked automatically; otherwise this is required.",
            "type": [
              "string",
              "null"
            ]
          }
        },
        "required": [
          "propertyId",
          "checkIn",
          "checkOut"
        ],
        "type": "object"
      },
      "name": "create_booking",
      "outputSchema": null
    },
    {
      "description": "Scans the signed-in host's most recent bookings (up to 50) and returns only what needs action right now: stays that are imminent or under way where the guest has not completed check-in, and bookings whose SES.HOSPEDAJES submission failed. Empty list means nothing needs attention within the window. No guest PII.",
      "inputSchema": {
        "properties": {
          "arrivalWindowDays": {
            "default": 3,
            "description": "How many days ahead counts as \"imminent\" (a negative gap means the stay already started). Defaults to 3.",
            "type": "integer"
          }
        },
        "type": "object"
      },
      "name": "get_attention_required",
      "outputSchema": null
    },
    {
      "description": "Whether the guest has completed the check-in form for a booking the host owns (None or Submitted). No form content.",
      "inputSchema": {
        "properties": {
          "bookingId": {
            "description": "The booking id.",
            "type": "string"
          }
        },
        "required": [
          "bookingId"
        ],
        "type": "object"
      },
      "name": "get_guest_form_status",
      "outputSchema": null
    },
    {
      "description": "The signed-in host's plan tier, trial status, and this month's usage against plan limits (properties, templates, bookings).",
      "inputSchema": {
        "properties": {},
        "type": "object"
      },
      "name": "get_usage_summary",
      "outputSchema": null
    },
    {
      "description": "Lists the signed-in host's bookings (newest first), paged. Returns id, property id, check-in/check-out dates, status, and whether a check-in link and guest contact exist — never the guest's email, phone, or documents.",
      "inputSchema": {
        "properties": {
          "skip": {
            "default": 0,
            "description": "Rows to skip, for paging. Defaults to 0.",
            "type": "integer"
          },
          "take": {
            "default": 20,
            "description": "Rows to return, max 50. Defaults to 20.",
            "type": "integer"
          }
        },
        "type": "object"
      },
      "name": "list_bookings",
      "outputSchema": null
    },
    {
      "description": "Lists the signed-in host's properties: id, name, address, municipality/province, and whether it is archived. No guest data.",
      "inputSchema": {
        "properties": {
          "includeArchived": {
            "default": false,
            "description": "Include archived properties. Defaults to false.",
            "type": "boolean"
          }
        },
        "type": "object"
      },
      "name": "list_properties",
      "outputSchema": null
    },
    {
      "description": "SES.HOSPEDAJES (police registration) submission status for a set of bookings the host owns: status, attempts, last error, and the official reference once accepted. Bookings with no submission yet are omitted.",
      "inputSchema": {
        "properties": {
          "bookingIds": {
            "description": "Booking ids to check, up to 50.",
            "items": {
              "type": "string"
            },
            "type": "array"
          }
        },
        "required": [
          "bookingIds"
        ],
        "type": "object"
      },
      "name": "list_ses_statuses",
      "outputSchema": null
    },
    {
      "description": "Sends (or resends) the guest check-in link by email for a booking the host owns. This is a real action with a side effect: it emails the guest and, on resend, invalidates the guest's previous link. Requires the write permission granted separately during sign-in. Ask the host to confirm before calling this.",
      "inputSchema": {
        "properties": {
          "bookingId": {
            "description": "The booking id.",
            "type": "string"
          },
          "email": {
            "default": null,
            "description": "Guest email to send to. Omit to use the email already on the booking.",
            "type": [
              "string",
              "null"
            ]
          },
          "guestName": {
            "default": null,
            "description": "Guest name, for the email greeting. Omit to keep the name already on the booking.",
            "type": [
              "string",
              "null"
            ]
          }
        },
        "required": [
          "bookingId"
        ],
        "type": "object"
      },
      "name": "send_guest_checkin_link",
      "outputSchema": null
    }
  ]
}

Verify it yourself

curl -s https://api.teppi.xyz/v1/evidence/sha256:21fdaf86105868e4c3f941dcb6cbad70c6ea67207c8e6fc238f4a037b22e1b47 | sha256sum