Happy Endpoint
NPM · HAPPYENDPOINT-MCP
Real-time UAE property, retail and travel data: listings, transactions, rental yields, products.
Available components
Last scanned (8 hours ago)
Scores higher than 53% of npm servers
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 15 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1007 tokens (~100/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 78% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
- Security disclosure: unverified → fail ▼ functional
- 27 Oct 26 +5
- Source repository: fail → pass ▲ security
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
- Security disclosure: fail → unverified ▼ functional
- Stability: unverified → 0.07 ▲ 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 5 Nov 2026 · Analysed npm/happyendpoint-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
compare_rental_yields Compare rental yields across areas ~127
Calculate and compare gross rental yield for several UAE areas at once. Yield is annual rent divided by purchase price, the headline metric for buy-to-let investors. This is computed from live listings, not available as a single API call. Uses median asking prices, so treat it as a screening tool rather than a valuation.
| Name | Type | Req | Description |
|---|---|---|---|
| bedrooms | string | – | "0" studio, "1", "2". Default "1" |
| locations | array | yes | Area names, for example ["dubai marina", "jvc", "business bay"] |
| propertyType | string | – | – |
No output schema declared.
No examples provided.
find_agents Find real estate agents ~61
Find real estate agents active in a UAE area, with their agency and performance badges such as TruBroker. Useful for agent directories and for finding who is most active in a given community.
| Name | Type | Req | Description |
|---|---|---|---|
| location | string | yes | Area name |
| purpose | string | – | – |
No output schema declared.
No examples provided.
find_locations Find property locations ~105
Search UAE property locations by name. Returns matching areas, communities, and individual buildings with how many listings each has. Use this when a place name is ambiguous, or to discover what areas exist. Other property tools accept place names directly and resolve them for you, so you usually do not need to call this first.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum results, default 10 |
| query | string | yes | Place name, for example "dubai marina" or "jvc" |
No output schema declared.
No examples provided.
get_property_details Get full property details ~66
Full record for one property: specification, amenities, agency, and location hierarchy. Needs an id from search_properties. This endpoint is slow, often over 30 seconds, so prefer search_properties when its fields are enough.
| Name | Type | Req | Description |
|---|---|---|---|
| propertyId | string | yes | Property id from search_properties |
No output schema declared.
No examples provided.
get_transactions Get historical property transactions ~110
Actual recorded sale and rental transactions for a UAE area, with price per sqm and whether each was a first sale from the developer or a resale. This is what property really sold for, unlike search_properties which returns asking prices. Use this for valuation, market trends, and price-per-sqm questions.
| Name | Type | Req | Description |
|---|---|---|---|
| location | string | yes | Area name |
| page | integer | – | – |
| purpose | string | – | Default for-sale |
| timePeriod | string | – | Lookback window, default 12m |
No output schema declared.
No examples provided.
list_available_apis List available Happy Endpoint APIs ~45
List the data sources this server can reach, and where to subscribe to each. Useful when a call fails because of a missing subscription, or to see what data is available.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_hotels Search hotels ~113
Search hotels by destination and dates, with prices and availability. Give dates as YYYY-MM-DD; they are converted to the format the API expects. The destination is resolved to an internal id automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| adults | integer | – | Default 2 |
| checkIn | string | yes | YYYY-MM-DD |
| checkOut | string | yes | YYYY-MM-DD |
| currency | string | – | Default USD |
| destination | string | yes | City, airport, or hotel name |
| rooms | integer | – | Default 1 |
No output schema declared.
No examples provided.
search_off_plan Search off-plan developments ~101
Search off-plan and under-construction property projects in the UAE. Off-plan means not yet built, usually bought on a payment plan. Useful for questions about new developments, launches, and pre-handover payment terms.
| Name | Type | Req | Description |
|---|---|---|---|
| location | string | yes | Area name |
| maxPreHandoverPayment | number | – | Maximum percent payable before handover, for example 50 |
| page | integer | – | – |
| priceMax | number | – | AED |
No output schema declared.
No examples provided.
search_products Search retail products ~113
Search live retail product data by category. "beauty" covers cosmetics and skincare across the US, Canada, and France. "home" covers furniture and home goods across eight countries, and supports cross-country price comparison via countryCode.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | – |
| countryCode | string | – | Home category only. us, ca, gb, de, fr, it, se, ch. Default us |
| query | string | yes | Search term, for example "moisturizer" or "desk" |
No output schema declared.
No examples provided.
search_properties Search property listings ~166
Search UAE property listings for sale or rent by area, price, bedrooms, and type. Takes a place name, not an ID. Prices are AED; for rentals the price is the ANNUAL rent. Returns asking prices from current listings, which run higher than actual sale prices, so use get_transactions for what property really sold for.
| Name | Type | Req | Description |
|---|---|---|---|
| bedrooms | string | – | "0" is a studio, "1", "2", and so on |
| location | string | yes | Area name, for example "dubai marina", "jvc", "business bay" |
| page | integer | – | – |
| priceMax | number | – | AED |
| priceMin | number | – | AED |
| propertyType | string | – | – |
| purpose | string | – | Default for-sale |
No output schema declared.
No examples provided.
How do I install the Happy Endpoint MCP server?
Happy Endpoint runs locally as an npm package, launched with npx -y happyendpoint-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · happyendpoint-mcp
claude mcp add happyendpointhq-happyendpoint-mcp -- npx -y happyendpoint-mcp
What is the Happy Endpoint MCP server?
Happy Endpoint is an MCP server listed in the public MCP registry as io.github.happyendpointhq/happyendpoint-mcp. Real-time UAE property, retail and travel data: listings, transactions, rental yields, products. This page covers its npm package (happyendpoint-mcp).
Is the Happy Endpoint MCP server safe to use?
Happy Endpoint scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 Happy Endpoint MCP server expose?
Happy Endpoint exposes 10 tools: find_locations, search_properties, get_property_details, search_off_plan, get_transactions, and 5 more. Their descriptions and schemas cost roughly 1,007 tokens of context every time the server is loaded.
Is the Happy Endpoint MCP server still maintained?
Happy Endpoint is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Happy Endpoint MCP server under?
Happy Endpoint declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Happy Endpoint MCP server?
VerifyMCP ran 16 checks on Happy Endpoint, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.