passiv-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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| html_to_markdownA | Convert HTML to clean Markdown or plain text. Same engine as the Clean Copy browser extension. Max 50 KB of HTML per call. |
| compliance_scanA | Scan a website for 9 EU compliance essentials: privacy policy, terms, cookie consent, imprint, accessibility statement, DPA, security headers, meta tags, hreflang. Returns a score out of 100 plus pass/fail per check with fix tips. |
| profile_pageB | Profile a web page: title/meta description, Open Graph tags, JSON-LD structured data, heading structure, image alt coverage and security headers, with a weighted score and letter grade. |
| check_security_headersA | Check a URL for security headers: Content-Security-Policy, HSTS, X-Frame-Options, X-Content-Type-Options and Referrer-Policy. Reports which are present/missing. |
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 4 tools
The four tools have distinct primary purposes: security headers, HTML conversion, compliance scanning, and page profiling. However, there is some overlap: both compliance_scan and profile_page include security headers in their checks, and check_security_headers is a standalone tool for the same. This minor redundancy could cause confusion about which tool to use for security header information.
All tool names follow a consistent verb_noun or noun_noun pattern (check_security_headers, html_to_markdown, compliance_scan, profile_page). They are clear, descriptive, and use snake_case uniformly with no mixing of conventions.
Four tools is a reasonable number for a focused web analysis and conversion server. It covers distinct functionalities without bloat. Slightly on the lower side but adequate for the apparent scope.
The server covers several web page analysis and conversion tasks, but notable gaps exist: no tool for analyzing performance metrics, broken links, or SEO beyond compliance and profiling. More importantly, check_security_headers is subsumed by compliance_scan and profile_page, suggesting incomplete decomposition or redundant surface. However, for the listed core functionalities, the surface is complete.