Skip to main content
Glama
oper-stack

@operstack/mcp

Official
by oper-stack

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
audit_siteA

Read a public site and score six areas out of ten: technical SEO, content and structure, AEO (whether an answer engine can quote it), GEO (whether AI systems can identify and use it), off-page trust, and conversion. Returns every failing and borderline check with what was actually found on the pages. Free public signals only: no account, no paid tool, nothing stored. Use it when someone asks why a site is not being cited, why AI assistants recommend competitors, or what to fix first.

check_llms_txtA

Read a site's /llms.txt, check it against the format (one H1 naming the site, a summary, sections of links) and follow its links to see whether each still leads to a page, a redirect or nothing. This file rots silently because no human ever opens it. Use it when someone asks whether their llms.txt is correct, why an assistant quotes the wrong pages, or before publishing a new one.

run_gatesA

Run the sixteen quality gates on a folder of Markdown or MDX content on this machine: cut titles, copied paragraphs, hollow sections, dead links, redirect chains, a stale agent index, figures with no source, and the agent surface. Returns the report. Use it before publishing, or when asked what is wrong with a content corpus. It needs a local path, not a URL, and it reads files without sending them anywhere.

compare_sitesA

Run the same six-area measurement on two to four public sites and return them side by side. Use it when someone asks why a competitor is being quoted instead of them, or wants to know where the gap actually is rather than guessing. Free public signals only.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 4 tools

Disambiguation4/5

Each tool has a fairly distinct purpose: single-site audit, multi-site comparison, llms.txt validation, and local content gates. However, compare_sites is essentially a multi-site extension of audit_site, and check_llms_txt overlaps with the AEO/GEO portion of audit_site, so an agent could occasionally waver between them despite the clarifying descriptions.

Naming Consistency5/5

All four tools follow a clean verb_noun snake_case pattern: compare_sites, audit_site, check_llms_txt, run_gates. The convention is predictable throughout with no style mixing.

Tool Count4/5

Four tools is a reasonable, well-scoped count for a site-measurement server, and each earns its place. It leans slightly thin, since there is no tool for remediation or reporting beyond the core diagnostics.

Completeness4/5

The surface covers the core diagnostic lifecycle: single-site audit, competitor comparison, a specific llms.txt check, and local corpus gates. Minor gaps remain—no historical tracking, export/reporting, or standalone robots/schema checks—but agents can work around these for the stated purpose.