My MCP Serv
REMOTE · SEND-EMAIL-MCP-04D3FDCA.STAGING.ALPIC.LIVE · SCANNED OCT 1
Non functional server (yet)
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 127 tokens (~127/item across 1 items; 1 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_email" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 1 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
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the My MCP Serv server?
My MCP Serv is a hosted endpoint at https://send-email-mcp-04d3fdca.staging.alpic.live/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · send-email-mcp-04d3fdca.staging.alpic.live
claude mcp add --transport http live-alpic-staging-send-email-mcp-04d3fdca-send- 'https://send-email-mcp-04d3fdca.staging.alpic.live/'
{
"mcpServers": {
"live-alpic-staging-send-email-mcp-04d3fdca-send-": {
"url": "https://send-email-mcp-04d3fdca.staging.alpic.live/"
}
}
} {
"servers": {
"live-alpic-staging-send-email-mcp-04d3fdca-send-": {
"type": "http",
"url": "https://send-email-mcp-04d3fdca.staging.alpic.live/"
}
}
} [mcp_servers.live-alpic-staging-send-email-mcp-04d3fdca-send-] url = "https://send-email-mcp-04d3fdca.staging.alpic.live/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"live-alpic-staging-send-email-mcp-04d3fdca-send-": {
"type": "remote",
"url": "https://send-email-mcp-04d3fdca.staging.alpic.live/",
"enabled": true
}
}
} openclaw mcp add live-alpic-staging-send-email-mcp-04d3fdca-send- --url 'https://send-email-mcp-04d3fdca.staging.alpic.live/' --transport streamable-http
mcp_servers:
live-alpic-staging-send-email-mcp-04d3fdca-send-:
url: "https://send-email-mcp-04d3fdca.staging.alpic.live/" {
"McpServers": {
"live-alpic-staging-send-email-mcp-04d3fdca-send-": {
"Transport": "http",
"Url": "https://send-email-mcp-04d3fdca.staging.alpic.live/"
}
}
} assistant mcp add live-alpic-staging-send-email-mcp-04d3fdca-send- -t streamable-http -u 'https://send-email-mcp-04d3fdca.staging.alpic.live/'
{
"mcpServers": {
"live-alpic-staging-send-email-mcp-04d3fdca-send-": {
"type": "http",
"url": "https://send-email-mcp-04d3fdca.staging.alpic.live/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 1 Oct 26 +36
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Schema quality: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → good ▲ functional
- First check of Tool coverage: 0 functional
- First check of Destructive annotations: 0 functional
- First check of Tool coverage: 100 functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 2 Sept 26 23
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- 1 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 31 Aug 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 30 Aug 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 29 Aug 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
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 1 Oct 2026 · Probed https://send-email-mcp-04d3fdca.staging.alpic.live
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.staging.alpic.live | CN=Amazon RSA 2048 M04,O=Amazon,C=US | 21 Sept 2026 | 6 Apr 2027 | RSA 2048 | SHA256-RSA | 14c635a575e4dafd6b8c89742081286 |
| SANs: *.staging.alpic.live | ||||||
| CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 773124f2a952e3ed18a58bdb85d1bc0ce5f27 |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of send-email-mcp-04d3fdca.staging.alpic.live. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| live. | present | 36322 | 8 | Verified |
| alpic.live. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://send-email-mcp-04d3fdca.staging.alpic.live | Verified | 200 | |
| http (plaintext) | http://send-email-mcp-04d3fdca.staging.alpic.live | HTTPS enforced | 301 | https://send-email-mcp-04d3fdca.staging.alpic.live/ |
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 →
send_email ~127
Send an email via Resend API. Args: sender_email: Sender email address (must be verified in Resend) to_emails: List of recipient email addresses subject: Email subject line text_content: Plain text content (required if html_content not provided) html_content: HTML content (required if text_content not provided) Returns: API response with email ID on success
| Name | Type | Req | Description |
|---|---|---|---|
| html_content | – | – | – |
| sender_email | string | yes | – |
| subject | string | yes | – |
| text_content | – | – | – |
| to_emails | array | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
What is the My MCP Serv server?
My MCP Serv is listed in the public MCP registry as live.alpic.staging.send-email-mcp-04d3fdca/send-email-mcp. Non functional server (yet). This page covers its hosted endpoint (https://send-email-mcp-04d3fdca.staging.alpic.live).
Is the My MCP Serv server safe to use?
My MCP Serv scores 59 out of 100 on VerifyMCP. 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 My MCP Serv server expose?
My MCP Serv exposes 1 tool: send_email. Their descriptions and schemas cost roughly 127 tokens of context every time the server is loaded.
Does the My MCP Serv server require authentication?
No. We connected to My MCP Serv without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the My MCP Serv server still maintained?
My MCP Serv is still listed as active in the MCP registry. We last reached this channel on 1 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.