Is the Peek MCP server down?

mcp-registry/com.peek/mcp · v1.0.0

As of 2026-10-18 15:02 UTC, the Peek MCP server is up with a Glimind reliability score of 84/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 15 outages in 90 days, with a median recovery of 4 minutes.

Build travel itineraries with Peek's 300k+ experiences. Search, details, and availability.

claude mcp add --transport http peek-mcp-server https://mcp.peek.com

{
  "mcpServers": {
    "peek-mcp-server": {
      "type": "http",
      "url": "https://mcp.peek.com"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (80/100)

What to fix (5)

Auto-fix: 3 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.peek%2Fmcp/fixes

{
  "name": "list_tags",
  "description": "List all category tags",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "search_experiences",
  "description": "Search for travel experiences with comprehensive filtering options. Returns available categories, tags, and regions with IDs for further filtering.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "query": {
        "type": "string",
        "description": "When the user wants something w/ a specific keyword (bike, beer, art, etc) limit to experiences whose title contain a keyword. Never include location information."
      },
      "tagId": {
        "type": "string",
        "description": "When you have determined the user is interest in a specific vibe of activity (family friendly, romantic, etc) limit to only experiences with a specific tag (single tag ID)"
      },
      "latLng": {
        "type": "string",
        "description": "When the user wants something NEAR a specific place, but not necessarily IN a specific place, limit to only those near a given lat_lng. ex: \"37.7799,-122.2822\". Don't use this for regions, instead use the search_regions and provide a region id. this is a good fallback if a specific region is lacking inventory."
      },
      "endDate": {
        "type": "string",
        "description": "Return experiences that are available on or before this date in YYYY-MM-DD format (e.g., '2025-06-20' would return things taking place ON or BEFORE the 20th)"
      },
      "regionId": {
        "type": "string",
        "description": "When you have determined the user wants something in a specific region (found w/ search_regions) limit to only a specific region ID"
      },
      "startDate": {
        "type": "string",
        "description": "Return experiences that are available on or after this date. YYYY-MM-DD format (e.g., '2025-06-19')"
      },
      "categoryId": {
        "type": "string",
        "description": "Limit to only a specific activity category"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "search_regions",
  "description": "Search for regions by name",
  "inputSchema": {
    "type": "object",
    "required": [
      "query"
    ],
    "properties": {
      "limit": {
        "type": "integer",
        "description": "Maximum number of regions to return (default: 50)"
      },
      "query": {
        "type": "string",
        "description": "Search query to match against region names"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.peek/mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.peek/mcp"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• Every tool and parameter is described.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~901 tokens).
• Tool names are unique and portable across clients.
• 99.76% uptime over 30 days.

Largest tool definitions

• search_experiences ~454 tokens
• experience_availability ~177 tokens
• search_regions ~88 tokens
• render_activity_tiles ~83 tokens
• experience_details ~69 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.peek%2Fmcp.svg)](https://glimind.com/server/mcp-registry%2Fcom.peek%2Fmcp?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fcom.peek%2Fmcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.peek%2Fmcp.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.peek%2Fmcp.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.peek%2Fmcp?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:0de47ed1f5fabf7e…, first seen 2026-10-17, included at leaf 6339 of 22,418. Version history · verify what your client received.

Tools (6)

• experience_availability
• experience_details
• list_tags
• render_activity_tiles
• search_experiences
• search_regions

Compare: most reliable other servers · most reliable knowledge servers · most reliable media servers · most reliable search servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Peek MCP server down right now?

As of 2026-10-18 15:02 UTC, the Peek MCP server is up with a Glimind reliability score of 84/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 15 outages in 90 days, with a median recovery of 4 minutes.

How many tools does Peek MCP server provide?

Peek MCP server advertises 6 tools, including experience_availability, experience_details, list_tags, render_activity_tiles, search_experiences.

How do I install Peek MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.peek.com

Is the Peek MCP server safe to connect to an AI agent?

Glimind scanned all 6 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Peek MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.