verify_sending_domain

3 registry entries were observed exposing a tool named verify_sending_domain — none of them flagged as a privileged capability.

Every row is point-in-time scan output, dated below. Forge has an observed tool surface for 13,558 of 45,202 scannable entries (30%) — an entry that has not been scanned cannot appear here, so absence from this list is not evidence that an entry does not expose this tool.

  1. nintact-mcpMCPcommunitytrust 60/100 · B
    v0.5.1
    ↓ 255/wk

    MCP server for NINTACT — create contact forms, read what came in, approve AI-written replies.

    ClaudeCursorCopilotGemini
    com.nintactMIT1mo agonpmGitHubobserved · static extraction
    mcpmodel-context-protocolmcp-serverclaudecontact-formforms
  2. @sendraven/mcpMCPcommunitylivetrust 60/100 · B
    v0.4.24
    ↓ 186/wk
    ★ 1

    MCP server for SendRaven, email infrastructure for AI agents: send email, read replies as threads, run campaigns and automations, with per-key limits and approvals.

    ClaudeCursorCopilotChatGPTGemini
    Common Ninja Ltd.MIT8d agonpmGitHubobserved · static extraction
    mcpmodel-context-protocolemailemail-apiai-agentsclaude
  3. now.shiply/shiplyMCPcommunitylivetrust 60/100 · B
    v1.1.0

    Publish any app in one call: SQL database, functions, email, and a custom domain. Flat price.

    ClaudeCursorCopilotChatGPTGemini
    now.shiplyUnknown3mo agoobserved · live tools/list
    mcp

All indexed toolsSearch the registry for verify_sending_domain