Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.greetwell/mcp

REMOTE · MCP.GREETWELL.COM

Discover and book 5,000+ curated local experiences across 500 US destinations.

0 this week 76 Trust /100

Last scanned (22 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Entertainment and Games

Trust breakdown (7 categories)

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 Security60
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 390 tokens (~97/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Registry listing versus package

Where what the registry lists and what we observed about the package disagree. This is read from the stored diagnostics and is never an input to the score.

  • Endpoint address

    Registry says
    https://mcp.greetwell.com/mcp
    Package shows
    https://mcp.greetwell.com/mcp/

    The registry's URL redirects here, so the authorisation and transport results describe this address rather than the one listed. See the evidence →

Changelog

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.

  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 7 Nov 26 0
    • Endpoint reachability: unreachable → reachable ▲ functional
  • 6 Nov 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
  • 5 Nov 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • HSTS header: fail → unverified ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 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
Diagnostics

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 21 Nov 2026 · Probed https://mcp.greetwell.com/mcp/ · Declared URL https://mcp.greetwell.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.greetwell.com CN=YR2,O=Let's Encrypt,C=US 17 Oct 2026 15 Jan 2027 RSA 2048 SHA256-RSA 689f3c6abff407b4d17c7dac35b12aea733
SANs: mcp.greetwell.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of mcp.greetwell.com. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
greetwell.com. DS published 2371 13 Verified
mcp.greetwell.com. Verified address RRset verified with the apex keys
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 3 probes
Transport URL Outcome Status Location
streamable-http https://mcp.greetwell.com/mcp Redirected 308 /mcp/
streamable-http · followed https://mcp.greetwell.com/mcp/ Verified 200
http (plaintext) http://mcp.greetwell.com/mcp HTTPS enforced 301 https://mcp.greetwell.com/mcp
MCP tools · 4 exposed · ~325 tokens

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 →

Tool Tokens
get_activity_availability ~45

Read-only availability for an activity on a date (YYYY-MM-DD).

NameTypeReqDescription
datestringyes–
party_size–––
product_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_activity_details ~86

Read-only details for a single activity/product. Response includes `booking_link`, `thumbnail_url`, `group_size`, and a standardized `item_card`. Listing content fields (`additional_details`, `perfect_for`, `faq_items`) carry authoritative eligibility and logistics rules (e.g. minimum age, what to wear); check them before answering guest questions.

NameTypeReqDescription
product_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_complementary_recommendation ~104

Read-only ranked complementary activities anchored to a source product_id. Each recommendation includes `booking_link`, `thumbnail_url`, and a standardized `item_card`.

NameTypeReqDescription
date–––
has_children–––
includes_children–––
location–––
max_recommendationsinteger––
party_size–––
product_idstringyes–
radius_milesnumber––
time_slot–––

Structured output declared, but exposes no named fields.

No examples provided.

search_activities ~90

Read-only search for activities by location/query/date. Each result includes `booking_link`, `thumbnail_url`, `group_size`, and a standardized `item_card`.

NameTypeReqDescription
date–––
has_children–––
includes_children–––
limitinteger––
location–––
party_size–––
query–––
radius_milesnumber––

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the io.github.greetwell/mcp server?

io.github.greetwell/mcp is a hosted endpoint at https://mcp.greetwell.com/mcp, 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.greetwell.com

# add to Claude Code
claude mcp add --transport http greetwell-mcp 'https://mcp.greetwell.com/mcp'
Common questions

What is the io.github.greetwell/mcp server?

io.github.greetwell/mcp is listed in the public MCP registry as io.github.greetwell/mcp. Discover and book 5,000+ curated local experiences across 500 US destinations. This page covers its hosted endpoint (https://mcp.greetwell.com/mcp).

Is the io.github.greetwell/mcp server safe to use?

io.github.greetwell/mcp scores 76 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 io.github.greetwell/mcp server expose?

io.github.greetwell/mcp exposes 4 tools: search_activities, get_activity_details, get_activity_availability, get_complementary_recommendation. Their descriptions and schemas cost roughly 325 tokens of context every time the server is loaded.

Does the io.github.greetwell/mcp server require authentication?

No. We connected to io.github.greetwell/mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.greetwell/mcp server still maintained?

io.github.greetwell/mcp is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the io.github.greetwell/mcp server?

VerifyMCP ran 12 checks on io.github.greetwell/mcp, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about io.github.greetwell/mcp: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.