Agent Standings check

com.agentstandingsPublished by agentstandings.comOfficial publisherv0.1.0Updated Oct 29, 2026

Live status and 30-day reliability of public MCP servers, from independent hourly probes.

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Checks live status and 30-day reliability of public remote MCP servers, and lists daily standings ranked by uptime and latency.

What you can do
  • Check a public MCP server's live status, latency, tool count and schema changes by registry name, endpoint URL, host or short name
  • Read 30-day reliability figures built from independent hourly probes
  • List the latest daily standings of tracked MCP servers, ranked by 7-day uptime then p95 latency
When to use it
Use it before relying on a remote MCP server, to see whether it is up and whether its tool schemas changed recently, or to compare tracked servers by uptime and latency.
Requirements
Remote streamable HTTP endpoint at agentstandings.com; no authentication, environment variables or headers declared. Network access to the service is needed.
Before you install
Results are automated measurements of public endpoints and are explicitly not an endorsement; treat them as one signal rather than a guarantee of quality or availability.

Installation

In SourceWeft

  1. Open Agent Standings check in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.agentstandings%2Fcheck/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "agent-standings-check": {
      "type": "http",
      "url": "https://agentstandings.com/mcp"
    }
  }
}

Tools

2

check_tool

Check an MCP server

Live status and 30-day reliability of a public remote MCP server, from independent hourly probes. Pass the registry name (e.g. "com.example/server"), the endpoint URL or host, or the short server name. Returns status (up, auth required, degraded, down, error, blocked), latency, tool count, schema hash, uptime, incidents and tool-schema drift events.

Parametersnamerequired

standings

Daily standings

The latest daily standings of tracked MCP servers, ranked by 7-day uptime then p95 latency.

Parameterslimit

Version history

1
  1. v0.1.0LatestOct 29, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.