Website Intelligence MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_titleC | Analyze the title tag of a webpage |
| analyze_metaC | Analyze the meta description of a webpage |
| analyze_headingsC | Analyze the heading structure of a webpage |
| analyze_imagesC | Analyze images and their alt attributes on a webpage |
| analyze_linksC | Analyze the links on a webpage |
| analyze_canonicalC | Analyze the canonical URL of a webpage |
| analyze_robotsC | Analyze the robots meta directive of a webpage |
| analyze_open_graphC | Analyze Open Graph metadata of a webpage |
| analyze_schemaC | Validate JSON-LD schema objects of a webpage and count valid and invalid schemas |
| analyze_viewportC | Analyze the viewport meta tag of a webpage |
| analyze_langC | Analyze the HTML lang attribute of a webpage |
| analyze_faviconC | Analyze the favicon of a webpage |
| analyze_hreflangC | Analyze hreflang declarations of a webpage |
| analyze_charsetC | Analyze the character encoding of a webpage |
| analyze_sslC | Analyze whether a webpage uses HTTPS |
| analyze_sitemapC | Analyze the sitemap availability of a webpage |
| analyze_robots_txtC | Analyze the robots.txt file of a webpage |
| analyze_performanceC | Analyze basic page performance metrics |
| analyze_securityC | Analyze basic HTTPS and security headers |
| analyze_socialC | Analyze Open Graph and Twitter Card metadata |
| analyze_mobileC | Analyze mobile viewport and responsive configuration |
| analyze_technologyC | Analyze basic technology and platform signals |
| analyze_accessibilityC | Analyze basic accessibility issues |
| analyze_contentC | Analyze basic content quality and structure |
| analyze_structured_dataB | Summarize JSON-LD structured data blocks of a webpage and flag empty or invalid blocks |
| analyze_technicalC | Analyze basic technical SEO configuration |
| analyze_websiteC | Run a complete website intelligence analysis |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 27 tools
Most tools target a distinct HTML element or file, but several pairs overlap significantly: analyze_open_graph vs analyze_social (social includes Open Graph), analyze_schema vs analyze_structured_data (both validate/summarize JSON-LD), analyze_ssl vs analyze_security (security includes HTTPS), and analyze_mobile vs analyze_viewport. Descriptions help clarify the boundaries, but an agent could still misselect when only a general audit is needed.
Every tool follows the same analyze_<noun> pattern with no deviations, making the set highly predictable. Verb choice and casing are uniform throughout.
At 27 tools, the server exceeds the 25-tool threshold for 'too many' and is roughly double the typical well-scoped range. Many granular analyzers (title, meta, headings, lang, charset, etc.) could reasonably be grouped, making the surface feel over-fragmented despite the aggregate analyze_website tool.
The set covers a wide SEO/intelligence surface: metadata, headings, images, links, canonical, robots, hreflang, schema, performance, security, accessibility, and an aggregate analysis tool. Minor gaps remain (e.g., redirects, broken-link crawling, backlink data), but core lifecycle coverage for website auditing is strong.