# io.github.retep-tru/maeil (remote · mcp.maeil.cc)

Invite someone to a calendar event by phone number and get their real email back when they accept.

- Trust score: 61/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.maeil.cc`: 61/100 (this document), [markdown](https://verifymcp.io/servers/retep-tru-maeil/mcp.md), [page](https://verifymcp.io/servers/retep-tru-maeil/mcp)

## Channel facts

- Endpoint: `https://mcp.maeil.cc/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http retep-tru-maeil https://mcp.maeil.cc/mcp
```

### Codex

```toml
[mcp_servers.retep-tru-maeil]
url = "https://mcp.maeil.cc/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "retep-tru-maeil": {
      "type": "remote",
      "url": "https://mcp.maeil.cc/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add retep-tru-maeil --url https://mcp.maeil.cc/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  retep-tru-maeil:
    url: "https://mcp.maeil.cc/mcp"
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 61, +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.

### 2026-08-01 (score 60, +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.

### 2026-07-31 (score 59, −2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 61, +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.

### 2026-07-28 (score 60, +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.

### 2026-07-27 (score 59, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 58)

First indexed and scored.

## MCP tools (2)

### `send_calendar_invite` (~373 tokens)

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.

Input parameters:

- `callback_url` (string): Optional public https URL. maeil POSTs the recipient's response (and email) here when they accept or decline.
- `consent_attestation` (string, required): 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, required): Organizer email. The RSVP and the recipient's revealed email are delivered to this address.
- `phone` (string, required): Recipient phone number, US/Canada. Accepts +15551234567, 15551234567, 5551234567, or (555) 123-4567.
- `start` (string, required): 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, required): Event title. Shown in the text message and on the accept page.

### `get_invite_status` (~75 tokens)

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.

Input parameters:

- `invite_id` (string, required): The invite_id returned by send_calendar_invite.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/retep-tru-maeil/mcp#diagnostics

## Score history

- 2026-08-03: 61
- 2026-08-02: 60
- 2026-08-01: 60
- 2026-07-31: 59
- 2026-07-30: 61
- 2026-07-29: 60
- 2026-07-28: 60
- 2026-07-27: 59
- 2026-07-26: 58

## Links

- Remote endpoint: https://mcp.maeil.cc/mcp
- Website: https://maeil.cc/power
- Changelog RSS feed: https://verifymcp.io/servers/retep-tru-maeil/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/retep-tru-maeil/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/retep-tru-maeil/mcp