Anymail Finder

io.github.anymailfinderPublished by GitHub account anymailfinderv1.2.0Updated Nov 5, 2026

Find and verify work emails by name, company, role or LinkedIn URL, and find who is behind an email.

The publisher's own server: Finder Jobs

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Anymail Finder is a remote MCP server that lets an assistant find and verify work emails by name, company, role or LinkedIn URL, and reverse-look-up who owns…

What you can do
  • Find work email addresses from a person's name, company, role or LinkedIn profile URL.
  • Verify whether a given email address is valid.
  • Reverse-look-up the person behind an email address.
  • No individual tools are documented in the supplied listing, so exact operations are not itemized.
When to use it
Useful when an assistant needs to research professional contact details for sales, recruiting or outreach, or to check whether an address is deliverable before using it.
Requirements
A remote endpoint at api.anymailfinder.com over streamable HTTP; OAuth authentication is required, so an Anymail Finder account is needed. No environment variables or headers are declared.
Before you install
Email lookups return personal contact data about third parties, so consider privacy and consent rules in your jurisdiction. The listing does not state whether lookups consume paid credits; check the provider's pricing before heavy use.

Installation

In SourceWeft

  1. Open Anymail Finder 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.anymailfinder%2Fmcp-server/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": {
    "anymail-finder": {
      "type": "http",
      "url": "https://api.anymailfinder.com/mcp"
    }
  }
}

README

This repository has no README.

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.2.0LatestNov 5, 2026
  2. v1.1.0Sep 16, 2026

Score

75% 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
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Finder integrations