Archived listing / no verified MCP endpoint/Communication

agmail listing

No MCP endpoint is published. This listing is retained for reference.

agmail is listed as a pay-per-use email inbox service for AI agents. The listing says an agent can choose an address, wait for a message in one call, and extract a code or link, with payment per call in x402 stablecoins and no account. The provider domain agmail.shveik.dev did not resolve on 2026-11-16, so the endpoint, tool behavior and payment terms are unverified. This page is retained as a reference only.

Archived listingNo verified MCP endpoint is published. This page is retained for reference only.
No MCP endpoint Reviewed 2026-11-16
About

Where it fits

Agent builders who need a temporary inbox for sign-up or verification flows, pending provider verification.

  • Create a temporary email address for an agent, if the service returns.
  • Wait for a message and extract its code or link.
  • Pay per call with x402 stablecoins instead of opening an account.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • Authentication fails or no tools appear. The listing does not verify the provider's credential flow; check its documentation before retrying.
  • The endpoint responds but rejects tool calls. Confirm the current address and any account, key, or payment requirement with the provider.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.