# 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.

- Trust score: 70/100 (medium)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `himalayan-lighthouse.dumaguete.uk`: 70/100 (this document), [markdown](https://verifymcp.io/servers/dagrang-repository-himalayan-lighthouse/himalayan-lighthouse.md), [page](https://verifymcp.io/servers/dagrang-repository-himalayan-lighthouse/himalayan-lighthouse)

## Channel facts

- Endpoint: `https://himalayan-lighthouse.dumaguete.uk/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 69/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 487 tokens (~97/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability check failed: schema churn in the 11 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 3 additions.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http dagrang-repository-himalayan-lighthouse 'https://himalayan-lighthouse.dumaguete.uk/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dagrang-repository-himalayan-lighthouse": {
      "url": "https://himalayan-lighthouse.dumaguete.uk/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dagrang-repository-himalayan-lighthouse": {
      "type": "http",
      "url": "https://himalayan-lighthouse.dumaguete.uk/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dagrang-repository-himalayan-lighthouse]
url = "https://himalayan-lighthouse.dumaguete.uk/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dagrang-repository-himalayan-lighthouse": {
      "type": "remote",
      "url": "https://himalayan-lighthouse.dumaguete.uk/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dagrang-repository-himalayan-lighthouse --url 'https://himalayan-lighthouse.dumaguete.uk/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dagrang-repository-himalayan-lighthouse:
    url: "https://himalayan-lighthouse.dumaguete.uk/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dagrang-repository-himalayan-lighthouse": {
      "Transport": "http",
      "Url": "https://himalayan-lighthouse.dumaguete.uk/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dagrang-repository-himalayan-lighthouse -t streamable-http -u 'https://himalayan-lighthouse.dumaguete.uk/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dagrang-repository-himalayan-lighthouse": {
      "type": "http",
      "url": "https://himalayan-lighthouse.dumaguete.uk/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 0 to 3.

### 2026-11-11 (score 69, +10)

- [security regression] Stability: unverified → fail
- [security regression] Tool “lit_now” was removed
- [security improvement] 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
- [functional regression] Schema quality: 69 → 97
- [functional improvement] Tool coverage: 50% → 100%
- [functional improvement] Tool “list_sites” now declares an output schema
- [functional improvement] 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”
- [cosmetic] Tool “list_sites” changed its title: List the sites
- [cosmetic] Tool “suggest” changed its title: Suggest pages from the first words

### 2026-11-10 (score 59)

First indexed and scored.

## MCP tools (5)

### `search` (~105 tokens)

Search the network

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.

Input parameters:

- `query` (string, required): The subject, in a few words.

Output parameters:

- `results` (array)

### `fetch` (~77 tokens)

Read a page of the network

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.

Input parameters:

- `id` (string, required): The id of a search result (the page's https address).

Output parameters:

- `id` (string)
- `metadata` (object)
- `text` (string)
- `title` (string)
- `url` (string)

### `suggest` (~99 tokens)

Suggest pages from the first words

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.

Input parameters:

- `q` (string): The subject, or the first words of it. Empty = what the World is looking up right now.

Output parameters:

- `q` (string)
- `suggestions` (array)

### `list_trending_pages` (~87 tokens)

List trending subjects and their pages

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.

Input parameters:

- `limit` (integer): How many (10 when left out).

Output parameters:

- `now` (array)

### `list_sites` (~21 tokens)

List the sites

Every site of the network with what it answers and its address.

Output parameters:

- `sites` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dagrang-repository-himalayan-lighthouse/himalayan-lighthouse#diagnostics

## Score history

- 2026-11-21: 70
- 2026-11-20: 69
- 2026-11-19: 69
- 2026-11-18: 69
- 2026-11-17: 69
- 2026-11-16: 69
- 2026-11-15: 69
- 2026-11-14: 69
- 2026-11-13: 69
- 2026-11-12: 69
- 2026-11-11: 69
- 2026-11-10: 59

## Common questions

### 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.

## Links

- Remote endpoint: https://himalayan-lighthouse.dumaguete.uk/mcp
- Website: https://himalayan-lighthouse.dumaguete.uk/en/
- Changelog RSS feed: https://verifymcp.io/servers/dagrang-repository-himalayan-lighthouse/himalayan-lighthouse.xml
- Changelog JSON feed: https://verifymcp.io/servers/dagrang-repository-himalayan-lighthouse/himalayan-lighthouse/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dagrang-repository-himalayan-lighthouse/himalayan-lighthouse.json
- HTML version of this page: https://verifymcp.io/servers/dagrang-repository-himalayan-lighthouse/himalayan-lighthouse
