126-mail-smtp · v1

126 Mail SMTP

126 Mail SMTP. No stable public request shape is recorded, so the call is refused and no mail is sent.

Run now REST API / MCP Manifest

Sample input

Paste text in the workbench and run.

API / MCP call

curl -X POST https://toolkit.fun/api/v1/t/126-mail-smtp \
  -H "Authorization: Bearer tk_..." \
  -H "Content-Type: application/json" \
  -d '{"input":"...","params":{}}'

MCP server: https://toolkit.fun/api/mcp

Shortest path for an agent

Read the manifest first, then call the same run contract used by the web UI. The input, output, permissions, and receipt stay consistent across REST and MCP.

Manifest: https://toolkit.fun/api/v1/registry/tools/126-mail-smtp/manifest
REST: POST https://toolkit.fun/api/v1/t/126-mail-smtp
MCP: https://toolkit.fun/api/mcp

Who it is for

Use this tool directly when you need 126 Mail SMTP, want to chain it into a workflow, or want to expose it to an agent over REST API or MCP. This page carries the sample, call syntax, manifest, and version so search engines and generative retrieval can describe the tool accurately.

Notes

126 Mail SMTP. No stable public request shape is recorded, so the call is refused and no mail is sent.

Frequently asked questions

What does 126 Mail SMTP do?

126 Mail SMTP. No stable public request shape is recorded, so the call is refused and no mail is sent.

How do I use 126 Mail SMTP online?

Click “Open workbench” to open 126 Mail SMTP, provide your input, and run the tool.

What input and output does 126 Mail SMTP use?

Declared input type: text. Declared output type: json.