Fenlight
REMOTE · FENLIGHT.WAGGLE.AE
Google search results, forum threads, local and shopping data, keyword ideas, AI answer tracking.
Available components
Last scanned (1 hour ago)
Scores higher than 62% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Marketing and SEO
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability50
- AI-judged instruction clarity (fair).Partial
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 14% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 9 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
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.
- 23 Oct 26 0
- Tool “keyword_ideas” rewrote its description, which is the text the model reads security
- 22 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.
- 20 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.
- 18 Oct 26 +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.
- 17 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 16 Oct 26 69
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 23 Oct 2026 · Probed https://fenlight.waggle.ae/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=fenlight.waggle.ae | CN=YE2,O=Let's Encrypt,C=US | 16 Oct 2026 | 14 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6fc6e48fe9c89aa535aa75fe0bf655b459b |
| SANs: fenlight.waggle.ae | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of fenlight.waggle.ae. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ae. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="fenlight"
Bearer realm="fenlight"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://fenlight.waggle.ae/mcp | Verified | 400 | |
| http (plaintext) | http://fenlight.waggle.ae/mcp | HTTPS enforced | 308 | https://fenlight.waggle.ae/mcp |
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 →
ai_answers AI Answers and Brand Visibility ~301
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.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | yes | 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 | yes | The question to put to the assistant, as a buyer would ask it |
| samples | integer | – | Times the question is asked of the assistant |
No output schema declared.
No examples provided.
company_serp_footprint Company Search Footprint ~113
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).
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | – |
| depth | integer | – | – |
| domain | – | – | – |
| fresh | boolean | – | – |
| gl | string | – | – |
| hl | string | – | – |
| location | string | – | – |
No output schema declared.
No examples provided.
extract_local_places Google Local Places ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| fresh | boolean | – | – |
| gl | string | – | – |
| hl | string | – | – |
| location | – | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
extract_shopping_results Google Shopping Results ~78
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.
| Name | Type | Req | Description |
|---|---|---|---|
| fresh | boolean | – | – |
| gl | string | – | – |
| hl | string | – | – |
| location | – | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
find_discussion_candidates Forum and Discussion Finder ~99
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.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | integer | – | – |
| fresh | boolean | – | – |
| gl | string | – | – |
| hl | string | – | – |
| location | – | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
geo_citation_radar GEO Citation Radar ~135
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.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | – | – | – |
| depth | integer | – | – |
| domain | – | – | – |
| engine | string | – | – |
| fresh | boolean | – | – |
| gl | string | – | – |
| hl | string | – | – |
| location | string | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
google_serp Google Search Results ~163
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.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | integer | – | – |
| fresh | boolean | – | – |
| gl | string | – | – |
| hl | string | – | – |
| local_pack | boolean | – | – |
| location | – | – | – |
| query | string | yes | – |
| shopping | boolean | – | – |
No output schema declared.
No examples provided.
keyword_ideas Keyword Ideas ~222
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.
| Name | Type | Req | Description |
|---|---|---|---|
| expand | – | – | – |
| fresh | boolean | – | – |
| gl | – | – | – |
| hl | – | – | – |
| limit | integer | – | – |
| location | – | – | – |
| location_code | – | – | – |
| seed | string | yes | – |
No output schema declared.
No examples provided.
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.
remote · fenlight.waggle.ae
claude mcp add --transport http ae-waggle-fenlight 'https://fenlight.waggle.ae/mcp'
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.