Is the Mifactory Bot Mifactory Email MCP server down?

mcp-registry/io.github.mifactory-bot/mifactory-email · v1.0.0

healthy
Last checked 2026-10-19 21:08 UTC · handshake 136ms

As of 2026-10-19 21:08 UTC, the Mifactory Bot Mifactory Email MCP server 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 1 outage in 90 days, with a median recovery of 11 minutes.

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

Send transactional emails for AI agents via SMTP. Templates included.

Install Mifactory Bot Mifactory Email MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http mifactory-bot-mifactory-email-mcp-server https://mifactory-email.vercel.app/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "mifactory-bot-mifactory-email-mcp-server": {
      "type": "http",
      "url": "https://mifactory-email.vercel.app/mcp"
    }
  }
}

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

Agent-readiness: D (66/100)

D (66/100): 0 error(s), 4 warning(s) across 3 tool(s); ~586 tokens of tool definitions.
Scores higher than 1% of 15,371 MCP servers Glimind has audited.
Its tool list costs an agent ~586 tokens per session — lighter than 90% of servers.
65 → 66 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions43
Safety hints0
Token cost100
Client compatibility70
Protocol40
Reliability100
Stability100

What to fix (5)

3 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: send_bulk, send_email, send_template

3 of 3 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: send_bulk, send_email, send_template

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: send_bulk, send_template

Negotiates MCP 2024-11-05. 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 →

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: 3 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/mcp-registry%2Fio.github.mifactory-bot%2Fmifactory-email/fixes

send_bulk 1 change 
{
  "name": "send_bulk",
  "description": "Envía hasta 10 emails en una sola llamada. Cuesta 5 créditos.",
  "inputSchema": {
    "type": "object",
    "required": [
      "smtp",
      "emails"
    ],
    "properties": {
      "smtp": {
        "type": "object",
        "required": [
          "host",
          "user",
          "pass"
        ],
        "properties": {
          "host": {
            "type": "string"
          },
          "pass": {
            "type": "string"
          },
          "user": {
            "type": "string"
          }
        }
      },
      "emails": {
        "type": "array",
        "items": {
          "type": "object",
          "required": [
            "to",
            "subject"
          ],
          "properties": {
            "to": {
              "type": "string"
            },
            "html": {
              "type": "string"
            },
            "text": {
              "type": "string"
            },
            "subject": {
              "type": "string"
            }
          }
        },
        "description": "Lista de emails a enviar (máx 10)"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
send_email 1 change 
{
  "name": "send_email",
  "description": "Envía un email transaccional. Cuesta 1 crédito.",
  "inputSchema": {
    "type": "object",
    "required": [
      "smtp",
      "to",
      "subject"
    ],
    "properties": {
      "to": {
        "type": "string",
        "description": "Email destinatario"
      },
      "from": {
        "type": "string",
        "description": "Email remitente (opcional)"
      },
      "html": {
        "type": "string",
        "description": "Cuerpo en HTML"
      },
      "smtp": {
        "type": "object",
        "required": [
          "host",
          "user",
          "pass"
        ],
        "properties": {
          "host": {
            "type": "string",
            "description": "SMTP host (ej: smtp.gmail.com)"
          },
          "pass": {
            "type": "string",
            "description": "Contraseña SMTP"
          },
          "port": {
            "type": "number",
            "description": "Puerto (default: 587)"
          },
          "user": {
            "type": "string",
            "description": "Usuario SMTP"
          }
        },
        "description": "Configuración SMTP"
      },
      "text": {
        "type": "string",
        "description": "Cuerpo en texto plano"
      },
      "subject": {
        "type": "string",
        "description": "Asunto del email"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
send_template 1 change 
{
  "name": "send_template",
  "description": "Envía email usando un template predefinido. Cuesta 2 créditos. Templates: welcome, invoice, reset_password, notification.",
  "inputSchema": {
    "type": "object",
    "required": [
      "smtp",
      "to",
      "template"
    ],
    "properties": {
      "to": {
        "type": "string",
        "description": "Email destinatario"
      },
      "from": {
        "type": "string",
        "description": "Email remitente (opcional)"
      },
      "smtp": {
        "type": "object",
        "required": [
          "host",
          "user",
          "pass"
        ],
        "properties": {
          "host": {
            "type": "string"
          },
          "pass": {
            "type": "string"
          },
          "user": {
            "type": "string"
          }
        }
      },
      "template": {
        "type": "string",
        "description": "Nombre del template: welcome, invoice, reset_password, notification"
      },
      "variables": {
        "type": "object",
        "description": "Variables para el template"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

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.mifactory-bot/mifactory-email"],"email":"[email protected]"}'

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

Tools (3)

Compare: most reliable communication servers · most reliable email 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 Mifactory Bot Mifactory Email MCP server down right now?

As of 2026-10-19 21:08 UTC, the Mifactory Bot Mifactory Email MCP server 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 1 outage in 90 days, with a median recovery of 11 minutes.

How many tools does Mifactory Bot Mifactory Email MCP server provide?

Mifactory Bot Mifactory Email MCP server advertises 3 tools, including send_bulk, send_email, send_template.

How do I install Mifactory Bot Mifactory Email MCP server?

Point your MCP client at this streamable-http endpoint: https://mifactory-email.vercel.app/mcp

Is the Mifactory Bot Mifactory Email MCP server safe to connect to an AI agent?

Glimind scanned all 3 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 Mifactory Bot Mifactory Email 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