Koskamo

Leadhound API MCP

An MCP server for sales prospecting and lead generation that discovers local businesses needing specific services based on Google reviews. It provides verified findings with source evidence, grades purchased contact lists, and offers standing market watches, all billed on delivery with strict spend caps.

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

Leadhound API MCP logo, by leadhoundapiVendor evidenceStreamable HTTPOAuth sign-inEndpoint checked 2026-11-06Operated by leadhoundapi
MCP endpoint (Streamable HTTP)
https://api.leadhoundapi.com/mcp
Vendor documentation

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to leadhoundapi.com ·
  • Passed Endpoint is on the registry namespace domain ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Discover local businesses needing specific services with proof from reviews
  • Grade purchased CSV contact lists for validity and market fit
  • Set up standing watches for new market findings delivered as they appear

Source and maintenance

Vendor evidenceRegistry 0.1.0
mcp-registry: com.leadhoundapi/leadhound@0.1.0Project website

Tools

Reported by the attributed source; not independently observed by Koskamo.

No tool definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 1 answered).

  1. 2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
197 ms
95th percentile latency
197 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 197 ms · metadata changed · refuses unauthenticated initialize (HTTP 401)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http leadhound-api-mcp https://api.leadhoundapi.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add leadhound-api-mcp --url https://api.leadhoundapi.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable leadhound-api-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "leadhound-api-mcp": {
      "url": "https://api.leadhoundapi.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "leadhound-api-mcp": {
      "type": "streamableHttp",
      "url": "https://api.leadhoundapi.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start leadhound-api-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "leadhound-api-mcp": {
      "type": "http",
      "url": "https://api.leadhoundapi.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http leadhound-api-mcp https://api.leadhoundapi.com/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://api.leadhoundapi.com/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "leadhound-api-mcp": {
      "serverUrl": "https://api.leadhoundapi.com/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Leadhound API MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 1,260

Do you run Leadhound API MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing