Status Observer MCP

Related Servers

Alternatives to Status Observer MCP

No user-submitted related servers found.

Related Servers

mcp-rss-aggregator
Browser Automation Agent Orchestration
imprvhub
A
license
A
quality
A
maintenance
Model Context Protocol Server for aggregating RSS feeds in Claude Desktop
Updated 2 days ago (2026-09-27 03:27 UTC)
3
27
Mozilla Public 2.0
YouTube MCP
Entertainment & Media Agent Orchestration
tunde-alao
F
license
A
quality
D
maintenance
A Model Context Protocol server that enables Claude to interact with YouTube data and functionality through the Claude Desktop application.
Updated a year ago (2025-07-05 15:25 UTC)
1
11
-
Polymarket MCP Tool
Blockchain Finance Web3 & Decentralized Tech
fernandezpablo85
A
license
A
quality
D
maintenance
A Model Context Protocol server that enables interaction with Polymarket prediction markets through Claude Desktop.
Updated a year ago (2025-06-23 13:47 UTC)
3
1
MIT
MCP Python Server — API
API Testing Developer Tools Browser Automation
cdryampi
F
license
Not graded
quality
D
maintenance
A Python server implementing the Model Context Protocol that exposes tools for querying external APIs, compatible with Claude Desktop and ChatGPT Desktop.
Updated a year ago (2025-05-09 11:03 UTC)
-
CrewAI Enterprise MCP Serverofficial
Agent Orchestration Project Management
crewAIInc
F
license
B
quality
D
maintenance
A Model Context Protocol server that enables users to kickoff and monitor deployed CrewAI workflows through Claude Desktop.
Updated 2 years ago (2025-03-19 18:06 UTC)
2
59
-
@pawells/mcp-memory
PhillipAWells
-
license
Not graded
quality
Not graded
maintenance
Model Context Protocol server for semantic memory and knowledge management with Claude Code.
Updated 2 months ago (2026-07-23 00:03 UTC)
-

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.9/5.0

Scored 2026-09-28 06:30 across 1 tool

Disambiguation5/5

With only a single tool, there is no possibility of confusion or misselection between tools. The one tool's purpose is unambiguous.

Naming Consistency4/5

The lone tool 'status' is a simple, readable noun name. There is no naming pattern to violate, though it does not follow a verb_noun convention.

Tool Count3/5

A single tool for a status-checking service is thin but arguably sufficient since it is a read-only fetch. It covers many vendors under one operation, making the surface borderline minimal.

Completeness4/5

The tool covers a broad set of vendors' status APIs, fulfilling the core domain purpose. However, it lacks operations for filtering by vendor, incident history, or per-service detail, which are minor gaps.