# SeekinWeb — AI visibility (remote · seekinweb.com)

Does AI recommend a business? Who it names instead, which sources it uses, plus AI readability.

- Trust score: 82/100 (high trust)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `seekinweb.com`: 82/100 (this document), [markdown](https://verifymcp.io/servers/com-seekinweb-ai-visibility/api-mcp.md), [page](https://verifymcp.io/servers/com-seekinweb-ai-visibility/api-mcp)

## Channel facts

- Endpoint: `https://seekinweb.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.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-05.

- **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**: 77/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 543 tokens (~181/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the SeekinWeb — AI visibility MCP server?

SeekinWeb — AI visibility is a hosted endpoint at https://seekinweb.com/api/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 com-seekinweb-ai-visibility 'https://seekinweb.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-seekinweb-ai-visibility": {
      "url": "https://seekinweb.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-seekinweb-ai-visibility": {
      "type": "http",
      "url": "https://seekinweb.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-seekinweb-ai-visibility]
url = "https://seekinweb.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-seekinweb-ai-visibility": {
      "type": "remote",
      "url": "https://seekinweb.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-seekinweb-ai-visibility --url 'https://seekinweb.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-seekinweb-ai-visibility:
    url: "https://seekinweb.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-seekinweb-ai-visibility": {
      "Transport": "http",
      "Url": "https://seekinweb.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-seekinweb-ai-visibility -t streamable-http -u 'https://seekinweb.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-seekinweb-ai-visibility": {
      "type": "http",
      "url": "https://seekinweb.com/api/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-01 (score 82, +1)

- [security] Stability: 0.97 → pass

### 2026-10-30 (score 81, +1)

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

### 2026-10-28 (score 80, +1)

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

### 2026-10-25 (score 79, +1)

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

### 2026-10-23 (score 78, +1)

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

### 2026-10-21 (score 77, +1)

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

### 2026-10-19 (score 76, +1)

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

### 2026-10-17 (score 75, +1)

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

## MCP tools (3)

### `check_ai_recommendations` (~162 tokens)

Check AI recommendations

Checks whether an AI assistant with live web search recommends a business when a customer asks for what it offers, without naming it. Returns how many answers named the business, which brands were named instead, which websites the assistant relied on (the sources to be present on), and what the assistant says about the business. Runs in the background on first use (about a minute): if it reports that the test is running, call it again shortly. Free, no account.

Input parameters:

- `lang` (string): Output language: "en" (default) or "es".
- `url` (string, required): Domain or URL of the site, e.g. "example.com" or "https://example.com". Use your own site or one you are authorized to review.

### `scan_website` (~143 tokens)

Scan AI readability

Scans a website and returns its AI Visibility Score (0-100): whether AI crawlers and agents can find, read and cite it. Eight weighted signals (content readable without JavaScript, AI crawler access in robots.txt, structured data, semantic structure, metadata, performance, llms.txt, sitemap), each with a concrete fix when it fails. Free, no account.

Input parameters:

- `lang` (string): Output language: "en" (default) or "es".
- `url` (string, required): Domain or URL of the site, e.g. "example.com" or "https://example.com". Use your own site or one you are authorized to review.

### `generate_llms_txt` (~129 tokens)

Generate llms.txt

Drafts an llms.txt file (llmstxt.org convention) for the root of a domain: a structured summary of the site for language models and agents, derived from the page's real content. Returns the file text. Note: llms.txt is an emerging convention with unproven impact.

Input parameters:

- `lang` (string): Output language: "en" (default) or "es".
- `url` (string, required): Domain or URL of the site, e.g. "example.com" or "https://example.com". Use your own site or one you are authorized to review.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-seekinweb-ai-visibility/api-mcp#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 82
- 2026-11-03: 82
- 2026-11-02: 82
- 2026-11-01: 82
- 2026-10-31: 81
- 2026-10-30: 81
- 2026-10-29: 80
- 2026-10-28: 80
- 2026-10-27: 79
- 2026-10-26: 79
- 2026-10-25: 79
- 2026-10-24: 78
- 2026-10-23: 78
- 2026-10-22: 77
- 2026-10-21: 77
- 2026-10-20: 76
- 2026-10-19: 76
- 2026-10-18: 75
- 2026-10-17: 75
- 2026-10-16: 74
- 2026-10-15: 74
- 2026-10-14: 73
- 2026-10-13: 73
- 2026-10-12: 72
- 2026-10-10: 72
- 2026-10-05: 69
- 2026-10-04: 69
- 2026-10-03: 68
- 2026-10-02: 68

## Common questions

### What is the SeekinWeb — AI visibility MCP server?

SeekinWeb — AI visibility is an MCP server listed in the public MCP registry as com.seekinweb/ai-visibility. Does AI recommend a business? Who it names instead, which sources it uses, plus AI readability. This page covers its hosted endpoint (https://seekinweb.com/api/mcp).

### Is the SeekinWeb — AI visibility MCP server safe to use?

SeekinWeb — AI visibility scores 82 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 SeekinWeb — AI visibility MCP server expose?

SeekinWeb — AI visibility exposes 3 tools: check_ai_recommendations, scan_website, generate_llms_txt. Their descriptions and schemas cost roughly 434 tokens of context every time the server is loaded.

### Does the SeekinWeb — AI visibility MCP server require authentication?

No. We connected to SeekinWeb — AI visibility without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the SeekinWeb — AI visibility MCP server still maintained?

SeekinWeb — AI visibility is still listed as active in the MCP registry. We last reached this channel on 5 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 SeekinWeb — AI visibility MCP server?

VerifyMCP ran 12 checks on SeekinWeb — AI visibility, 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 SeekinWeb — AI visibility: 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://seekinweb.com/api/mcp
- Website: https://seekinweb.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-seekinweb-ai-visibility/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-seekinweb-ai-visibility/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-seekinweb-ai-visibility/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-seekinweb-ai-visibility/api-mcp