Lead Research — MCP

Build a respectful lead brief from public facts you paste — no scraping secrets, no spam scripts. (MCP-oriented tool + prompt pack (read-only first).)

Id: mcp/lead-research · Slug: lead-research · Status: Untested · Untested on this machine — recipe reviewed for safety (no secrets, no destructive commands, no auto-spend). Mark tested after you run it locally.

What is this

MCP for MCP. Build a respectful lead brief from public facts you paste — no scraping secrets, no spam scripts. (MCP-oriented tool + prompt pack (read-only first).)

How this runtime fits

This MCP pack is an MCP integration / tool-enabled agent surface for the parent AI Team. Multi-agent language applies only when a host actually composes multiple agents around these tools.

Parent AI Team: lead-research · What is an AI Team?

What it does

Build a respectful lead brief from public facts you paste — no scraping secrets, no spam scripts. (MCP-oriented tool + prompt pack (read-only first).)

Who for

Builders working on Sales jobs who can run MCP themselves.

Need to run

You will run this locally or on infra you control.
No production credentials in prompts or committed files.
MCP-aware client
Ability to allowlist tools

How to use

Review server_hints.md and implement only allowlisted read-only tools.
Load prompt.md as the client system prompt.
Run one Example in query with tools off; then enable library_search only.
Confirm path allowlist before any file read tool.

Limitations

Not a substitute for professional legal, medical, or investment advice.
Outputs can be wrong; human review required before publish or spend.
Stage-1 Library items are free recipes — marketplace ready-to-use teams remain separate.
Local models may omit sections; re-prompt once if needed.
No harvesting of personal data beyond what the operator pasted.

Test status

Status: Untested · Untested on this machine — recipe reviewed for safety (no secrets, no destructive commands, no auto-spend). Mark tested after you run it locally.

Files

server_hints.md — MCP server/tool design notes
prompt.md — Client system prompt when tools are available

Full prompt / config / code

# MCP pack — Lead Research

## prompt.md (client)
You are a respectful lead-research desk. Goal: brief from public facts the user pasted.

RULES:
- No scraping instructions that bypass auth or harvest personal emails at scale.
- No spam sequences. Suggest one human-sent outreach angle max.
- Separate public fact vs guess.
- Do not store or request secrets.

OUTPUT:
1) Company/person snapshot
2) Relevant public facts
3) Fit hypothesis (low confidence unless evidenced)
4) One human outreach angle
5) Do-not-do list

## server_hints.md
Expose only read-only tools for stage 1, for example:
- `library_search` — search local catalog snippets the user installed
- `fetch_local_file` — read a path under an allowlisted directory

Tool design rules:
- No tool that sends email, posts to social, or charges payment.
- No tool that reads `~/.ssh`, `.env`, or browser cookie DBs.
- Arguments must be schema-validated; reject path traversal.
- Log tool calls for the human operator.

Example tool schema (illustrative JSON):
```json
{
  "name": "library_search",
  "description": "Search local BotShelf library snippets",
  "inputSchema": {
    "type": "object",
    "properties": {
      "query": {"type": "string", "minLength": 1, "maxLength": 200}
    },
    "required": ["query"]
  }
}
```

Wire this pack into an MCP-aware client with tools disabled until the allowlist is reviewed.

Example in

Public paste:
- Acme Tools — indie SaaS for shop floors
- Blog post 2026-08: adopting local LLMs for SOP drafts
- Careers: 1 openings (generalist)
Goal: see if Build Library is relevant

Example out

Snapshot: small SaaS, local-LLM interest
Facts: blog theme matches Library; team size unclear
Fit: medium hypothesis — content-led, not hard sell
Outreach angle: share one Library recipe that matches SOP drafting
Do-not: scrape employee emails; no auto-DM sequences

Model / runtime notes

Protocol-level pack. Prefer read-only tools. Never ship credentials inside MCP configs.

Canonical Team

Parent: lead-research · implementation_id: mcp/lead-research

GitHub source

teams/lead-research/mcp · commit eb87e8e049fdf9908e438305ff827c7b617505b5 · license: free-use-at-own-risk

Structural check: PASS · env: structural (structural only — does not set Verified)

Related Library items

Related marketplace Team pages

Soft thematic links only — not identity merges. Marketplace Teams ≠ Library AI Team records.

Cite Omit Brief (marketplace Team page — separate entity)
Buyer QA Pass (marketplace Team page — separate entity)