Skip to main content
Glama
adsandcode

mcp-server-contentgate

by adsandcode

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
check_keywordsA

Verify that target keywords actually appear in a rendered page. Every term tied at the highest search volume must appear at least primary_min_hits times; every other term at least once. Matching is literal and case-insensitive: whitespace is never normalised, because 'web hosting' and 'webhosting' are different terms with different search volumes.

check_translationA

Compare a translation against its source document for structural drift: heading sequence, HTML tag sequence, table row count, internal link paths, price tokens, locale prefix on internal links, leftover source-script characters, introduced em dashes and emoji. This checks structure, not meaning: it cannot tell you a translation is good, only that it is no longer the same document.

check_internal_linksA

Check that a content page links to at least one commercial page from its body, and optionally that it states a concrete figure. Links inside excluded boilerplate do not count, because a site-wide call-to-action block would otherwise satisfy this on every page and the check would guard nothing.

check_claimsA

Scan copy for affirmative performance claims of the kind that get finance, gambling and health advertising rejected: guaranteed profit, stated win rates, promised returns. Sentences that exist to disclaim or prohibit those phrases are not flagged.

sitemap_lastmodA

Decide a sitemap lastmod date honestly. Hash the meaningful content of a page, compare it against the stored hash, and move the date only when the content genuinely changed. Stamping today's date on every URL every build teaches crawlers that the field carries no information.

content_hashA

Hash the meaningful content of a page, with volatile blocks and scripts removed. Use it to tell a real edit from a rebuild.

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 6 tools

Disambiguation5/5

Each tool targets a distinct content-quality dimension: keyword presence, translation structure, internal linking, advertising claims, sitemap lastmod dating, and hashing. Even the two hashing-related tools are cleanly separated as utility versus policy. No tool appears to duplicate another.

Naming Consistency3/5

Four tools follow a clear check_<object> pattern, but sitemap_lastmod and content_hash break the verb-first convention and read as nouns. The mixed style is still readable and predictable enough for moderate coherence.

Tool Count5/5

Six tools is well-scoped for a content-gate server, covering distinct compliance checks plus hashing support. Each tool earns its place, and the count is comfortably in the ideal range.

Completeness4/5

The tool surface covers the main content-gate checks and provides hashing support for honest lastmod decisions. Broader content QA checks like metadata validation or broken-link detection are absent, but those are outside the server's apparent specialization.