io.github.retep-tru/maeil
REMOTE · MCP.MAEIL.CC · SCANNED AUG 3
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 →
Endpoint Security46
- 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 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. See how to fix → View diagnostics → Unverified
- HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 566 tokens (~283/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.maeil.cc
claude mcp add --transport http retep-tru-maeil 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": {
"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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 58
First indexed and scored.
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 3 Aug 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 | 21 Jul 2026 | 19 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 5a3b683198d26d8addea65355c0f5ba7e3a |
| 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 |
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 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 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.maeil.cc/mcp | Verified | 200 | |
| 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.
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.