Skip to main content
Glama

FreeAPI.watch

Check status of public remote MCP servers

check_mcp_servers

Returns live status for the public no-auth remote MCP servers we monitor, measured with a real JSON-RPC initialize handshake every hour rather than a plain HTTP GET. Use this to pick an MCP server that currently works, or to diagnose whether a server you are connected to is down for everyone.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_mcp_servers"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the burden well by disclosing that checks are hourly, use a real JSON-RPC initialize handshake rather than a plain GET, and cover only public no-auth servers. It does not describe the exact response structure or limitations, but it provides meaningful operational context beyond the tool name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two tight sentences, front-loading what the tool returns and then explaining how to use it. Every sentence adds useful information with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple zero-parameter status-check tool with no output schema or annotations, the description covers the target population, measurement method, cadence, and intended use cases. The main remaining gap is that it does not sketch what the returned status looks like.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so the baseline is 4. The description appropriately spends no space explaining parameter semantics and focuses on scope and behavior instead.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: returns live status for public no-auth remote MCP servers. It also distinguishes this from generic HTTP status checks by specifying a real JSON-RPC initialize handshake, making the purpose clear against likely siblings such as check_api_status.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives two concrete use cases: picking an MCP server that currently works, and diagnosing whether a connected server is down for everyone. It does not explicitly state when not to use it or name an alternative tool, but the context is clear enough for selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources