Loading ToolBench

Reading the current corpus…

mailwizz-smtp-proxy MCP server · F · ToolBench

← Browse

mailwizz-smtp-proxy

github.com/Sendmux/mailwizz-smtp-proxy

Integrates email delivery with automatic bounce and complaint handling via Sendmux Sending API

2026-07-28+3 tools

27/100

Definition Quality26

Protocol Readiness0

Supportability47

Spec posture

Inferred effective spec 2026-07-28+·current baseline 2026-07-28

Static source inference · medium confidence

Current-spec patterns detected

Summary

This is a MailWizz extension, not an MCP server. The codebase shows PHP models and controllers for email delivery integration, not MCP tool definitions. No MCP protocol implementation is visible. The three listed 'tools' (send, processSendmuxWebApi, processWebhookEvent) appear to be inferred from class methods, not explicitly registered as MCP tools with schemas. Tool definitions lack proper JSON Schema input specifications, descriptions are minimal or missing, and there is no evidence of MCP transport (HTTP, SSE, or STDIO). The repository URL points to a 'mailwizz-smtp-proxy' which is not an MCP server.

Tools (3)

processSendmuxWebApiwriteauth18/100

Process Sendmux webhook events for bounce and complaint handling

processWebhookEventwriteauth20/100

Process a single webhook event from Sendmux

sendwriteauth50/100

Send email via Sendmux Sending API

Issues (5)

CRITICALtool ↗

Not an MCP server. Codebase is a MailWizz PHP extension, not an MCP implementation. No MCP protocol transport, tool registration, or capability negotiation visible.

sendprocessSendmuxWebApiprocessWebhookEvent

CRITICALtool ↗

Tool definitions inferred from class methods, not explicitly registered. No JSON Schema input schemas visible for processSendmuxWebApi and processWebhookEvent.

processSendmuxWebApiprocessWebhookEvent

HIGHtool ↗

Naming violates verb_noun convention. 'processSendmuxWebApi' and 'processWebhookEvent' use generic 'process' verb. Should be 'handle_webhook_event' or 'process_bounce_complaint'. Generic names prevent LLM intent inference.

processSendmuxWebApiprocessWebhookEvent

HIGHtool-description ↗

Descriptions are minimal or absent. 'processSendmuxWebApi' has no description in source. 'processWebhookEvent' description is vague ('Process a single webhook event').

Recommendations

Clarify: Is this an MCP server or a MailWizz extension? If MCP, implement proper MCP protocol with HTTP/SSE transport, tool registration via initialize, and JSON Schema input/output specs.
If converting to MCP: rename tools to verb_noun format (send_email, handle_webhook_event, process_bounce_complaint) and add 50-200 char descriptions explaining WHAT, WHEN, and WHAT IT RETURNS.
Add explicit JSON Schema input definitions for all tools. processSendmuxWebApi and processWebhookEvent currently have no visible schemas. Include type, description, and constraints for every parameter.
Document output schemas. Specify what fields send_email returns (message_id, status, timestamp) so agents can chain calls and extract required data.
Add error handling guidance: 'If API returns 401, check webhook_secret. If 429, retry after 60s. If 5xx, contact Sendmux support.' Include recovery hints and retryability classification.

Score history

Overall score trend

First recorded score · v2 rubric

27/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	F	27	2026-07-28+	v2