MeSquared Visibility
Server Details
Public-site SEO/AEO readiness scans with evidence scores, issues, and clear measurement scope.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Available Tools
3 toolscompare_visibilityCompare SEO/AEO Website ReadinessARead-onlyIdempotentInspect
Run public-site SEO/AEO website-readiness scans for two business websites and compare aggregate scores, selected evidence, site signals, and top issues. This is a readiness comparison, not observed rank or live citation benchmarking.
| Name | Required | Description | Default |
|---|---|---|---|
| first_url | Yes | The first business website URL, such as example.com. | |
| second_url | Yes | The second business website URL, such as competitor.com. |
Output Schema
| Name | Required | Description |
|---|---|---|
| first | Yes | |
| second | Yes | |
| winner | Yes | |
| score_gap | Yes | |
| full_scan_url | Yes |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds context that the tool performs public-site scans (network access) and clarifies the scope of comparison (readiness, not live rankings), which goes beyond the annotation hints.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two concise sentences, front-loaded with the core action and outcome. Every word earns its place, with no fluff or repetition of schema information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the output schema exists and annotations are strong, the description sufficiently covers the tool's purpose, scope, and limitations. It mentions the types of outputs (aggregate scores, evidence, signals, issues) without needing to detail return structure, and the exclusion clarifies edge cases.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema provides 100% coverage with clear descriptions and examples for both parameters. The description does not add additional parameter-level detail, so it meets the baseline for high schema coverage but does not exceed it.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function: running SEO/AEO readiness scans on two websites and comparing scores, evidence, signals, and issues. It distinguishes from siblings by focusing on comparison of two sites, and explicitly clarifies it is not rank or citation benchmarking.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context that this is for comparing two business websites' readiness, and includes an exclusion ('not observed rank or live citation benchmarking'). However, it does not explicitly name alternative tools (e.g., scan_visibility) or state when to choose this over them.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
scan_visibilityScan SEO/AEO Website ReadinessARead-onlyIdempotentInspect
Run a public-site SEO/AEO website-readiness scan for one business website. Returns aggregate readiness scores, selected technical and answer-quality evidence, site signals, and prioritized issues. This does not measure observed rankings, Search Console performance, or live AI mentions/citations.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | The business website URL to scan, such as example.com. |
Output Schema
| Name | Required | Description |
|---|---|---|
| url | Yes | |
| score | Yes | |
| summary | Yes | |
| audit_id | Yes | |
| aeo_score | Yes | |
| geo_score | Yes | |
| seo_score | Yes | |
| top_issues | Yes | |
| site_signals | No | |
| full_scan_url | Yes | |
| score_profile | Yes | |
| score_components | No | |
| measurement_scope | Yes |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds valuable behavioral context: it returns aggregate scores and evidence, and importantly clarifies what the scan does NOT measure, preventing misuse. No contradiction with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences: the first states the action and scope, the second lists outputs and limitations. Every sentence earns its place, no redundancy, and the key information is front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has a simple 1-parameter schema, rich annotations, and an output schema, the description sufficiently covers the purpose, output categories, and explicit non-scope items. No critical gaps for an agent to select and invoke the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% for the single 'url' parameter with a clear description. The tool description adds 'for one business website' but does not provide additional parameter-level details beyond the schema. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's verb 'Run' and resource 'public-site SEO/AEO website-readiness scan', and scopes it to 'one business website', distinguishing it from the sibling compare_visibility. It also lists what it returns (aggregate readiness scores, evidence, signals, issues), making the purpose unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives explicit exclusions: 'This does not measure observed rankings, Search Console performance, or live AI mentions/citations.' This tells the agent when not to use the tool. It also implies when to use it (single-site readiness scan), but it does not name alternative tools explicitly.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
visibility_audit_infoVisibility Audit InformationARead-onlyIdempotentInspect
Explain the MeSquared SEO/AEO website-readiness methodology, its measurement boundaries, and how to use the available scan tools.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
| tools | Yes | |
| product | Yes | |
| measures | Yes | |
| free_scan_url | Yes | |
| does_not_measure | Yes | |
| measurement_layers | Yes |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare this as read-only, idempotent, open-world, and non-destructive. The description adds behavioral context by specifying that it explains methodology and boundaries, not performing any scans itself. This goes beyond the annotations but doesn't provide details on response format, but the output schema covers that.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, well-structured sentence that front-loads the purpose ('Explain the MeSquared SEO/AEO website-readiness methodology') and efficiently lists the additional scope. No words are wasted.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For an informational tool with no parameters and an output schema, the description is fully complete: it states the methodology, measurement boundaries, and usage guidance for scan tools. The output schema handles return format specifics, and the simplicity of the tool requires no further detail.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so the baseline is 4. The description adds no parameter-specific semantics because none exist, and the schema is already complete with no properties.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses the specific verb 'Explain' and clearly identifies the resource: the MeSquared SEO/AEO website-readiness methodology, its measurement boundaries, and how to use scan tools. This strongly differentiates it from sibling tools compare_visibility and scan_visibility, which actually perform scans/comparisons rather than explaining the methodology.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description states it explains how to use the available scan tools, which implies this tool should be consulted before performing scans. It provides clear context for when to use it, though it does not explicitly mention when not to use it or name the sibling tools as alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
2 tool updates
- Changed
compare_visibility4 fields changed- added
Input schema / properties / first_url / maxLengthAdded value: +2048 - added
Input schema / properties / first_url / minLengthAdded value: +1 - added
Input schema / properties / second_url / maxLengthAdded value: +2048 - added
Input schema / properties / second_url / minLengthAdded value: +1
- Changed
scan_visibility2 fields changed- added
Input schema / properties / url / maxLengthAdded value: +2048 - added
Input schema / properties / url / minLengthAdded value: +1
3 tool updates
- Changed
compare_visibility10 fields changed- added
Output schema / properties / first / properties / measurement_scopeAdded value: +{ + "additionalProperties": false, + "properties": { + "notes": { + "items": { + "type": "string" + }, + "type": "array" + }, + "observed_aeo": { + "const": "not_measured", + "type": "string" + }, + "observed_seo": { + "const": "not_measured", + "type": "string" + }, + "readiness": { + "const": "measured", + "type": "string" + } + }, + "required": [ + "readiness", + "observed_seo", + "observed_aeo", + "notes" + ], + "type": "object" +} - added
Output schema / properties / first / properties / score_componentsAdded value: +{ + "additionalProperties": false, + "properties": { + "ai_crawler_access": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "answer_block": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "content_modularity": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "eeat": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "experience": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "factual_density": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "format_diversity": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "freshness": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "heading_hierarchy": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "render_accessibility": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "schema_coverage": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "schema_quality": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "schema_stack": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "schema_validation": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "semantic_structure": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "snippet_control": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "technical_foundation": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "title_alignment": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + } + }, + "required": [ + "technical_foundation", + "experience", + "freshness", + "schema_quality", + "schema_stack", + "eeat", + "answer_block", + "format_diversity", + "factual_density", + "content_modularity", + "ai_crawler_access", + "snippet_control", + "render_accessibility", + "schema_coverage", + "schema_validation", + "heading_hierarchy", + "semantic_structure", + "title_alignment" + ], + "type": "object" +} - added
Output schema / properties / first / properties / score_profileAdded value: +{ + "anyOf": [ + { + "additionalProperties": false, + "properties": { + "id": { + "type": "string" + }, + "version": { + "type": "string" + } + }, + "required": [ + "id", + "version" + ], + "type": "object" + }, + { + "type": "null" + } + ] +} - added
Output schema / properties / first / properties / site_signalsAdded value: +{ + "additionalProperties": false, + "properties": { + "blocked_ai_crawlers": { + "items": { + "type": "string" + }, + "type": "array" + }, + "llms_txt_available": { + "type": "boolean" + }, + "pages_analyzed": { + "maximum": 9007199254740991, + "minimum": 0, + "type": "integer" + }, + "rendered_pages_analyzed": { + "maximum": 9007199254740991, + "minimum": 0, + "type": "integer" + }, + "robots_available": { + "type": "boolean" + }, + "schema_types": { + "items": { + "type": "string" + }, + "type": "array" + }, + "sitemap_available": { + "type": "boolean" + } + }, + "required": [ + "pages_analyzed", + "rendered_pages_analyzed", + "robots_available", + "sitemap_available", + "llms_txt_available", + "blocked_ai_crawlers", + "schema_types" + ], + "type": "object" +} - changed
Output schema / properties / first / requiredPrevious value: -[ - "url", - "score", - "seo_score", - "aeo_score", - "geo_score", - "summary", - "top_issues", - "audit_id" -]New value: +[ + "url", + "score", + "seo_score", + "aeo_score", + "geo_score", + "summary", + "top_issues", + "audit_id", + "score_profile", + "measurement_scope" +] - added
Output schema / properties / second / properties / measurement_scopeAdded value: +{ + "additionalProperties": false, + "properties": { + "notes": { + "items": { + "type": "string" + }, + "type": "array" + }, + "observed_aeo": { + "const": "not_measured", + "type": "string" + }, + "observed_seo": { + "const": "not_measured", + "type": "string" + }, + "readiness": { + "const": "measured", + "type": "string" + } + }, + "required": [ + "readiness", + "observed_seo", + "observed_aeo", + "notes" + ], + "type": "object" +} - added
Output schema / properties / second / properties / score_componentsAdded value: +{ + "additionalProperties": false, + "properties": { + "ai_crawler_access": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "answer_block": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "content_modularity": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "eeat": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "experience": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "factual_density": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "format_diversity": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "freshness": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "heading_hierarchy": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "render_accessibility": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "schema_coverage": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "schema_quality": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "schema_stack": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "schema_validation": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "semantic_structure": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "snippet_control": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "technical_foundation": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "title_alignment": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + } + }, + "required": [ + "technical_foundation", + "experience", + "freshness", + "schema_quality", + "schema_stack", + "eeat", + "answer_block", + "format_diversity", + "factual_density", + "content_modularity", + "ai_crawler_access", + "snippet_control", + "render_accessibility", + "schema_coverage", + "schema_validation", + "heading_hierarchy", + "semantic_structure", + "title_alignment" + ], + "type": "object" +} - added
Output schema / properties / second / properties / score_profileAdded value: +{ + "anyOf": [ + { + "additionalProperties": false, + "properties": { + "id": { + "type": "string" + }, + "version": { + "type": "string" + } + }, + "required": [ + "id", + "version" + ], + "type": "object" + }, + { + "type": "null" + } + ] +} - added
Output schema / properties / second / properties / site_signalsAdded value: +{ + "additionalProperties": false, + "properties": { + "blocked_ai_crawlers": { + "items": { + "type": "string" + }, + "type": "array" + }, + "llms_txt_available": { + "type": "boolean" + }, + "pages_analyzed": { + "maximum": 9007199254740991, + "minimum": 0, + "type": "integer" + }, + "rendered_pages_analyzed": { + "maximum": 9007199254740991, + "minimum": 0, + "type": "integer" + }, + "robots_available": { + "type": "boolean" + }, + "schema_types": { + "items": { + "type": "string" + }, + "type": "array" + }, + "sitemap_available": { + "type": "boolean" + } + }, + "required": [ + "pages_analyzed", + "rendered_pages_analyzed", + "robots_available", + "sitemap_available", + "llms_txt_available", + "blocked_ai_crawlers", + "schema_types" + ], + "type": "object" +} - changed
Output schema / properties / second / requiredPrevious value: -[ - "url", - "score", - "seo_score", - "aeo_score", - "geo_score", - "summary", - "top_issues", - "audit_id" -]New value: +[ + "url", + "score", + "seo_score", + "aeo_score", + "geo_score", + "summary", + "top_issues", + "audit_id", + "score_profile", + "measurement_scope" +]
- Changed
scan_visibility5 fields changed- added
Output schema / properties / measurement_scopeAdded value: +{ + "additionalProperties": false, + "properties": { + "notes": { + "items": { + "type": "string" + }, + "type": "array" + }, + "observed_aeo": { + "const": "not_measured", + "type": "string" + }, + "observed_seo": { + "const": "not_measured", + "type": "string" + }, + "readiness": { + "const": "measured", + "type": "string" + } + }, + "required": [ + "readiness", + "observed_seo", + "observed_aeo", + "notes" + ], + "type": "object" +} - added
Output schema / properties / score_componentsAdded value: +{ + "additionalProperties": false, + "properties": { + "ai_crawler_access": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "answer_block": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "content_modularity": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "eeat": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "experience": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "factual_density": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "format_diversity": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "freshness": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "heading_hierarchy": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "render_accessibility": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "schema_coverage": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "schema_quality": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "schema_stack": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "schema_validation": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "semantic_structure": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "snippet_control": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "technical_foundation": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + }, + "title_alignment": { + "anyOf": [ + { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + { + "type": "null" + } + ] + } + }, + "required": [ + "technical_foundation", + "experience", + "freshness", + "schema_quality", + "schema_stack", + "eeat", + "answer_block", + "format_diversity", + "factual_density", + "content_modularity", + "ai_crawler_access", + "snippet_control", + "render_accessibility", + "schema_coverage", + "schema_validation", + "heading_hierarchy", + "semantic_structure", + "title_alignment" + ], + "type": "object" +} - added
Output schema / properties / score_profileAdded value: +{ + "anyOf": [ + { + "additionalProperties": false, + "properties": { + "id": { + "type": "string" + }, + "version": { + "type": "string" + } + }, + "required": [ + "id", + "version" + ], + "type": "object" + }, + { + "type": "null" + } + ] +} - added
Output schema / properties / site_signalsAdded value: +{ + "additionalProperties": false, + "properties": { + "blocked_ai_crawlers": { + "items": { + "type": "string" + }, + "type": "array" + }, + "llms_txt_available": { + "type": "boolean" + }, + "pages_analyzed": { + "maximum": 9007199254740991, + "minimum": 0, + "type": "integer" + }, + "rendered_pages_analyzed": { + "maximum": 9007199254740991, + "minimum": 0, + "type": "integer" + }, + "robots_available": { + "type": "boolean" + }, + "schema_types": { + "items": { + "type": "string" + }, + "type": "array" + }, + "sitemap_available": { + "type": "boolean" + } + }, + "required": [ + "pages_analyzed", + "rendered_pages_analyzed", + "robots_available", + "sitemap_available", + "llms_txt_available", + "blocked_ai_crawlers", + "schema_types" + ], + "type": "object" +} - changed
Output schema / requiredPrevious value: -[ - "url", - "score", - "seo_score", - "aeo_score", - "geo_score", - "top_issues", - "summary", - "full_scan_url", - "audit_id" -]New value: +[ + "url", + "score", + "seo_score", + "aeo_score", + "geo_score", + "top_issues", + "summary", + "full_scan_url", + "audit_id", + "score_profile", + "measurement_scope" +]
- Changed
visibility_audit_info2 fields changed- added
Output schema / properties / measurement_layersAdded value: +{ + "items": { + "additionalProperties": false, + "properties": { + "description": { + "type": "string" + }, + "name": { + "type": "string" + }, + "status": { + "enum": [ + "measured", + "not_measured" + ], + "type": "string" + } + }, + "required": [ + "name", + "status", + "description" + ], + "type": "object" + }, + "type": "array" +} - changed
Output schema / requiredPrevious value: -[ - "product", - "free_scan_url", - "measures", - "does_not_measure", - "tools" -]New value: +[ + "product", + "free_scan_url", + "measures", + "does_not_measure", + "measurement_layers", + "tools" +]
3 tool updates
- Changed
compare_visibility3 fields changed- changed
Input schema / properties / first_url / descriptionPrevious value: -"The first business website URL."New value: +"The first business website URL, such as example.com." - changed
Input schema / properties / second_url / descriptionPrevious value: -"The second business website URL."New value: +"The second business website URL, such as competitor.com." - changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": false, + "properties": { + "first": { + "additionalProperties": false, + "properties": { + "aeo_score": { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + "audit_id": { + "type": "string" + }, + "geo_score": { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + "score": { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + "seo_score": { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + "summary": { + "type": "string" + }, + "top_issues": { + "items": { + "additionalProperties": false, + "properties": { + "category": { + "type": "string" + }, + "description": { + "type": "string" + }, + "severity": { + "enum": [ + "critical", + "warning", + "info" + ], + "type": "string" + }, + "title": { + "type": "string" + } + }, + "required": [ + "title", + "severity", + "category", + "description" + ], + "type": "object" + }, + "type": "array" + }, + "url": { + "type": "string" + } + }, + "required": [ + "url", + "score", + "seo_score", + "aeo_score", + "geo_score", + "summary", + "top_issues", + "audit_id" + ], + "type": "object" + }, + "full_scan_url": { + "type": "string" + }, + "score_gap": { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + "second": { + "additionalProperties": false, + "properties": { + "aeo_score": { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + "audit_id": { + "type": "string" + }, + "geo_score": { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + "score": { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + "seo_score": { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + "summary": { + "type": "string" + }, + "top_issues": { + "items": { + "additionalProperties": false, + "properties": { + "category": { + "type": "string" + }, + "description": { + "type": "string" + }, + "severity": { + "enum": [ + "critical", + "warning", + "info" + ], + "type": "string" + }, + "title": { + "type": "string" + } + }, + "required": [ + "title", + "severity", + "category", + "description" + ], + "type": "object" + }, + "type": "array" + }, + "url": { + "type": "string" + } + }, + "required": [ + "url", + "score", + "seo_score", + "aeo_score", + "geo_score", + "summary", + "top_issues", + "audit_id" + ], + "type": "object" + }, + "winner": { + "enum": [ + "first_url", + "second_url", + "tie" + ], + "type": "string" + } + }, + "required": [ + "winner", + "score_gap", + "first", + "second", + "full_scan_url" + ], + "type": "object" +}
- Changed
scan_visibility2 fields changed- changed
Input schema / properties / url / descriptionPrevious value: -"The business website URL to scan."New value: +"The business website URL to scan, such as example.com." - changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": false, + "properties": { + "aeo_score": { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + "audit_id": { + "type": "string" + }, + "full_scan_url": { + "type": "string" + }, + "geo_score": { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + "score": { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + "seo_score": { + "maximum": 100, + "minimum": 0, + "type": "number" + }, + "summary": { + "type": "string" + }, + "top_issues": { + "items": { + "additionalProperties": false, + "properties": { + "category": { + "type": "string" + }, + "description": { + "type": "string" + }, + "severity": { + "enum": [ + "critical", + "warning", + "info" + ], + "type": "string" + }, + "title": { + "type": "string" + } + }, + "required": [ + "title", + "severity", + "category", + "description" + ], + "type": "object" + }, + "type": "array" + }, + "url": { + "type": "string" + } + }, + "required": [ + "url", + "score", + "seo_score", + "aeo_score", + "geo_score", + "top_issues", + "summary", + "full_scan_url", + "audit_id" + ], + "type": "object" +}
- Added
visibility_audit_info
2 tool updates
- First observed
compare_visibility - First observed
scan_visibility
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
Scan any public site for AI-agent visibility; get scored findings, a machine-readable fix pack, and
Scan any website for AI readiness — 100-point score across 6 AEO categories in seconds.
AI visibility reports, competitor insights, readiness audits, and GEO content workflows.
Scan websites for AI visibility and marketing health with interactive dashboard.
Related MCP Servers
- AlicenseNot gradedqualityAmaintenanceAudits public websites for AI crawler access, public technical signals, and deployment readiness. Includes a focused path to the full readiness report when deeper remediation guidance is needed.MIT

SitePulsar MCP Serverofficial
AlicenseNot gradedqualityDmaintenanceMeasures and improves how findable, readable, and usable a website is to AI answer engines and autonomous AI agents through hosted AEO audit tools.MIT- AlicenseAqualityBmaintenanceRelease gate agents call before they tell users a public website is ready to ship. Scans public websites across security, SEO, accessibility, legal compliance, and sustainability.9MIT
- AlicenseAqualityDmaintenanceEnables users to scan any website for AI search visibility, producing AEO, GEO, agent readiness, and mention-readiness scores along with AI identity and business profile insights. Paid tools extend this to competitive comparisons, detailed audits, and generated fixes.41MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
Each tool has a clearly distinct purpose: scan_visibility handles a single site, compare_visibility handles two sites, and visibility_audit_info provides explanatory context. There is no functional overlap or ambiguity.
The two primary tools follow a consistent verb_noun pattern (compare_visibility, scan_visibility). The third tool, visibility_audit_info, uses a noun-based name, which is a minor deviation but still clearly readable and thematically aligned.
With only 3 tools, the server is minimally scoped but appropriately covers its core functionality: single scan, comparison, and informational support. This is on the low end but well-suited for a focused visibility assessment service.
The tool set covers the primary operations needed for this domain: scanning one site, scanning and comparing two sites, and understanding the methodology. No critical gaps exist for a stateless scanning service, though historical scans or bulk operations are absent.