gecici.email

npx add-mcp 'https://gecici.email/mcp'

Temporary email for AI agents

Create a receive-only inbox for development or QA work you are authorized to perform. Read messages, extracted verification codes, and links using the access token returned at creation. Never put the token in a prompt, public log, or repository.

Hosted MCP endpoint

https://gecici.email/mcp is the hosted HTTP MCP endpoint. Configure it as a remote MCP server in a compatible client. Client setup varies; availability in a particular AI product is not guaranteed.

The tools support inbox creation and token-protected message and verification retrieval. Keep the address and token together in your agent's secure runtime state.

TESTED GUIDE · 25 October 2026

Test temporary email and verification-code tools with browser-use

An agent testing your application's email verification needs to create an inbox, read the incoming code, and delete the inbox when finished. This example registers those three operations as browser-use tools. The bearer token stays inside the Python helper; the agent receives the address and code needed by your form.

The check below dispatches real tools against the hosted API and adds a fictional message through the simulation endpoint. It does not launch a browser, call a language model or use an external email sender. Passing it does not prove that a website signup was completed.

1. Install the tested revision

Use Python 3.11 or later and start in a new directory. No model key or separate gecici-email Python package is required for this check.

git clone https://github.com/codeonthetable/gecici-email.git
cd gecici-email
git checkout 4951b8f041b8ebe9b98282dacbc4c2d262b711b5
python3 -m venv .venv
source .venv/bin/activate
python -m pip install 'browser-use==0.13.11'
python -m unittest discover -s tests -v
python examples/browser_use_inbox.py --qa-run

On Windows, activate with .venv\Scripts\activate. The pinned Git revision downloads the code used for the results below. Review the example source before running it.

2. Understand the result

With Python 3.12.14 and browser-use 0.13.11, 16 local tests passed; the separate opt-in live MCP test was skipped. The hosted API check returned these fields as true. It prints no addresses, tokens, messages or codes.

create_action_passed: true

The tool created a temporary inbox.

token_not_returned: true

The create tool's result did not contain the bearer token.

otp_action_matched: true

The extracted code matched the fictional message inserted by the test.

cleanup: true

The disposable inbox was deleted after the check.

Requests carry the qa-test label. This demonstration is excluded from normal usage; it is not a real user or successful AI-use count. Empty inboxes and timeouts are not successful verification.

3. Connect your own application's test flow

1. Create a fresh InboxTools(qa=True) for each run and add the tools to your existing agent with register(Tools()).
2. Ask the agent to call gecici_create_inbox and enter the returned address into your test form. Keep the bearer token out of the form.
3. After your application sends its message, call gecici_wait_for_otp with a timeout from 1 to 45 seconds. Enter the received code and check your application's explicit success state.
4. Call gecici_delete_inbox and also use await inbox.close() in your runner's finally block.

This adaptation needs your actual test application URL, a browser setup and a configured model. The full model-and-form workflow has not been tested for this guide. Your model can see the address and code, so use fictional test data and review your agent's history settings.

Agent integration code and test details →

No code arrived: what to check

Result	Next check
Deadline reached	Check your application's send result and delivery delay. Do not mark the form verified before a code arrives.
Inbox action failed	Check connectivity, expiry and parameters. Use a fresh helper for a new run.
Deletion failed	Retry await inbox.close() on the same helper. Failed deletion keeps the token in memory for retry.

The tools follow browser-use's custom-tool API. This example is published in the gecici.email repository; it does not imply browser-use endorsement or an accepted upstream contribution.

REST and MCP API guide · Türkçe rehber

REST integration

The REST base is https://gecici.email/api/v1. Create an inbox with POST /inbox/generate or POST /inbox/custom. Then pass Authorization: Bearer <token> when reading, extending, or deleting that inbox.

Read the English API guide.

Check the application result

Run the tested email verification form: a Python application and real Chrome form check wrong codes, verification, reuse rejection and cleanup with a hosted QA inbox. Message transport is simulated; no SMTP or LLM run is claimed.

Downloadable clients

The public GitHub repository provides a runnable client and integration material. It does not provide the private hosted server source. Check the repository's current setup instructions before integrating.

Operational limits

• Receive-only; no outbound email.
• Default inbox lifetime: 60 minutes; token holder may extend or delete.
• External delivery, verification acceptance, and third-party service behavior are not guaranteed.
• No CAPTCHA or security-control bypass is provided.