Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for builders testing agent flows that need sign-up confirmations or one-time emails, especially when they want an MCP-native inbox instead of writing email plumbing from scratch.
Who should use it
Who should skip it
Skip pexni/smails if the source repository or demo is inactive, unmaintained, or no longer matches the description shown here.
About this signal
pexni/smails is tracked by RepoRadar as a developer tool in the Agent Automation section. It was first seen on 2026-06-28 and last updated on 2026-06-28. The current verdict is 'try now' with a Silver tier and easy setup difficulty. Across RepoRadar's eight signals, pexni/smails is strongest on workflow potential (9.3) and setup ease (8.8) and weakest on momentum (3.0) — a profile worth weighing against your own priorities. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned pexni/smails a composite score of 7.8 out of 10, placing it in the Silver tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 3.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
It is designed to surface verification emails and magic links to an agent or script, so keep it on throwaway accounts and test flows rather than personal or production identity paths; The inboxes are intentionally disposable and auto-expiring, which makes them a poor fit for anything that needs durable account recovery or compliance retention; Using it in a live signup or auth flow still means an external system is being modified, so human review should stay in the loop for anything beyond low-stakes testing.