Skip to main content
Glama
APVentureEngine

vendor-status

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
VENDOR_STATUS_MCP_TTLNoCache time-to-live in seconds for status data files. Controls how often the server revalidates cached copies.
VENDOR_STATUS_MCP_CACHENoOverride the cache directory used to store downloaded Vendor Status Watch data. Defaults to ~/.cache/vendor-status-mcp.

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": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
find_vendorA

Resolve a SaaS/cloud vendor by name, slug or status-page domain to its entry in the 1,100+ vendor status-page map: status page URL, platform (Statuspage, Instatus, status.io, Better Stack, ...), whether a machine-readable feed exists, and its state in the newest poll. Use this first when unsure of the exact vendor slug.

vendor_statusA

Current state of one vendor from the newest daily poll: ok / degraded / partial / major / maintenance / unknown, the vendor's own status line, open incident count and the poll timestamp. Says plainly that it is a daily poll, not a live probe.

vendors_down_nowA

Every vendor that was NOT fully operational in the newest poll, worst first (major, partial, degraded, then maintenance), with counts by state across all polled vendors. Use for 'which SaaS vendors have incidents right now'.

vendor_incidentsA

One vendor's incident history as its status page posted it: title, state, impact, start/resolve timestamps, latest update text and the incident URL, newest first. Histories go back weeks to years depending on what the vendor's page exposes.

vendor_resolution_timesA

How long one vendor's incidents take to be declared resolved: median, 90th percentile, count over 24h and the longest on record, computed from the vendor's own posted start and resolve timestamps (maintenance and inferred resolutions excluded). Not an uptime or SLA number.

status_feed_urlsA

The machine-readable endpoints for one vendor's status page — summary JSON, incidents JSON, RSS and Atom where the platform provides them — so an agent or a script can poll the vendor directly without a key. Also returns this dataset's normalized history JSON for the vendor.

dataset_statusA

Coverage and freshness of the underlying dataset: vendors mapped, how many have machine-readable feeds, incidents on record, incidents in the last 30 days, platform breakdown, poll cadence, license and bulk downloads.

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

Disambiguation5/5

Each tool targets a distinct concern: single-vendor current status, vendor lookup, aggregate outages, incident history, resolution metrics, feed endpoints, and dataset metadata. Even the incident-related tools are clearly separated by current state vs. historical detail.

Naming Consistency4/5

Most tools follow a consistent snake_case noun-phrase pattern with a vendor_ prefix, making the set easy to scan. find_vendor is a verb-led deviation)Skip, and vendors_down_now uses a different structure, but these are minor and do not undermine predictability.

Tool Count5/5

Seven tools is well-scoped for a read-only vendor status dataset. Each tool covers a distinct part of the workflow without unnecessary duplication or bloat.

Completeness4/5

The set covers lookup, current status, affected vendors, incident history, resolution statistics, direct feed access, and dataset health. A bulk 'all vendor statuses' or cross-vendor incident search is missing, but core agent workflows are well supported.

Maintenance

ActivityMaintained
ResponsivenessNo issues