Prospectr

io.github.kanecr-cmdPublished by GitHub account kanecr-cmdv0.5.3Updated Nov 8, 2026

Public-record buying signals and prospect research for US field sales reps.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP server for prospect research and public-record buying signals aimed at US field sales reps.

What you can do
  • The listing gives no tool list, instructions or README, so only its stated purpose is known.
  • It is described as providing public-record buying signals and prospect research for US field sales reps.
  • An assistant connecting to it would be expected to surface prospect and buying-signal information for sales work, but the specific actions available are not documented in the supplied material.
When to use it
Consider it if you do field sales in the US and want an assistant to help with prospect research or buying signals drawn from public records. Without a documented tool list, verify its actual capabilities before relying on it.
Requirements
A remote streamable HTTP endpoint; no local package or runtime is needed. Authentication is OAuth and is required, so you need an account with the provider and a client that supports OAuth for remote MCP servers.
Before you install
It handles prospect and public-record data about people and companies, which may raise privacy and compliance considerations for your use. The tool list is undocumented, so what it can read or change is unclear; review the provider's terms and data handling before connecting.

Installation

In SourceWeft

  1. Open Prospectr 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.kanecr-cmd%2Fprospectr/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": {
    "prospectr": {
      "type": "http",
      "url": "https://prospectr-mcp.kanecr.workers.dev/mcp"
    }
  }
}

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. v0.5.3LatestNov 8, 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.