No user-submitted related servers found.
Scored across 179 tools
Several near-identical creation flows coexist: create_verification, create_session, create_multi_channel_verification, create_verification_request, create_user_request, start_domain_verification, start_user_domain_verification, and start_add_phone all appear to start some kind of verification, and an agent must read deeply to pick the right one. Domain checking is likewise split across verify_domain, verify_domain_with_credentials, trigger_verification, check_domain_verification, and check_user_domain_verification, while listing tools (list_verifications, list_verification_requests, list_my_requests, list_incoming_requests) overlap by subject vs creator. Descriptions are rich but the boundaries between tools remain unclear at the set level.
Most names are snake_case verb_noun, but the verb vocabulary is inconsistent for parallel concepts: start_login vs create_account vs create_session, start_add_phone vs create_session, add_domain vs setup_domain_email, plus bare outliers like search and test_verify. Readable, but there is no single predictable convention an agent can rely on to guess a tool name.
179 tools is an extreme surface for a single server — far beyond what an agent can survey, let alone select from reliably. Much of the volume is granular CRUD across a dozen sub-domains (2FA, circles, HITL, delegations, templates, billing, DNS credentials), which should be separate servers or consolidated into fewer parameterized tools.
Coverage is genuinely broad: verification lifecycle, domains, phones, emails, API keys, webhooks, HITL, circles, delegations, billing, templates, login and 2FA flows all have create/read/update/delete-ish operations. Minor gaps exist (e.g. a confirmation resend tool is explicitly noted as absent, and some poll-only flows), but agents can usually work around them.
