gecici.email - Temporary Email for QA
REMOTE · GECICI.EMAIL
Temporary inboxes for authorized QA, with token-protected message, code and link reading.
Available components
Last scanned (14 hours ago)
Scores higher than 56% of remote servers
Reachable. Last reached 6 Nov 2026.
Category Testing and QA
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- 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 Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 425 tokens (~85/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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 +1
- 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 0
- Stability: unverified → 0.03 ▲ functional
- 4 Nov 26 70
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 6 Nov 2026 · Probed https://gecici.email/mcp
TLS valid
Negotiated TLS 1.2 with TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=gecici.email | CN=YR2,O=Let's Encrypt,C=US | 22 Sept 2026 | 21 Dec 2026 | RSA 2048 | SHA256-RSA | 607afd3658c1ae0c2f661329f2be578a359 |
| SANs: gecici.email, www.gecici.email | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of gecici.email. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| email. | DS published | 53311 | 8 | Verified |
| gecici.email. | No DS | 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://gecici.email/mcp | Verified | 200 | |
| http (plaintext) | http://gecici.email/mcp | HTTPS enforced | 301 | https://gecici.email/mcp |
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 →
gecici_create_inbox Create temporary test inbox ~112
Create a temporary inbox for an authorized development or QA workflow. Return its address, access token, and expiry; the token is required to read it.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | Optional domain name. Defaults to "gecici.email". |
| prefix | string | – | Optional custom prefix (e.g. "myagent_99"): 4-32 ASCII characters with a digit and an internal -, _ or .; official and common role names are reserved. If omitted, a random address is generated. |
No output schema declared.
No examples provided.
gecici_get_ai_summary Read latest email summary ~53
Read the latest message summary from a temporary inbox owned with the supplied token.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The disposable email address. |
| token | string | yes | Access token returned by gecici_create_inbox. |
No output schema declared.
No examples provided.
gecici_get_inbox_messages List inbox messages ~63
List messages in a temporary inbox owned with the supplied token, including senders, subjects, and extracted summaries.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The disposable email address to inspect. |
| token | string | yes | Access token returned by gecici_create_inbox. |
No output schema declared.
No examples provided.
gecici_wait_for_magic_link Read verification link ~94
Read a verification or sign-in link received by a temporary inbox owned with the supplied token. Does not open the link.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The disposable email address to monitor. |
| timeout_seconds | number | – | Maximum time to wait in seconds (default: 30, min: 5, max: 45). |
| token | string | yes | Access token returned by gecici_create_inbox. |
No output schema declared.
No examples provided.
gecici_wait_for_otp Read verification code ~103
Read an email verification code received by a temporary inbox owned with the supplied token. Use for authorized testing.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The disposable email address to monitor (e.g. "agent123@gecici.email"). |
| timeout_seconds | number | – | Maximum time to wait in seconds (default: 30, min: 5, max: 45). |
| token | string | yes | Access token returned by gecici_create_inbox. |
No output schema declared.
No examples provided.
How do I install the gecici.email - Temporary Email for QA MCP server?
gecici.email - Temporary Email for QA is a hosted endpoint at https://gecici.email/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 · gecici.email
claude mcp add --transport http codeonthetable-gecici-email 'https://gecici.email/mcp'
What is the gecici.email - Temporary Email for QA MCP server?
gecici.email - Temporary Email for QA is an MCP server listed in the public MCP registry as io.github.codeonthetable/gecici-email. Temporary inboxes for authorized QA, with token-protected message, code and link reading. This page covers its hosted endpoint (https://gecici.email/mcp).
Is the gecici.email - Temporary Email for QA MCP server safe to use?
gecici.email - Temporary Email for QA scores 71 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 gecici.email - Temporary Email for QA MCP server expose?
gecici.email - Temporary Email for QA exposes 5 tools: gecici_create_inbox, gecici_wait_for_otp, gecici_wait_for_magic_link, gecici_get_inbox_messages, gecici_get_ai_summary. Their descriptions and schemas cost roughly 425 tokens of context every time the server is loaded.
Does the gecici.email - Temporary Email for QA MCP server require authentication?
No. We connected to gecici.email - Temporary Email for QA without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the gecici.email - Temporary Email for QA MCP server still maintained?
gecici.email - Temporary Email for QA is still listed as active in the MCP registry. We last reached this channel on 6 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 gecici.email - Temporary Email for QA MCP server?
VerifyMCP ran 13 checks on gecici.email - Temporary Email for QA, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.