Lead Recorder

com.leadrecorderPublished by leadrecorder.comOfficial publisherv1.0.0Updated Oct 24, 2026

Ask where your website leads came from. Phone taps, forms and bookings, with sources.

VerifiedStreamable HTTPWeb executableData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Remote MCP server from Lead Recorder that lets an assistant answer questions about where a website's leads came from, including phone taps, forms and bookings…

What you can do
  • Answer questions about the origin of website leads.
  • Review phone taps, form submissions and bookings together with their traffic sources.
  • No individual tools are documented, so the exact actions depend on the connected account.
When to use it
Useful when you want to ask an assistant about lead attribution for a website — which channels produced calls, form fills or bookings — instead of opening a dashboard.
Requirements
A remote MCP endpoint at mcp.leadrecorder.com over streamable HTTP; OAuth sign-in is required. No environment variables or headers are declared. A Lead Recorder account with lead data is implied.
Before you install
Access is granted through OAuth to your Lead Recorder account, so the assistant can read your lead and attribution data; review the scopes requested during sign-in. The description does not state whether any tool writes or changes data.

Installation

In SourceWeft

  1. Open Lead Recorder 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/com.leadrecorder%2Flead-recorder/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": {
    "lead-recorder": {
      "type": "http",
      "url": "https://mcp.leadrecorder.com/"
    }
  }
}

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

1
  1. v1.0.0LatestSep 16, 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.