Himalayan Lighthouse
REMOTE · HIMALAYAN-LIGHTHOUSE.DUMAGUETE.UK
The pages, on a network of free sites, that answer a subject. Lit as the World looks it up.
Available components
Last scanned (13 hours ago)
Scores higher than 54% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Search and Retrieval
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 Security69
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 487 tokens (~97/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability check failed: schema churn in the 11 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 3 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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 (12)
- TLS certificate
- Authorization
- 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.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
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 →
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3.
- 11 Nov 26 +10
- Stability: unverified → fail ▼ security
- Tool “lit_now” was removed ▼ security
- Authorization: unverified → partial ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “suggest” rewrote its description, which is the text the model reads security
- Schema quality: 69 → 97 ▼ functional
- Tool coverage: 50% → 100% ▲ functional
- Tool “list_sites” now declares an output schema ▲ functional
- Tool “suggest” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- Server version: 2.2.3 → 2.4.1 functional
- New tool “fetch” functional
- New tool “list_trending_pages” functional
- New tool “search” functional
- Tool “list_sites” changed its title: List the sites cosmetic
- Tool “suggest” changed its title: Suggest pages from the first words cosmetic
- 10 Nov 26 59
First indexed and scored.
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://himalayan-lighthouse.dumaguete.uk/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=dumaguete.uk | CN=WE1,O=Google Trust Services,C=US | 9 Nov 2026 | 7 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | f64cf1c855b696c513519462670e9d4c |
| SANs: dumaguete.uk, himalayan-lighthouse.dumaguete.uk, *.himalayan-lighthouse.dumaguete.uk | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of himalayan-lighthouse.dumaguete.uk. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| uk. | DS published | 43876 | 8 | Verified |
| dumaguete.uk. | No DS | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://himalayan-lighthouse.dumaguete.uk/mcp | Verified | 200 | |
| http (plaintext) | http://himalayan-lighthouse.dumaguete.uk/mcp | Inconclusive | 405 |
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 →
fetch Read a page of the network ~77
Read one page found with search (or any page of a site of this network): its title, its text and its address, for quoting and citing. Takes the id search returned. It reads pages of this network only; any other address is refused.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The id of a search result (the page's https address). |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| metadata | object | – | – |
| text | string | yes | – |
| title | string | yes | – |
| url | string | yes | – |
No examples provided.
list_sites List the sites ~21
Every site of the network with what it answers and its address.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| sites | array | yes | – |
No examples provided.
list_trending_pages List trending subjects and their pages ~87
What people around the World are looking up right now (search trends, most-read subjects, the day's events) and the page of the network that answers each, newest first. Each page was opened and checked before it was listed. Use it when the user asks what is trending or what people are looking up now.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many (10 when left out). |
| Name | Type | Req | Description |
|---|---|---|---|
| now | array | yes | – |
No examples provided.
search Search the network ~105
Search one network of websites (courses on any subject, a multilingual dictionary and encyclopedia, live disaster warnings, visa rules, everyday tools) for the pages that answer a query. Returns up to 8 results, each with an id to pass to fetch, a title and an address a person can open. Use it when the user asks about a subject one of these sites covers; it does not search the wider web.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | The subject, in a few words. |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
No examples provided.
suggest Suggest pages from the first words ~99
From the first words of a subject (a prefix is enough), the pages of the network that answer it: pages being looked up right now first, then the site whose subject it is. Returns up to 8 { title, url, site, line }. With no words it returns what is being looked up right now.
| Name | Type | Req | Description |
|---|---|---|---|
| q | string | – | The subject, or the first words of it. Empty = what the World is looking up right now. |
| Name | Type | Req | Description |
|---|---|---|---|
| q | string | – | – |
| suggestions | array | yes | – |
No examples provided.
How do I install the Himalayan Lighthouse MCP server?
Himalayan Lighthouse is a hosted endpoint at https://himalayan-lighthouse.dumaguete.uk/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 · himalayan-lighthouse.dumaguete.uk
claude mcp add --transport http dagrang-repository-himalayan-lighthouse 'https://himalayan-lighthouse.dumaguete.uk/mcp'
What is the Himalayan Lighthouse MCP server?
Himalayan Lighthouse is an MCP server listed in the public MCP registry as io.github.dagrang-repository/himalayan-lighthouse. The pages, on a network of free sites, that answer a subject. Lit as the World looks it up. This page covers its hosted endpoint (https://himalayan-lighthouse.dumaguete.uk/mcp).
Is the Himalayan Lighthouse MCP server safe to use?
Himalayan Lighthouse scores 70 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 Himalayan Lighthouse MCP server expose?
Himalayan Lighthouse exposes 5 tools: search, fetch, suggest, list_trending_pages, list_sites. Their descriptions and schemas cost roughly 389 tokens of context every time the server is loaded.
Does the Himalayan Lighthouse MCP server require authentication?
No. We connected to Himalayan Lighthouse without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Himalayan Lighthouse MCP server still maintained?
Himalayan Lighthouse 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 Himalayan Lighthouse MCP server?
VerifyMCP ran 12 checks on Himalayan Lighthouse, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Himalayan Lighthouse: HTTPS. 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.