Webby MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PUBMED_EMAIL | Yes | Your email address (required by NCBI) | |
| PUBMED_API_KEY | No | Optional API key for higher rate limits |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| validate_performance_pagespeedA | Analyze website performance using Google PageSpeed Insights. Returns Core Web Vitals and performance scores. Free API with 25K requests/day. |
| validate_performance_gtmetrixC | Analyze website performance using GTmetrix. Requires API key (free tier available). |
| validate_performance_webpagetestA | Analyze website performance using WebPageTest via browser automation. Free 300 tests/month. Returns test ID immediately or waits for full results. |
| validate_accessibility_waveC | Analyze website accessibility using WAVE. Tests WCAG compliance, errors, and contrast issues. Requires API key. |
| validate_accessibility_axeB | Analyze website accessibility using Axe. Free, open-source, finds ~57% of WCAG issues with zero false positives. |
| validate_security_mozilla_observatoryB | Analyze HTTP security headers using Mozilla Observatory. Tests CSP, HSTS, etc. Free API, 1 scan per minute per domain. |
| validate_security_ssl_labsA | Analyze SSL/TLS configuration using SSL Labs. Comprehensive certificate and protocol analysis. Long-running (may take minutes). |
| validate_all_performanceB | Run all available performance tests (PageSpeed Insights + optionally WebPageTest + optionally GTmetrix). |
| validate_all_accessibilityC | Run all accessibility tests (Axe + optionally WAVE if API key provided). |
| validate_all_seoC | Run SEO analysis using PageSpeed Insights (includes Lighthouse SEO). |
| validate_all_securityB | Run all security tests (Mozilla Observatory + SSL Labs). |
| validate_comprehensiveC | Run comprehensive validation across all categories (performance, accessibility, SEO, security). |
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 12 tools
The tools have clear distinctions between categories (accessibility, performance, security, SEO) and specific tool implementations (e.g., Axe vs. WAVE), but there is significant overlap in the 'validate_all_' and 'validate_comprehensive' tools, which aggregate other tools and could cause confusion about when to use individual vs. bundled validations. The descriptions help clarify, but the redundancy creates ambiguity in tool selection.
All tool names follow a consistent 'validate_' prefix with descriptive suffixes (e.g., 'accessibility_axe', 'performance_pagespeed'), using snake_case uniformly. This predictable pattern makes it easy for agents to understand the purpose and category of each tool at a glance, with no deviations in naming style.
With 12 tools, the count is reasonable for a web validation server covering multiple domains (accessibility, performance, security, SEO), though it feels slightly heavy due to the inclusion of both individual and aggregated tools. The scope is well-defined, and each tool serves a specific purpose, but the aggregation tools add some bulk that might be streamlined.
The tool set provides comprehensive coverage for web validation, including multiple tools per category (e.g., three performance tools, two accessibility tools) and aggregated options for broader testing. There are no obvious gaps; agents can perform detailed or holistic validations across all key web quality aspects without dead ends.