# Fenlight (remote · fenlight.waggle.ae)

Google search results, forum threads, local and shopping data, keyword ideas, AI answer tracking.

- Trust score: 72/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `fenlight.waggle.ae`: 72/100 (this document), [markdown](https://verifymcp.io/servers/ae-waggle-fenlight/fenlight.md), [page](https://verifymcp.io/servers/ae-waggle-fenlight/fenlight)

## Channel facts

- Endpoint: `https://fenlight.waggle.ae/mcp`
- Transports: `streamable-http`
- Auth: `required (not validated)`
- Version: `0.3.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-10-23.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - 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**: 50/100
  - AI-judged instruction clarity (fair).
  - Context-footprint check failed: tool/resource definitions use about 1289 tokens (~161/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 14% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "google_serp" implies "execute" and declares readOnlyHint instead, contradicting what its own name says it does.
  - An AI judge read all 9 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 Fenlight MCP server?

Fenlight is a hosted endpoint at https://fenlight.waggle.ae/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 ae-waggle-fenlight 'https://fenlight.waggle.ae/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ae-waggle-fenlight": {
      "url": "https://fenlight.waggle.ae/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ae-waggle-fenlight": {
      "type": "http",
      "url": "https://fenlight.waggle.ae/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ae-waggle-fenlight]
url = "https://fenlight.waggle.ae/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ae-waggle-fenlight": {
      "type": "remote",
      "url": "https://fenlight.waggle.ae/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ae-waggle-fenlight --url 'https://fenlight.waggle.ae/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ae-waggle-fenlight:
    url: "https://fenlight.waggle.ae/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ae-waggle-fenlight": {
      "Transport": "http",
      "Url": "https://fenlight.waggle.ae/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ae-waggle-fenlight -t streamable-http -u 'https://fenlight.waggle.ae/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ae-waggle-fenlight": {
      "type": "http",
      "url": "https://fenlight.waggle.ae/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-10-23 (score 72, 0)

- [security] Tool “keyword_ideas” rewrote its description, which is the text the model reads

### 2026-10-22 (score 72, +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.

### 2026-10-20 (score 71, +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.

### 2026-10-18 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-17 (score 69, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-16 (score 69)

First indexed and scored.

## MCP tools (8)

### `google_serp` (~163 tokens)

Google Search Results

Execute a full Google SERP search query with strict Google provenance (depth 10 to 100). Returns verified Google organic results with classification tagging (forums, video, ecommerce) and the results page's features (AI Overview, PAA, Knowledge Graph). The local pack and shopping are add-ons: set local_pack and/or shopping to true to include them. A result searched in the last 24 hours is served from the cache at a lower price; set fresh to true to search live.

Input parameters:

- `depth` (integer)
- `fresh` (boolean)
- `gl` (string)
- `hl` (string)
- `local_pack` (boolean)
- `location`
- `query` (string, required)
- `shopping` (boolean)

### `find_discussion_candidates` (~99 tokens)

Forum and Discussion Finder

Search Google and filter organic results (positions 1-100) specifically for community discussions and forum threads (Reddit, Quora, HackerNews, StackExchange, niche forums). Ideal for sentiment analysis, user discussions, and customer problem discovery.

Input parameters:

- `depth` (integer)
- `fresh` (boolean)
- `gl` (string)
- `hl` (string)
- `location`
- `query` (string, required)

### `extract_local_places` (~84 tokens)

Google Local Places

Extract Google Local Pack (3-pack) and Google Places listings for local queries. Returns place_id/cid, title, rating, review count, address, latitude/longitude, category, phone, and website.

Input parameters:

- `fresh` (boolean)
- `gl` (string)
- `hl` (string)
- `location`
- `query` (string, required)

### `extract_shopping_results` (~78 tokens)

Google Shopping Results

Extract Google Shopping carousel listings for e-commerce and product queries. Returns product title, price, currency, merchant, rating, reviews, image URL, link, and product ID.

Input parameters:

- `fresh` (boolean)
- `gl` (string)
- `hl` (string)
- `location`
- `query` (string, required)

### `geo_citation_radar` (~135 tokens)

GEO Citation Radar

Run GEO Citation & Injection Radar for a topic query and brand. Calculates citation probability score (0-100), identifies high-impact Reddit/Quora threads with injection playbooks, extracts listicle PR outreach targets with Vera contacts payload, discovers AEO question gaps from PAA, and produces an LLM-ready markdown injection brief.

Input parameters:

- `brand`
- `depth` (integer)
- `domain`
- `engine` (string)
- `fresh` (boolean)
- `gl` (string)
- `hl` (string)
- `location` (string)
- `query` (string, required)

### `company_serp_footprint` (~113 tokens)

Company Search Footprint

Audit a company's SERP digital footprint, brand reputation, owned domains, and entity profiles. Separates owned web properties, social/entity profiles (Wikipedia, LinkedIn, Instagram, Crunchbase), Google Maps locations, third-party mentions, and customer brand questions (PAA).

Input parameters:

- `company` (string, required)
- `depth` (integer)
- `domain`
- `fresh` (boolean)
- `gl` (string)
- `hl` (string)
- `location` (string)

### `keyword_ideas` (~222 tokens)

Keyword Ideas

Keyword ideas for a seed keyword from Google autocomplete (the seed plus question words or the alphabet), People Also Ask and related searches, cleaned and de-duplicated. Each idea carries its sources and an intent label (question, comparison, commercial, local, informational). Works in Arabic. Ideas only: no search volumes. Charged for the results page (6 credits live, 1 from your cache) plus 6 credits for each autocomplete call that returns suggestions, so at most 12 credits for expand 'none', 60 for 'questions' (the default), 168 for 'alphabet' (180 for an Arabic seed) and 186 for 'all'; it stops early once `limit` ideas are found, which is 12. Set fresh to true to search the results page live; autocomplete is always live.

Input parameters:

- `expand`
- `fresh` (boolean)
- `gl`
- `hl`
- `limit` (integer)
- `location`
- `location_code`
- `seed` (string, required)

### `ai_answers` (~301 tokens)

AI Answers and Brand Visibility

Put a buyer's question to an AI assistant that searches the live web, and see whether a brand and its competitors are named in the answer, in what rank, with the citations and cited domains behind it. The assistant is ChatGPT unless `engine` names claude, perplexity or gemini; an assistant the server has no key for answers not_configured and costs nothing. `samples` (1 to 5, default 1) asks the same question more than once, for a mention rate. Returns metrics per assistant, not the raw answers. Charged per call to the assistant at the price list in credits (see llms.txt), the same as POST /v1/ai/answers: the worst case is held first, only the calls made are charged, and a call where the assistant failed is charged nothing.

Input parameters:

- `brand` (string, required): Brand name to look for in the answer
- `brand_domain`: The brand's domain, for example roasters.ae
- `competitors`: Competitor names or domains to track
- `country` (string): Two-letter ISO country code of the market
- `engine` (string): The assistant to ask
- `language` (string): Language tag of the market, for example en or ar
- `prompt` (string, required): The question to put to the assistant, as a buyer would ask it
- `samples` (integer): Times the question is asked of the assistant

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ae-waggle-fenlight/fenlight#diagnostics

## Score history

- 2026-10-23: 72
- 2026-10-22: 72
- 2026-10-21: 71
- 2026-10-20: 71
- 2026-10-19: 70
- 2026-10-18: 70
- 2026-10-17: 69
- 2026-10-16: 69

## Common questions

### What is the Fenlight MCP server?

Fenlight is an MCP server listed in the public MCP registry as ae.waggle/fenlight. Google search results, forum threads, local and shopping data, keyword ideas, AI answer tracking. This page covers its hosted endpoint (https://fenlight.waggle.ae/mcp).

### Is the Fenlight MCP server safe to use?

Fenlight scores 72 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 Fenlight MCP server expose?

Fenlight exposes 8 tools: google_serp, find_discussion_candidates, extract_local_places, extract_shopping_results, geo_citation_radar, and 3 more. Their descriptions and schemas cost roughly 1,195 tokens of context every time the server is loaded.

### Does the Fenlight MCP server require authentication?

Yes. Fenlight asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Fenlight MCP server still maintained?

Fenlight is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://fenlight.waggle.ae/mcp
- Authorisation metadata: https://fenlight.waggle.ae/.well-known/oauth-protected-resource/mcp
- Changelog RSS feed: https://verifymcp.io/servers/ae-waggle-fenlight/fenlight.xml
- Changelog JSON feed: https://verifymcp.io/servers/ae-waggle-fenlight/fenlight.json
- HTML version of this page: https://verifymcp.io/servers/ae-waggle-fenlight/fenlight