Analook — Competitor Intelligence
REMOTE · WWW.ANALOOK.COM · SCANNED SEP 20
Competitor intelligence for AI agents — SEO, traffic, social, Product Hunt, pricing, AI insights.
Available components
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability56
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2981 tokens (~372/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 Management48
- Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 8 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 69% 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the Analook — Competitor Intelligence MCP server?
Analook — Competitor Intelligence is a hosted endpoint at https://www.analook.com/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 · www.analook.com
claude mcp add --transport http gingiris-1031-analook 'https://www.analook.com/mcp/'
{
"mcpServers": {
"gingiris-1031-analook": {
"url": "https://www.analook.com/mcp/"
}
}
} {
"servers": {
"gingiris-1031-analook": {
"type": "http",
"url": "https://www.analook.com/mcp/"
}
}
} [mcp_servers.gingiris-1031-analook] url = "https://www.analook.com/mcp/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"gingiris-1031-analook": {
"type": "remote",
"url": "https://www.analook.com/mcp/",
"enabled": true
}
}
} openclaw mcp add gingiris-1031-analook --url 'https://www.analook.com/mcp/' --transport streamable-http
mcp_servers:
gingiris-1031-analook:
url: "https://www.analook.com/mcp/" {
"McpServers": {
"gingiris-1031-analook": {
"Transport": "http",
"Url": "https://www.analook.com/mcp/"
}
}
} assistant mcp add gingiris-1031-analook -t streamable-http -u 'https://www.analook.com/mcp/'
{
"mcpServers": {
"gingiris-1031-analook": {
"type": "http",
"url": "https://www.analook.com/mcp/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 19 Sept 26 −8
- Stability: pass → fail ▼ security
- A breaking change shipped without a version bump: still 1.12.4 ▼ security
- Schema quality: 272 → 372 ▼ functional
- “analyze_competitor” added a required parameter “llm_model”, so existing callers break ▼ functional
- “browse_public_reports” added a required parameter “llm_model”, so existing callers break ▼ functional
- “get_growth_audit” added a required parameter “llm_model”, so existing callers break ▼ functional
- “get_report” added a required parameter “llm_model”, so existing callers break ▼ functional
- “get_report_markdown” added a required parameter “llm_model”, so existing callers break ▼ functional
- “get_report_status” added a required parameter “llm_model”, so existing callers break ▼ functional
- “list_my_reports” added a required parameter “llm_model”, so existing callers break ▼ functional
- “run_growth_audit” added a required parameter “llm_model”, so existing callers break ▼ functional
- Tool coverage: 59% → 69% ▲ functional
- Schema quality: excellent → good functional
- “analyze_competitor” reworded the description of “context” cosmetic
- “browse_public_reports” reworded the description of “context” cosmetic
- “get_growth_audit” reworded the description of “context” cosmetic
- “get_report” reworded the description of “context” cosmetic
- “get_report_markdown” reworded the description of “context” cosmetic
- “get_report_status” reworded the description of “context” cosmetic
- “list_my_reports” reworded the description of “context” cosmetic
- “run_growth_audit” reworded the description of “context” cosmetic
- 14 Sept 26 +7
- Stability: fail → pass ▲ security
- 5 Sept 26 −7
- Stability: pass → fail ▼ security
- 26 Aug 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Aug 26 0
- A breaking change shipped without a version bump: still 1.12.4 ▼ security
- Schema quality: 122 → 272 ▼ functional
- “analyze_competitor” added a required parameter “context”, so existing callers break ▼ functional
- “browse_public_reports” added a required parameter “context”, so existing callers break ▼ functional
- “get_growth_audit” added a required parameter “context”, so existing callers break ▼ functional
- “get_report” added a required parameter “context”, so existing callers break ▼ functional
- “get_report_markdown” added a required parameter “context”, so existing callers break ▼ functional
- “get_report_status” added a required parameter “context”, so existing callers break ▼ functional
- “list_my_reports” added a required parameter “context”, so existing callers break ▼ functional
- “run_growth_audit” added a required parameter “context”, so existing callers break ▼ functional
- Tool coverage: 0% → 59% ▲ functional
- “analyze_competitor” added an optional parameter “conversation_id” cosmetic
- “browse_public_reports” added an optional parameter “conversation_id” cosmetic
- “get_growth_audit” added an optional parameter “conversation_id” cosmetic
- “get_report” added an optional parameter “conversation_id” cosmetic
- “get_report_markdown” added an optional parameter “conversation_id” cosmetic
- “get_report_status” added an optional parameter “conversation_id” cosmetic
- “list_my_reports” added an optional parameter “conversation_id” cosmetic
- “run_growth_audit” added an optional parameter “conversation_id” cosmetic
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 20 Sept 2026 · Probed https://www.analook.com/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.analook.com | CN=YE2,O=Let's Encrypt,C=US | 30 Jul 2026 | 28 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 63c94dba9c2979c6fc6c1e2d1cf54d0f501 |
| SANs: www.analook.com | ||||||
| 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 www.analook.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| analook.com. | absent | 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 |
| content-security-policy | frame-ancestors 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.analook.com/mcp/ | Verified | 200 | |
| http (plaintext) | http://www.analook.com/mcp/ | HTTPS enforced | 301 | https://www.analook.com/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 →
analyze_competitor ~482
Submit a competitor analysis job. Analyzes a competitor's website across 15+ data sources (SEO, traffic, social, Product Hunt, GitHub, Wayback Machine history, AI-generated insights, etc.) and returns a job_id. Use get_report_status(job_id) to poll and get_report(job_id) to retrieve results when status='completed'. Typical analysis takes 2-5 minutes. Requires authentication (deducts 1 credit from your Analook balance). Args: url: Competitor website URL (e.g. 'https://linear.app' or 'lovable.dev') product_name: Optional product name override (defaults to domain) lang: Report language, 'en' (default) or 'zh' for Chinese output Returns: {job_id: str, status: 'started', poll_url: str} on success {error: str, hint?: str} on auth/validation failure
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include,… |
| conversation_id | string | – | Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. |
| lang | – | – | – |
| llm_model | string | yes | The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model… |
| product_name | – | – | – |
| url | string | yes | – |
No output schema declared.
No examples provided.
browse_public_reports ~359
Browse Analook's public competitor-intelligence report gallery. Returns recently published public reports (product name, domain, category, and a link). No authentication or credits required — a fast way to discover existing analyses before spending a credit on a fresh one. Args: category: Optional filter, e.g. 'AI / Agents', 'Dev Tools', 'Crypto / Web3', 'Marketing / SEO', 'SaaS / Other'
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | – | – |
| context | string | yes | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include,… |
| conversation_id | string | – | Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. |
| llm_model | string | yes | The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model… |
No output schema declared.
No examples provided.
get_growth_audit ~343
Fetch a Growth Audit's three reports (Executive Summary, Diagnosis, Action Plan) as Markdown. Args: job_id: ID from run_growth_audit() (starts with 'ga-') Returns: {status, reports: {executive_summary, diagnosis_report, action_plan}} while running, only {status, progress} is returned.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include,… |
| conversation_id | string | – | Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. |
| job_id | string | yes | – |
| llm_model | string | yes | The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model… |
No output schema declared.
No examples provided.
get_report ~375
Fetch the full competitor analysis report as structured JSON. Reports contain: website snapshot, Wayback Machine history, SEO/traffic data (DataForSEO), social media presence, Product Hunt launches, GitHub stats, pricing, funding, AI-generated business insights, growth playbooks, and more. Args: job_id: ID from analyze_competitor(); status must be 'completed' Returns: The full report dict (nested structure), or {error} if not found / not ready.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include,… |
| conversation_id | string | – | Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. |
| job_id | string | yes | – |
| llm_model | string | yes | The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model… |
No output schema declared.
No examples provided.
get_report_markdown ~336
Fetch the competitor analysis report as human-readable Markdown. Suitable for piping into agents that prefer text over structured JSON, or for direct display to end users. Args: job_id: ID from analyze_competitor(); status must be 'completed' Returns: {markdown: str} or {error: str}
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include,… |
| conversation_id | string | – | Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. |
| job_id | string | yes | – |
| llm_model | string | yes | The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model… |
No output schema declared.
No examples provided.
get_report_status ~315
Poll an analysis job's status. Args: job_id: ID returned from analyze_competitor() Returns: {status: 'running'|'completed'|'failed', progress?: str, report_url?: str}
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include,… |
| conversation_id | string | – | Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. |
| job_id | string | yes | – |
| llm_model | string | yes | The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model… |
No output schema declared.
No examples provided.
list_my_reports ~335
List your recent competitor analysis reports (up to 50). Requires authentication. Returns a lightweight list (id, url, product_name, created_at, status) — use get_report(job_id) to fetch the full report for any of them. Returns: {reports: [{id, url, product_name, created_at, status}, ...]}
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include,… |
| conversation_id | string | – | Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. |
| llm_model | string | yes | The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model… |
No output schema declared.
No examples provided.
run_growth_audit ~436
Run a full Growth Audit — three linked strategic reports for a product. Unlike analyze_competitor (a single 15-signal intelligence snapshot), a Growth Audit produces an Executive Summary + a Diagnosis Report + a 30-day Action Plan, grounded in real channel/tactic playbooks. Best for 'how do I grow THIS product' rather than 'what is this competitor doing'. Takes ~4-6 minutes. Requires authentication and deducts 10 credits. Poll with get_growth_audit(job_id) until status='completed'. Args: url: Product website URL to audit product_name: Optional product name override (defaults to domain) lang: Report language, 'en' (default) or 'zh'
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include,… |
| conversation_id | string | – | Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. |
| lang | – | – | – |
| llm_model | string | yes | The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model… |
| product_name | – | – | – |
| url | string | yes | – |
No output schema declared.
No examples provided.
What is the Analook — Competitor Intelligence MCP server?
Analook — Competitor Intelligence is an MCP server listed in the public MCP registry as io.github.Gingiris-1031/analook. Competitor intelligence for AI agents, SEO, traffic, social, Product Hunt, pricing, AI insights. This page covers its hosted endpoint (https://www.analook.com/mcp/).
Is the Analook — Competitor Intelligence MCP server safe to use?
Analook — Competitor Intelligence scores 68 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 Analook — Competitor Intelligence MCP server expose?
Analook — Competitor Intelligence exposes 8 tools: analyze_competitor, get_report_status, get_report, get_report_markdown, list_my_reports, and 3 more. Their descriptions and schemas cost roughly 2,981 tokens of context every time the server is loaded.
Does the Analook — Competitor Intelligence MCP server require authentication?
No. We connected to Analook — Competitor Intelligence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Analook — Competitor Intelligence MCP server still maintained?
Analook — Competitor Intelligence is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.