io.github.fieldcure/outbox
NUGET · FIELDCURE.MCP.OUTBOX · SCANNED SEP 20
Multi-channel messaging MCP server for Slack, Telegram, Email, KakaoTalk, and Discord.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 117 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 297 tokens (~74/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.fieldcure/outbox MCP server?
io.github.fieldcure/outbox runs locally as a NuGet package, launched with dnx FieldCure.Mcp.Outbox@2.1.3 --yes. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
nuget · FieldCure.Mcp.Outbox
claude mcp add fieldcure-outbox -- dnx FieldCure.Mcp.Outbox@2.1.3 --yes
{
"mcpServers": {
"fieldcure-outbox": {
"command": "dnx",
"args": [
"FieldCure.Mcp.Outbox@2.1.3",
"--yes"
]
}
}
} {
"servers": {
"fieldcure-outbox": {
"command": "dnx",
"args": [
"FieldCure.Mcp.Outbox@2.1.3",
"--yes"
]
}
}
} codex mcp add fieldcure-outbox -- dnx FieldCure.Mcp.Outbox@2.1.3 --yes
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"fieldcure-outbox": {
"type": "local",
"command": [
"dnx",
"FieldCure.Mcp.Outbox@2.1.3",
"--yes"
],
"enabled": true
}
}
} mcp_servers:
fieldcure-outbox:
command: "dnx"
args: ["FieldCure.Mcp.Outbox@2.1.3", "--yes"] {
"McpServers": {
"fieldcure-outbox": {
"Transport": "stdio",
"Command": "dnx",
"Arguments": [
"FieldCure.Mcp.Outbox@2.1.3",
"--yes"
]
}
}
} {
"mcpServers": {
"fieldcure-outbox": {
"command": "dnx",
"args": [
"FieldCure.Mcp.Outbox@2.1.3",
"--yes"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.77 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 −2
- Stability: pass → 0.83 functional
- 10 Sept 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed nuget/FieldCure.Mcp.Outbox@2.1.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | nuget |
| Reason | Signature present, unreadable |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_channel ~86
Adds a new messaging channel by collecting configuration through MCP elicitation. Supported types: slack, telegram, gmail, naver, smtp, kakaotalk, microsoft, discord.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string|null | – | Display name for the channel (optional) |
| type | string | yes | Channel type: slack, telegram, gmail, naver, smtp, kakaotalk, microsoft, discord |
No output schema declared.
No examples provided.
list_channels ~34
Lists all configured messaging channels. Returns channel ID, type, name, and additional metadata such as the sender address for SMTP channels.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
remove_channel ~39
Removes a configured messaging channel and its stored data.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | yes | Channel ID to remove (e.g. 'slack_dev-alerts') |
No output schema declared.
No examples provided.
send_message ~138
Sends a message through a configured channel. For SMTP channels, 'to' (recipient email) and 'subject' parameters are required. For Slack channels, 'target_channel' can override the default channel.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | yes | Channel ID to send through (e.g. 'slack_dev-alerts', 'smtp_gmail_1') |
| message | string | yes | Message body text |
| subject | string|null | – | Email subject (required for SMTP channels) |
| target_channel | string|null | – | Target channel override (e.g. Slack channel name) |
| to | string|null | – | Recipient email address (required for SMTP channels) |
No output schema declared.
No examples provided.
What is the io.github.fieldcure/outbox MCP server?
io.github.fieldcure/outbox is an MCP server listed in the public MCP registry as io.github.fieldcure/outbox. Multi-channel messaging MCP server for Slack, Telegram, Email, KakaoTalk, and Discord. This page covers its NuGet package (FieldCure.Mcp.Outbox).
Is the io.github.fieldcure/outbox MCP server safe to use?
io.github.fieldcure/outbox scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.fieldcure/outbox MCP server expose?
io.github.fieldcure/outbox exposes 4 tools: send_message, list_channels, add_channel, remove_channel. Their descriptions and schemas cost roughly 297 tokens of context every time the server is loaded.
Is the io.github.fieldcure/outbox MCP server still maintained?
io.github.fieldcure/outbox is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.fieldcure/outbox MCP server under?
io.github.fieldcure/outbox declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.