Template
REMOTE · EMAIL-MCP-DBB94DBF.ALPIC.LIVE
Description of my MCP server
Available components
Last scanned (19 hours ago)
Scores higher than 7% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Communication
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 yet verified: we couldn't confirm whether this endpoint requires it. 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 402. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (5)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (6)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 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
- 5 Nov 26 −36
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.10 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Schema quality: 33 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 4 Nov 26 −13
- Stability: pass → 0.10 functional
- 1 Nov 26 +49
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 2 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
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 33 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 10 Oct 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.10 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Schema quality: 33 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 2 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 1 Oct 26 0
- 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 2 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 → fair ▲ functional
- Schema quality: unverified → 33 ▲ functional
- Schema quality: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ 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
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 21 Nov 2026 · Probed https://email-mcp-dbb94dbf.alpic.live
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.alpic.live | CN=Amazon RSA 2048 M04,O=Amazon,C=US | 23 Sept 2026 | 8 Apr 2027 | RSA 2048 | SHA256-RSA | 41ca0c3068063f7c713f936a81919aa |
| SANs: *.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 email-mcp-dbb94dbf.alpic.live. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| live. | DS published | 4724 | 8 | Verified |
| alpic.live. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 402 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 3 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://email-mcp-dbb94dbf.alpic.live | HTTP error | 402 | |
| sse | https://email-mcp-dbb94dbf.alpic.live | HTTP error | 402 | |
| http (plaintext) | http://email-mcp-dbb94dbf.alpic.live | HTTPS enforced | 301 | https://email-mcp-dbb94dbf.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 →
greet ~22
A simple greeting tool
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Name to greet |
No output schema declared.
No examples provided.
send_email ~177
Send emails via Resend API. Provide html_content and/or text_content.
| Name | Type | Req | Description |
|---|---|---|---|
| attachments | array | – | Attachments (max 40MB total) |
| bcc_emails | array | – | BCC recipients |
| cc_emails | array | – | CC recipients |
| html_content | string | – | HTML content of the email |
| reply_to | – | – | Reply-to email address(es) |
| scheduled_at | string | – | Schedule email for later (natural language or ISO 8601) |
| sender_email | string | yes | Sender email address, verified in Resend |
| subject | string | yes | Email subject line |
| tags | array | – | Custom tags as key/value pairs |
| text_content | string | – | Plain text version of the email |
| to_emails | array | yes | List of recipient email addresses (max 50) |
No output schema declared.
No examples provided.
How do I install the Template MCP server?
Template is a hosted endpoint at https://email-mcp-dbb94dbf.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 · email-mcp-dbb94dbf.alpic.live
claude mcp add --transport http live-alpic-email-mcp-dbb94dbf-email-mcp 'https://email-mcp-dbb94dbf.alpic.live/'
What is the Template MCP server?
Template is an MCP server listed in the public MCP registry as live.alpic.email-mcp-dbb94dbf/email-mcp. Description of my MCP server. This page covers its hosted endpoint (https://email-mcp-dbb94dbf.alpic.live).
Is the Template MCP server safe to use?
Template scores 23 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 Template MCP server expose?
Template exposes 2 tools: greet, send_email. Their descriptions and schemas cost roughly 199 tokens of context every time the server is loaded.
Does the Template MCP server require authentication?
Its publisher declares no required credentials for Template. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Template MCP server still maintained?
Template is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Template MCP server?
VerifyMCP ran 5 checks on Template, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about Template: Authorization, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.