Skip to main content
Glama
sikulovi-s-r-o

seoradar-mcp

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SEORADAR_API_KEYYesYour `sr_live_` API key from seoradar.cz
SEORADAR_API_URLNoAPI base URL (override for staging)https://seoradar.cz/api/v1

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
seo_auditA

Run a comprehensive SEO audit on any URL. Returns overall score (0-100), category scores, and an AI summary. Cached results return instantly; new URLs take 10-30s (polling handled automatically). Use get_audit_results with the returned hash for the full per-check breakdown.

get_audit_resultsA

Get the full detailed SEO audit report by hash: every check with pass/warn/fail status, messages, recommendations, and tips.

check_api_usageA

Check your SEO Radar API quota — tier, daily limit, used today, and remaining count.

list_monitored_urlsA

List all URLs you have under SEO monitoring, with each one's latest status and score.

add_monitored_urlA

Add a URL to SEO monitoring. It will be re-audited on a schedule and you get alerts on regressions.

remove_monitored_urlA

Remove a URL from SEO monitoring by its id.

get_monitoring_statusA

Get the latest monitoring status and score for one monitored URL by its id.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.3/5.0

Scored across 7 tools

Disambiguation5/5

All tools have clearly distinct purposes: seo_audit triggers an audit and returns a summary, while get_audit_results fetches a detailed report by hash; the description explicitly directs agents to use both together. Monitoring tools (list/add/remove/get status) are cleanly separated by action and scope, and check_api_usage stands alone.

Naming Consistency4/5

Most tools follow a consistent verb_noun pattern (check_api_usage, get_audit_results, list_monitored_urls, add_monitored_url, remove_monitored_url, get_monitoring_status). However, seo_audit breaks the pattern as a noun phrase rather than a verb_noun construction, creating a minor inconsistency.

Tool Count5/5

With 7 tools, the set is well-scoped for an SEO audit and monitoring service. Each tool covers a distinct core operation with no redundancy or bloat, making the count appropriate for the domain.

Completeness4/5

The tool set covers the core lifecycle for audits (run, retrieve details) and monitoring (add, list, get status, remove), plus API quota checking. Minor gaps like updating monitoring settings or listing historical audits exist, but agents can work around them without major failures.

Maintenance

ActivityInactive
ResponsivenessNo issues