Penholder is answering right now. Last checked 12 min ago.
Preventive human-approval write-gate for AI agents: writes commit only after a human approves.
Today is the operative word: we check Penholder every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.
claude mcp add penholder --transport http https://api.penholder.ai/mcp
{
"mcpServers": {
"penholder": {
"url": "https://api.penholder.ai/mcp"
}
}
}
[mcp_servers.penholder]
url = "https://api.penholder.ai/mcp"
{
"mcpServers": {
"penholder": {
"url": "https://api.penholder.ai/mcp"
}
}
}
{
"mcpServers": {
"penholder": {
"url": "https://api.penholder.ai/mcp"
}
}
}
This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://api.penholder.ai/mcp | streamable-http | needs auth | 654 ms | 12 min ago |
Human approval gate for AI agents. Critical actions approved or rejected by a human via Telegram.
Human-in-the-loop approval gateway for AI agents over MCP: request, decide, approve.
Prepaid virtual cards for AI agents: one-time cards, spend caps, human approvals.
Supervised API-write gateway for AI agents with policy, human approval and execution receipts.
Human approval for AI agents: a named person approves or rejects, silence is not consent.
Event management for organizers: events, sessions, speakers, agendas, forms, approval-gated writes.
Governed AI workflows with human approval gates and audit trails for Claude and MCP clients.
Read your TacticalRMM fleet; run commands only after per-command human approval.
Answers built from our own checks of this server.