io.github.retep-tru/maeil
REMOTE · MCP.MAEIL.CC · SCANNED OCT 7
Invite someone to a calendar event by phone number and get their real email back when they accept.
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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 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. Claim this server and supply a read-only token to verify it and lift the score.
How do I install the io.github.retep-tru/maeil MCP server?
io.github.retep-tru/maeil is a hosted endpoint at https://mcp.maeil.cc/mcp, 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 · mcp.maeil.cc
claude mcp add --transport http retep-tru-maeil 'https://mcp.maeil.cc/mcp'
{
"mcpServers": {
"retep-tru-maeil": {
"url": "https://mcp.maeil.cc/mcp"
}
}
} {
"servers": {
"retep-tru-maeil": {
"type": "http",
"url": "https://mcp.maeil.cc/mcp"
}
}
} [mcp_servers.retep-tru-maeil] url = "https://mcp.maeil.cc/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"retep-tru-maeil": {
"type": "remote",
"url": "https://mcp.maeil.cc/mcp",
"enabled": true
}
}
} openclaw mcp add retep-tru-maeil --url 'https://mcp.maeil.cc/mcp' --transport streamable-http
mcp_servers:
retep-tru-maeil:
url: "https://mcp.maeil.cc/mcp" {
"McpServers": {
"retep-tru-maeil": {
"Transport": "http",
"Url": "https://mcp.maeil.cc/mcp"
}
}
} assistant mcp add retep-tru-maeil -t streamable-http -u 'https://mcp.maeil.cc/mcp'
{
"mcpServers": {
"retep-tru-maeil": {
"type": "http",
"url": "https://mcp.maeil.cc/mcp"
}
}
} 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.
- 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
- 4 Sept 26 0
- Endpoint reachability: reachable → behind authorisation ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: unverified → pass ▲ security
- First check of Authorization: partial security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 26 Aug 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 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 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
- 31 Jul 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
- 27 Jul 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 7 Oct 2026 · Probed https://mcp.maeil.cc/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=maeil.cc | CN=YE1,O=Let's Encrypt,C=US | 18 Sept 2026 | 17 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6643a842f19acf290f3bb9e77c6275b7355 |
| SANs: *.maeil.cc, maeil.cc | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.maeil.cc. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| cc. | present | 12593 | 13 | Verified |
| maeil.cc. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer realm="maeil", resource_metadata="https://mcp.maeil.cc/.well-known/oauth-protected-resource"
Bearer realm="maeil", resource_metadata="https://mcp.maeil.cc/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| www-authenticate | Bearer realm="maeil", resource_metadata="https://mcp.maeil.cc/.well-known/oauth-protected-resource" |
Protected resource metadata
| Document | https://mcp.maeil.cc/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.maeil.cc/mcp |
| Authorisation server | https://api.maeil.cc |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.maeil.cc/mcp | Auth required | 401 | |
| http (plaintext) | http://mcp.maeil.cc/mcp | Inconclusive | 405 |
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 →
get_invite_status ~75
Check whether a sent invite has been accepted or declined, and retrieve the recipient's revealed email once they have accepted. Returns one of: sent, accepted, declined, failed. The revealed email is null until the recipient accepts and provides it.
| Name | Type | Req | Description |
|---|---|---|---|
| invite_id | string | yes | The invite_id returned by send_calendar_invite. |
No output schema declared.
No examples provided.
send_calendar_invite ~373
Invite a person to a calendar event using only their phone number. They receive the invite as a text message; if they accept, their real email address is returned to the organizer (retrieve it with get_invite_status, or have it POSTed to your callback_url). US and Canada phone numbers only. You must attest that you have the recipient's consent to contact them about this event.
| Name | Type | Req | Description |
|---|---|---|---|
| callback_url | string | – | Optional public https URL. maeil POSTs the recipient's response (and email) here when they accept or decline. |
| consent_attestation | string | yes | REQUIRED. A short statement of the basis on which you are permitted to text this person about this event (e.g. "client booked by phone on 6/1", "met at conference and exchanged numbers"). This is the… |
| description | string | – | Optional event description / notes. |
| end | string | – | Optional event end, same formats as start. |
| location | string | – | Optional location (e.g. "Phone", an address, or a meeting link). |
| organizer | string | yes | Organizer email. The RSVP and the recipient's revealed email are delivered to this address. |
| phone | string | yes | Recipient phone number, US/Canada. Accepts +15551234567, 15551234567, 5551234567, or (555) 123-4567. |
| start | string | yes | Event start. ISO 8601 datetime (e.g. 2026-06-15T14:00:00Z) or a date (2026-06-15) for an all-day event. |
| title | string | yes | Event title. Shown in the text message and on the accept page. |
No output schema declared.
No examples provided.
What is the io.github.retep-tru/maeil MCP server?
io.github.retep-tru/maeil is an MCP server listed in the public MCP registry as io.github.retep-tru/maeil. Invite someone to a calendar event by phone number and get their real email back when they accept. This page covers its hosted endpoint (https://mcp.maeil.cc/mcp).
Is the io.github.retep-tru/maeil MCP server safe to use?
io.github.retep-tru/maeil scores 31 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 io.github.retep-tru/maeil MCP server expose?
io.github.retep-tru/maeil exposes 2 tools: send_calendar_invite, get_invite_status. Their descriptions and schemas cost roughly 448 tokens of context every time the server is loaded.
Does the io.github.retep-tru/maeil MCP server require authentication?
Yes. io.github.retep-tru/maeil asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.github.retep-tru/maeil MCP server still maintained?
io.github.retep-tru/maeil is still listed as active in the MCP registry. We last reached this channel on 7 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.