Roster is listed as active in the registry but did not answer our last check.
Self-hosted participant resolution agent with an MCP server for agent workflows.
Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.
claude mcp add roster --transport http https://{roster_host}/mcp
{
"mcpServers": {
"roster": {
"url": "https://{roster_host}/mcp"
}
}
}
[mcp_servers.roster]
url = "https://{roster_host}/mcp"
{
"mcpServers": {
"roster": {
"url": "https://{roster_host}/mcp"
}
}
}
{
"mcpServers": {
"roster": {
"url": "https://{roster_host}/mcp"
}
}
}
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://{roster_host}/mcp | streamable-http | answering | 1 ms | 7 min ago |
MCP server for agent task workflows with phases, prompts, gates, and multi-agent coordination
MCP server for browser automation with AI agent
MCP server for the Codabench REST API — drives a full ML-benchmark participant workflow.
Go code coverage analysis tool with MCP server for AI-powered coverage workflows
Go code coverage analysis tool with MCP server for AI-powered coverage workflows
A standardized testing harness for MCP servers and agent workflows
MCP server for HaloPSA — clients, tickets, and PSA workflows via the HaloPSA REST API.
MCP server for HaloPSA — clients, tickets, and PSA workflows via the HaloPSA REST API.
Answers built from our own checks of this server.