agent-identity-mcp
# agent-identity-mcp
[](https://mcpservers.org/servers/flovoice53-tech/agent-identity-mcp)
MCP server that gives an AI agent a throwaway test identity — a real disposable email address and a real UK phone number — so it can sign up for something it's testing and read back the verification email/SMS itself, without a human in the loop.
Bundles two existing services:
- [receivemail.dev](https://receivemail.dev) ([source](https://github.com/flovoice53-tech/receivemail-worker)) for the email side.
- [sms-florin](https://flo-voice1.com) for the phone/SMS side.
## Status: published on npm and the official MCP registry
`create_test_email` no longer needs any receivemail.dev credential — mailbox creation is public/self-serve (rate-limited: 20/min per IP, 5,000/day total). The only credential needed is your own `SMS_FLORIN_API_KEY`, for the phone-number tools.
## Setup
```json
{
"mcpServers": {
"agent-identity": {
"command": "npx",
"args": ["-y", "agent-identity-mcp"],
"env": {
"SMS_FLORIN_API_KEY": "your_key_here"
}
}
}
}
```
## Tools
| Tool | Description |
| --- | --- |
| `create_test_email` | Get a fresh disposable email address, valid up to 60 minutes. |
| `get_test_email_messages` | Read what's arrived on an address created above. |
| `list_services` | List services a phone number can be rented for. |
| `rent_test_phone_number` | Rent a real UK number for a service. Costs balance. |
| `wait_for_test_sms` | Block until the SMS/OTP code arrives. |
## Pairs well with: acp-sandbox
Building or testing an AI shopping agent (ACP/agentic commerce)? [acp-sandbox](https://github.com/flovoice53-tech/acp-sandbox) is a hosted mock merchant your agent can complete a full test checkout against — no real store, no real money. Combined with this package, an agent gets a disposable email/phone for the buyer identity *and* a merchant to actually check out with, entirely test-side.
## Pairs well with: otp-watch
Ship your own signup/verification flow? [otp-watch](https://otpwatch.flo-voice1.com) uses the same underlying real phone numbers and disposable mailboxes to answer a different question: is your OTP/verification SMS or email actually arriving, and how fast? Point your own cron/CI at it to catch a broken delivery pipeline before your users do.
## License
MIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: create_test_email and get_test_email_messages handle email lifecycle, while list_services, rent_test_phone_number, and wait_for_test_sms handle phone/SMS OTP. No two tools overlap in function or target resource.
All tools follow the verb_noun pattern with lowercase snake_case: create, get, list, rent, wait. Minor imprecision like list_services not specifying 'phone' is acceptable given the narrow domain.
5 tools is well-scoped for the server's purpose of testing identity verification via email and phone SMS. Each tool earns its place and the count feels neither sparse nor bloated.
The tool surface covers the essential flows: create and read test emails; list services, rent a phone number, and wait for SMS. There are no obvious dead ends or missing operations for the stated identity-testing purpose.