whereamimentioned
REMOTE · WHEREAMIMENTIONED.COM
Measure whether AI assistants mention your brand. Reports, model answers, scans, free site tools.
Available components
Last scanned (17 hours ago)
Scores higher than 65% of remote servers
Reachable. Last reached 21 Nov 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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- 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 Usability65
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 525 tokens (~75/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 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
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 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
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 7 Nov 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 21 Nov 2026 · Probed https://whereamimentioned.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=whereamimentioned.com | CN=YR1,O=Let's Encrypt,C=US | 22 Sept 2026 | 21 Dec 2026 | RSA 2048 | SHA256-RSA | 50e034eade3610289aee67ad0512a9477c8 |
| SANs: whereamimentioned.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of whereamimentioned.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| whereamimentioned.com. | No DS | 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; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://whereamimentioned.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://whereamimentioned.com/api/mcp | HTTPS enforced | 308 | https://whereamimentioned.com/api/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_content_chunking Analyze content chunking ~50
Analyze how well a page is chunked for retrieval: per-heading sections with word and token counts, findings by severity, strengths, a score and the top fixes.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| chunks | array | yes | – |
| docFindings | array | yes | – |
| errors | integer | yes | – |
| mode | string | yes | – |
| score | integer | yes | – |
| strengthCount | integer | yes | – |
| topFixes | array | yes | – |
| totalTokens | integer | yes | – |
| totalWords | integer | yes | – |
| url | string | yes | – |
| warnings | integer | yes | – |
No examples provided.
check_ai_crawler_access Check AI crawler access ~61
Check whether a site's robots.txt allows or blocks each known AI crawler (GPTBot, ClaudeBot, PerplexityBot, Google-Extended and about thirty others), with the exact rule and line that decided it.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| bots | array | yes | – |
| origin | string | yes | – |
| robotsMissing | boolean | yes | – |
| robotsServerError | boolean | yes | – |
| robotsStatus | integer | yes | – |
| sitemaps | array | yes | – |
| summary | object | yes | – |
| truncated | boolean | yes | – |
No examples provided.
check_meta_description Check meta description ~57
Analyze a page's title, meta description, og:description and opening paragraph: character and pixel widths, where desktop and mobile truncate, a score and per-check findings.
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | – | – |
| url | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| chars | integer | yes | – |
| checks | array | yes | – |
| desktopCutoff | – | yes | – |
| mobileCutoff | – | yes | – |
| openingParagraphChecks | array | yes | – |
| pixels | integer | yes | – |
| score | integer | yes | – |
| untrusted | object | yes | – |
| url | string | yes | – |
No examples provided.
generate_llms_txt Generate llms.txt ~84
Crawl a site and generate an llms.txt. depth "index" produces the link index (up to 30 pages); depth "full" produces llms-full.txt with extracted page content (up to 20 pages).
| Name | Type | Req | Description |
|---|---|---|---|
| depth | string | – | – |
| description | string | – | – |
| siteName | string | – | – |
| url | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| depth | string | yes | – |
| discoveredVia | string | yes | – |
| estTokens | integer | – | – |
| notices | array | yes | – |
| pageCount | integer | yes | – |
| skippedCount | integer | yes | – |
| timedOut | boolean | yes | – |
| totalWords | integer | – | – |
| untrusted | object | yes | – |
No examples provided.
generate_sitemap Generate sitemap ~52
Crawl a site (up to 200 pages, sitemap-first with a link-following fallback) and return a valid sitemap.xml, with lastmod only where it was genuinely observed.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| discoveredVia | string | yes | – |
| skipped | integer | yes | – |
| timedOut | boolean | yes | – |
| untrusted | object | yes | – |
| urlCount | integer | yes | – |
No examples provided.
validate_llms_txt Validate llms.txt ~62
Fetch and validate a site's llms.txt: findings with severity and line numbers, a 0 to 100 score, section and entry counts, whether the linked URLs resolve, and whether a sibling llms-full.txt exists.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| brokenLinks | array | yes | – |
| findings | array | yes | – |
| hasLlmsFullTxt | boolean | yes | – |
| linksChecked | integer | yes | – |
| missing | boolean | yes | – |
| origin | string | yes | – |
| score | – | yes | – |
| stats | – | yes | – |
| status | integer | yes | – |
No examples provided.
validate_structured_data Validate structured data ~70
Fetch a page, validate its JSON-LD entities against the schema.org types that matter for AI visibility, and report per-entity findings with severity, entity counts and a score. Also reports how many microdata and RDFa annotations are present, without validating them.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| blocks | array | yes | – |
| entityCount | integer | yes | – |
| errors | integer | yes | – |
| microdataCount | integer | yes | – |
| passes | integer | yes | – |
| rdfaCount | integer | yes | – |
| score | integer | yes | – |
| url | string | yes | – |
| warnings | integer | yes | – |
No examples provided.
How do I install the whereamimentioned MCP server?
whereamimentioned is a hosted endpoint at https://whereamimentioned.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.
remote · whereamimentioned.com
claude mcp add --transport http com-whereamimentioned-whereamimentioned 'https://whereamimentioned.com/api/mcp'
What is the whereamimentioned MCP server?
whereamimentioned is an MCP server listed in the public MCP registry as com.whereamimentioned/whereamimentioned. Measure whether AI assistants mention your brand. Reports, model answers, scans, free site tools. This page covers its hosted endpoint (https://whereamimentioned.com/api/mcp).
Is the whereamimentioned MCP server safe to use?
whereamimentioned scores 76 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 whereamimentioned MCP server expose?
whereamimentioned exposes 7 tools: check_ai_crawler_access, validate_llms_txt, generate_llms_txt, generate_sitemap, analyze_content_chunking, and 2 more. Their descriptions and schemas cost roughly 436 tokens of context every time the server is loaded.
Does the whereamimentioned MCP server require authentication?
No. We connected to whereamimentioned without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the whereamimentioned MCP server still maintained?
whereamimentioned 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 whereamimentioned MCP server?
VerifyMCP ran 13 checks on whereamimentioned, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.