Is the Kapoost Human MCP server down?

mcp-registry/io.github.kapoost/humanmcp · v0.2.0-dev

Also listed as glama/kapoost/humanmcp

healthy
Last checked 2026-10-19 10:35 UTC · handshake 370ms

As of 2026-10-19 10:35 UTC, the Kapoost Human MCP server is up with a Glimind reliability score of 89/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 8 minutes.

uptime (30d checks)
99.9%
checks observed
3,790
outages (90d)
5
tools
43

Personal MCP server for humans who create. Proof of authorship, license control.

Install Kapoost Human MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http kapoost-human-mcp-server https://kapoost.humanmcp.net/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "kapoost-human-mcp-server": {
      "type": "http",
      "url": "https://kapoost.humanmcp.net/mcp"
    }
  }
}

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

Agent-readiness: D (63/100)

D (63/100): 0 error(s), 5 warning(s) across 43 tool(s); ~4,547 tokens of tool definitions.
Scores higher than 1% of 15,348 MCP servers Glimind has audited.
Its tool list costs an agent ~4,547 tokens per session — more than 60% of servers.
63 → 63 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions30
Safety hints11
Token cost75
Client compatibility70
Protocol100
Reliability85
Stability100

What to fix (6)

43 of 43 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: about_humanmcp, ask_human, bootstrap_session, delete_skill, fetch_answer and 38 more

43 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.

Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →

79 parameter(s) across 37 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: ask_human, bootstrap_session, delete_skill, fetch_answer, fetch_narada_result and 32 more

5 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: delete_skill, mysloodsiewnia_write, run_narada, submit_answer, upsert_skill

Handshake + tools/list takes ~1,817 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: 28 corrected tool definitions

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

delete_skill 1 change
{
  "name": "delete_skill",
  "description": "Delete a skill by slug. Owner-only: requires Authorization: Bearer <token>.",
  "inputSchema": {
    "type": "object",
    "required": [
      "slug"
    ],
    "properties": {
      "slug": {
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": true,
    "idempotentHint": true
  }
}
fetch_answer 1 change
{
  "name": "fetch_answer",
  "description": "Poll for an answer to an ask_human question. Marks the question as fetched the first time an answer is returned. Rate-limited 30/hr/IP.",
  "inputSchema": {
    "type": "object",
    "required": [
      "id"
    ],
    "properties": {
      "id": {
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
fetch_narada_result 1 change
{
  "name": "fetch_narada_result",
  "description": "Poll a narada job by ID. Statuses: pending, running, done, failed. When done, returns all persona voices.",
  "inputSchema": {
    "type": "object",
    "required": [
      "id"
    ],
    "properties": {
      "id": {
        "type": "string"
      }
    }
  },
  "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.kapoost/humanmcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.kapoost/humanmcp"}) 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.kapoost%2Fhumanmcp.svg)](https://glimind.com/server/mcp-registry%2Fio.github.kapoost%2Fhumanmcp?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.kapoost%2Fhumanmcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.kapoost%2Fhumanmcp.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.kapoost%2Fhumanmcp.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.kapoost%2Fhumanmcp?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:88ccf06db9753824…, first seen 2026-10-17, included at leaf 4640 of 26,207. Version history · verify what your client received.

Tools (43)

Compare: most reliable knowledge servers · most reliable communication servers · most reliable other servers · most reliable ml servers · most reliable data 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 Kapoost Human MCP server down right now?

As of 2026-10-19 10:35 UTC, the Kapoost Human MCP server is up with a Glimind reliability score of 89/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 8 minutes.

How many tools does Kapoost Human MCP server provide?

Kapoost Human MCP server advertises 43 tools, including about_humanmcp, ask_human, bootstrap_session, delete_skill, fetch_answer.

How do I install Kapoost Human MCP server?

Point your MCP client at this streamable-http endpoint: https://kapoost.humanmcp.net/mcp

Is the Kapoost Human MCP server safe to connect to an AI agent?

Glimind scanned all 43 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 Kapoost Human 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.

Feedback
Help us improve