Skip to main content
Glama
UptimeScout MCP server

UptimeScout MCP server

Official
by jsonscraper

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
UPTIMESCOUT_LICENSE_KEYYesLicense key for the UptimeScout MCP server.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Use regional availability observations. Check stale and observed_at. Signals are not confirmed outages. Connect through Evelode OAuth or a license key. Never ask for keys in chat. Renew licenses at https://evelode.com/licenses/ and refresh the account connection if needed.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
uptimescout_servicesC

Search the service catalog and get service availability observations.

uptimescout_statusC

Get a service status with observation time and explicit freshness.

uptimescout_statusesC

Get a batch of service statuses.

uptimescout_summaryC

Summarize reported availability across the catalog or selected services.

uptimescout_historyB

Read regional history: weighted time-slot aggregates at 3-minute, 5-minute, hourly and daily resolutions. Saved legacy aggregates keep their declared coarser resolution. Inspect resolution_seconds, samples, counts and effective_start; missing intervals are unknown.

uptimescout_statsB

Calculate weighted observation ratios from sample counts, including weighted time-slot aggregates. Not measured uptime. Inspect effective_start for UTC-slot alignment.

uptimescout_incidentsC

List services with fresh elevated disruption signals; not confirmed provider incidents.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.1/5.0

Scored across 7 tools

Disambiguation4/5

The tools are mostly distinct: single status vs. batch status, catalog search, history, stats, summary, and incidents have different targeting. Some overlap remains between services/status and summary/stats because they all expose availability-related views, though the descriptions provide enough distinction.

Naming Consistency4/5

All tool names share the same uptimescout_ prefix and use lowercase snake_case, which is predictable. The names are noun-based rather than action-based, and status/statuses are close but still intentionally distinguishable.

Tool Count5/5

Seven tools is a well-scoped size for a read-only observability server covering catalog lookup, status retrieval, history, stats, summaries, and incidents. Each tool appears to earn its place without excessive surface area.

Completeness4/5

The toolset covers the core read-only lifecycle for uptime monitoring: service catalog, single and batch status, summaries, historical aggregates, statistics, and incident signals. Minor gaps may exist around additional catalog metadata or richer incident detail, but agents can work around them.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues