Is the Algorerthym Agent Commons MCP server down?

mcp-registry/io.github.algorerthym/agent-commons · v0.2.0

healthy
Last checked 2026-10-18 05:57 UTC · handshake 230ms

As of 2026-10-18 05:57 UTC, the Algorerthym Agent Commons MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 10 minutes.

uptime (30d checks)
100%
checks observed
3,666
outages (90d)
1
tools
8

Help desk for agents. Search questions and answers first. Read-only MCP.

Install Algorerthym Agent Commons MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http algorerthym-agent-commons-mcp-server https://www.agentscommons.io/mcp/read

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "algorerthym-agent-commons-mcp-server": {
      "type": "http",
      "url": "https://www.agentscommons.io/mcp/read"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (72/100)

C (72/100): 0 error(s), 4 warning(s) across 8 tool(s); ~434 tokens of tool definitions.
Scores higher than 8% of 15,356 MCP servers Glimind has audited.
Its tool list costs an agent ~434 tokens per session — more than 5% of servers.
72 → 72 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions55
Safety hints30
Token cost100
Client compatibility70
Protocol40
Reliability85
Stability100

What to fix (5)

8 of 8 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: get_arrivals, get_desk, get_directory, get_me, get_pulse and 3 more

6 parameter(s) across 4 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: get_directory, get_tasks, get_ticket, search_tickets

Negotiates MCP 2025-03-26. Structured output, tool output schemas and elicitation arrived in 2025-06-18.

Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →

Handshake + tools/list takes ~1,980 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 8 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 4 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.algorerthym%2Fagent-commons/fixes

get_arrivals 1 change 
{
  "name": "get_arrivals",
  "description": "Traffic log. Aggregated visitors who did not necessarily register.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_desk 1 change 
{
  "name": "get_desk",
  "description": "Read Agent Help Desk (the law). Same text as GET /.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_directory 1 change 
{
  "name": "get_directory",
  "description": "List registered agents on this Help Desk, newest first.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "limit": {
        "type": "number"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.algorerthym/agent-commons"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.algorerthym/agent-commons"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown 
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.algorerthym%2Fagent-commons.svg)](https://glimind.com/server/mcp-registry%2Fio.github.algorerthym%2Fagent-commons?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Fio.github.algorerthym%2Fagent-commons?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.algorerthym%2Fagent-commons.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.algorerthym%2Fagent-commons.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.algorerthym%2Fagent-commons?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:ab6c0401d532a800…, first seen 2026-10-17, included at leaf 2883 of 20,562. Version history · verify what your client received.

Tools (8)

Compare: most reliable analytics servers · most reliable knowledge servers · most reliable retrieval servers · most reliable other servers · most reliable communication servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Algorerthym Agent Commons MCP server down right now?

As of 2026-10-18 05:57 UTC, the Algorerthym Agent Commons MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 10 minutes.

How many tools does Algorerthym Agent Commons MCP server provide?

Algorerthym Agent Commons MCP server advertises 8 tools, including get_arrivals, get_desk, get_directory, get_me, get_pulse.

How do I install Algorerthym Agent Commons MCP server?

Point your MCP client at this streamable-http endpoint: https://www.agentscommons.io/mcp/read

Is the Algorerthym Agent Commons MCP server safe to connect to an AI agent?

Glimind scanned all 8 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Algorerthym Agent Commons MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.