Enrow Mcp
io.enrowPublished by enrow.ioOfficial publisherv1.2.0Updated Oct 24, 2026
Find and verify professional emails and phone numbers via the Enrow API.
Overview
A remote MCP server that lets an assistant find and verify professional email addresses and phone numbers through the Enrow API.
- What you can do
- Enrow MCP connects an assistant to the Enrow API so it can look up and validate professional contact details. According to the registry description, it covers finding and verifying professional emails and phone numbers. The server is hosted remotely at a fixed endpoint and exposes its capabilities as MCP tools, though the specific tool list is not published in the manifest.
- When to use it
- Worth adding when an assistant needs to enrich or check business contact information, such as finding a work email for a person or confirming that an address or number is valid. It is less useful if you only need general web search or personal contact management.
- Requirements
- A remote MCP client that supports streamable HTTP, pointed at the provider's hosted endpoint. Authentication is OAuth and is required, so the user must complete an OAuth sign-in with Enrow. No environment variables, headers, or local packages are declared, but network access to the endpoint is needed.
Installation
In SourceWeft
- Open Enrow Mcp in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- 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.enrow%2Fenrow-mcp/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.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"enrow": {
"type": "http",
"url": "https://mcp.enrow.io/mcp"
}
}
}Tools
0Version history
2- v1.2.0LatestSep 23, 2026
- v1.1.0Sep 16, 2026
Score
56% 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
Publish an icon in the registry entry.
- 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.