Edge Actors: email verifier, DNS facts, URL to Markdown

io.github.EdgeF-4Published by GitHub account EdgeF-4v1.0.1Updated Nov 7, 2026

Email verifier ($0.60/1k), SPF/DMARC/MX facts, URL to Markdown, on your own Apify account.

The publisher's own server: Edge Network

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingSecurity & Monitoring

Overview

AI-generated overview

Apify-hosted remote MCP server offering email verification, SPF/DMARC/MX DNS lookups and URL-to-Markdown conversion on your own Apify account.

What you can do
  • Verify email addresses and get deliverability results
  • Look up DNS records such as SPF, DMARC and MX for a domain
  • Convert a web page URL into Markdown text
  • Run these actors against your own Apify account
When to use it
Useful when you need to clean or validate an email list, check a domain's email authentication records, or turn web pages into Markdown for reading or summarization without writing your own scrapers.
Requirements
Remote streamable HTTP endpoint at mcp.apify.com; an Apify account. Authentication via OAuth sign-in or an Apify API token sent as an Authorization Bearer header. Usage is billed to your Apify account.
Before you install
Paid usage: the email verifier is listed at $0.60 per 1,000 checks, billed through your Apify account. The Authorization header carries an Apify API token, so keep it secret and prefer OAuth where possible. Submitted email addresses and URLs are processed by Apify's actors.

Installation

In SourceWeft

  1. Open Edge Actors: email verifier, DNS facts, URL to Markdown in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.EdgeF-4%2Fedge-actors/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "edge-actors-email-verifier-dns-facts-url": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=edgef-4/bulk-email-verifier,edgef-4/domain-dns-facts,edgef-4/url-to-markdown-for-ai-agents"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.0.1LatestNov 7, 2026
  2. v1.0.0Nov 5, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Edge integrations