com.peek/mcp
REMOTE · MCP.PEEK.COM · SCANNED OCT 4
Build travel itineraries with Peek's 300k+ experiences. Search, details, and availability.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the com.peek/mcp server?
com.peek/mcp is a hosted endpoint at https://mcp.peek.com/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.peek.com
claude mcp add --transport http com-peek-mcp 'https://mcp.peek.com/'
{
"mcpServers": {
"com-peek-mcp": {
"url": "https://mcp.peek.com/"
}
}
} {
"servers": {
"com-peek-mcp": {
"type": "http",
"url": "https://mcp.peek.com/"
}
}
} [mcp_servers.com-peek-mcp] url = "https://mcp.peek.com/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-peek-mcp": {
"type": "remote",
"url": "https://mcp.peek.com/",
"enabled": true
}
}
} openclaw mcp add com-peek-mcp --url 'https://mcp.peek.com/' --transport streamable-http
mcp_servers:
com-peek-mcp:
url: "https://mcp.peek.com/" {
"McpServers": {
"com-peek-mcp": {
"Transport": "http",
"Url": "https://mcp.peek.com/"
}
}
} assistant mcp add com-peek-mcp -t streamable-http -u 'https://mcp.peek.com/'
{
"mcpServers": {
"com-peek-mcp": {
"type": "http",
"url": "https://mcp.peek.com/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.37 → unverified ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Oct 2026 · Probed https://mcp.peek.com
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.peek.com | CN=YE2,O=Let's Encrypt,C=US | 16 Aug 2026 | 14 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 6ed3a5ba1f6dd5f3a0b22077382addb77ea |
| SANs: mcp.peek.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.peek.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| peek.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.peek.com | Verified | 200 | |
| http (plaintext) | http://mcp.peek.com | HTTPS enforced | 301 | https://mcp.peek.com/ |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
experience_availability ~112
Get availability information for a specific experience including dates, times, and pricing
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | yes | End date inclusive in YYYY-MM-DD format (e.g., '2025-06-20' would return things taking place ON or BEFORE the 20th) |
| id | string | yes | The ID of the experience |
| quantity | integer | yes | Number of travelers |
| startDate | string | yes | Start date inclusive YYYY-MM-DD format (e.g., '2025-06-19') |
No output schema declared.
No examples provided.
experience_details ~32
Get detailed information about a specific experience by ID
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The ID of the experience to retrieve |
No output schema declared.
No examples provided.
list_tags ~13
List all category tags
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
render_activity_tiles ~46
Render activity tiles for a list of activity IDs, returning an embeddable widget URI
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | ID or comma separate list of activity IDs to render as tiles |
No output schema declared.
No examples provided.
search_experiences ~324
Search for travel experiences with comprehensive filtering options. Returns available categories, tags, and regions with IDs for further filtering.
| Name | Type | Req | Description |
|---|---|---|---|
| categoryId | string | – | Limit to only a specific activity category |
| endDate | string | – | 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) |
| latLng | string | – | 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 us… |
| query | string | – | 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. |
| regionId | string | – | When you have determined the user wants something in a specific region (found w/ search_regions) limit to only a specific region ID |
| startDate | string | – | Return experiences that are available on or after this date. YYYY-MM-DD format (e.g., '2025-06-19') |
| tagId | string | – | 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) |
No output schema declared.
No examples provided.
search_regions ~46
Search for regions by name
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of regions to return (default: 50) |
| query | string | yes | Search query to match against region names |
No output schema declared.
No examples provided.
What is the com.peek/mcp server?
com.peek/mcp is listed in the public MCP registry as com.peek/mcp. Build travel itineraries with Peek's 300k+ experiences. Search, details, and availability. This page covers its hosted endpoint (https://mcp.peek.com).
Is the com.peek/mcp server safe to use?
com.peek/mcp scores 33 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.peek/mcp server expose?
com.peek/mcp exposes 6 tools: experience_availability, experience_details, list_tags, render_activity_tiles, search_experiences, search_regions. Their descriptions and schemas cost roughly 573 tokens of context every time the server is loaded.
Does the com.peek/mcp server require authentication?
No. We connected to com.peek/mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.peek/mcp server still maintained?
com.peek/mcp is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.