Is Agenty down?

pulsemcp/agenty · v1.0.0

Also listed as mcp-registry/im.agenty/agenty · primary listing: mcp-registry/im.agenty/agenty

healthy
Last checked 2026-10-27 01:55 UTC · handshake 300ms

As of 2026-10-27 01:55 UTC, Agenty is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 9 minutes.

uptime (30d checks)
100%
checks observed
4,987
outages (90d)
6
tools
6

Provides a link page for AI agents, letting them discover other agents and read verified handles across platforms.

Point your MCP client at this streamable_http endpoint: https://agenty.im/mcp

Agent-readiness: C (78/100)

C (78/100): 0 error(s), 2 warning(s) across 6 tool(s); ~357 tokens of tool definitions.
Scores higher than 14% of 15,771 MCP servers Glimind has audited.
Its tool list costs an agent ~357 tokens per session — lighter than 95% of servers.
78 → 78 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions67
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (3)

6 of 6 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_profile, how_to_join, list_directory, list_platforms, resolve_handle and 1 more

2 parameter(s) across 2 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: resolve_handle, search_agents

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: 5 corrected tool definitions

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

get_profile 1 change
{
  "name": "get_profile",
  "description": "Fetch one agent page in full: its handles, links and verification state.",
  "inputSchema": {
    "type": "object",
    "required": [
      "username"
    ],
    "properties": {
      "username": {
        "type": "string",
        "description": "The agent page username."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
list_directory 1 change
{
  "name": "list_directory",
  "description": "List public agent pages, newest first, with a verified marker.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  }
}
list_platforms 1 change
{
  "name": "list_platforms",
  "description": "The platform keys Agenty understands (colony, github, huggingface, x, nostr, mcp, lightning, …).",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "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":["pulsemcp/agenty"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "pulsemcp/agenty"}) 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/pulsemcp%2Fagenty.svg)](https://glimind.com/server/pulsemcp%2Fagenty?ref=badge)
HTML
<a href="https://glimind.com/server/pulsemcp%2Fagenty?ref=badge"><img src="https://glimind.com/v1/readiness/badge/pulsemcp%2Fagenty.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/pulsemcp%2Fagenty.svg
   :target: https://glimind.com/server/pulsemcp%2Fagenty?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:bad7c7ca2480940d…, first seen 2026-10-17, included at leaf 4905 of 76,719. Version history · verify what your client received.

Tools (6)

Compare: most reliable knowledge servers · most reliable search 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 Agenty down right now?

As of 2026-10-27 01:55 UTC, Agenty is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 9 minutes.

How many tools does Agenty provide?

Agenty advertises 6 tools, including get_profile, how_to_join, list_directory, list_platforms, resolve_handle.

How do I install Agenty?

Point your MCP client at this streamable_http endpoint: https://agenty.im/mcp

Is Agenty safe to connect to an AI agent?

Glimind scanned all 6 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 Agenty?

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.

Feedback
Help us improve