Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Lead Intelligence

REMOTE · API.TIMZININ.COM · SCANNED SEP 21

Pay-per-call lead intelligence tools with free MCP discovery and x402 payments.

Available components

0 this week 82 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability59
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1869 tokens (~233/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Lead Intelligence MCP server?

Lead Intelligence is a hosted endpoint at https://api.timzinin.com/mcp/lead-intelligence, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.timzinin.com

# add to Claude Code
claude mcp add --transport http com-timzinin-api-lead-intelligence 'https://api.timzinin.com/mcp/lead-intelligence'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-timzinin-api-lead-intelligence": {
      "url": "https://api.timzinin.com/mcp/lead-intelligence"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-timzinin-api-lead-intelligence": {
      "type": "http",
      "url": "https://api.timzinin.com/mcp/lead-intelligence"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-timzinin-api-lead-intelligence]
url = "https://api.timzinin.com/mcp/lead-intelligence"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-timzinin-api-lead-intelligence": {
      "type": "remote",
      "url": "https://api.timzinin.com/mcp/lead-intelligence",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-timzinin-api-lead-intelligence --url 'https://api.timzinin.com/mcp/lead-intelligence' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-timzinin-api-lead-intelligence:
    url: "https://api.timzinin.com/mcp/lead-intelligence"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-timzinin-api-lead-intelligence": {
      "Transport": "http",
      "Url": "https://api.timzinin.com/mcp/lead-intelligence"
    }
  }
}
# add to Vellum
assistant mcp add com-timzinin-api-lead-intelligence -t streamable-http -u 'https://api.timzinin.com/mcp/lead-intelligence'
// mcp.json
{
  "mcpServers": {
    "com-timzinin-api-lead-intelligence": {
      "type": "http",
      "url": "https://api.timzinin.com/mcp/lead-intelligence"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 31 Aug 26 0
    • Stability: 0.97 → pass security
  • 30 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Aug 26 +2
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Aug 26 0
    • Authorization: unverified → partial security
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: pass → fail functional
    • New tool “careers-page-scraper” functional
    • New tool “domain-to-verified-work-email” functional
    • New tool “job-posting-to-hiring-manager-email” functional
    • New tool “lead-list-cleaner” functional
    • Tool “clinic-reception-gap-lead-finder” changed its title: Clinic Reception Gap Lead Finder cosmetic
    • Tool “new-opening-permit-lead-radar” changed its title: New Opening Permit Lead Radar cosmetic
    • Tool “pricing_info” changed its title: Pricing — Lead Intelligence cosmetic
    • Tool “restaurant-booking-gap-lead-finder” changed its title: Restaurant Booking Gap Lead Finder cosmetic
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 2 Aug 26 0
    • Stability: unverified → 0.03 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Sept 2026 · Probed https://api.timzinin.com/mcp/lead-intelligence

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.timzinin.com CN=YE1,O=Let's Encrypt,C=US 27 Jul 2026 25 Oct 2026 ECDSA 256 ECDSA-SHA384 5ef393ac3b7ccb852f589ba8f412cb7232f
SANs: api.timzinin.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.timzinin.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
timzinin.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.timzinin.com/mcp/lead-intelligence Verified 200
http (plaintext) http://api.timzinin.com/mcp/lead-intelligence HTTPS enforced 301 https://api.timzinin.com/mcp/lead-intelligence
MCP tools · 8 exposed · ~1,688 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
careers-page-scraper ~467

Resolve company domains to public Greenhouse, Lever, Ashby, Workable, Rippling, or Workday boards. Get attributed jobs, function and seniority, source evidence, confirmed zero, partial, and unresolved states. — $0.02/call, x402 (USDC on base).

NameTypeReqDescription
datasetIdstringPick another Actor's dataset of companies to resolve instead of typing domains directly (e.g. a company-list scraper's run). Ignored when 'domains' is set. Picking it here — not just pasting the ID —…
domainsarrayPlain company domains — no ATS token needed, this Actor figures out the applicant-tracking system itself (Greenhouse, Lever, Ashby, Workable, Rippling or Workday). Accepts bare domains or full URLs (…
maxConcurrencyintegerHow many domains to resolve in parallel, 1-20.
maxJobsPerCompanyintegerDepth limit for paginated sources (Workday, Rippling) — how many open roles to read per company before stopping. Non-paginated sources (Greenhouse, Lever, Ashby, Workable) already return their whole…

No output schema declared.

No examples provided.

clinic-reception-gap-lead-finder ~143

Analyze submitted clinic websites for reception-channel gaps with exact BYOD crawling and no discovery. — $0.05/call, x402 (USDC on base).

NameTypeReqDescription
clinicsarrayyesBuyer-submitted clinic websites to analyze.
detailLevelstringCompact or evidence-rich output.
freshnessMinutesintegerCache freshness window in minutes.
maxResultsintegerMaximum useful rows to bill and return.
minGapScoreintegerMinimum score for a useful clinic lead.
requestIdstringyesCorrelation key for this run.
schemaVersionstringyesInput schema version.

No output schema declared.

No examples provided.

domain-to-verified-work-email ~172

Find the work email a named person publishes on their own company website, confirmed by a same-document schema.org Person assertion. No pattern guessing, no SMTP probing. $0.01 only when a published match is found; no-match, role mailbox, ambiguous and partial outcomes are free. — $0.02/call, x402 (USDC on base).

NameTypeReqDescription
maxConcurrencyintegerPeople processed concurrently only in local non-monetized runs. On-platform source work and paid delivery are sequential.
maxPagesPerPersonintegerNumber of pages selected from the Actor-owned fixed order: /team, /about, /contact, then /.
peoplearrayyesOne to 50 people. Each domain must be a bare public company hostname, not a URL.

No output schema declared.

No examples provided.

job-posting-to-hiring-manager-email ~230

Turn a Greenhouse or Lever vacancy into the named hiring owner behind it, with a provider-verified work address from your own BYOK enrichment key. You pay $0.02 only for a verified hiring contact; ambiguous company matches, unsupported boards and empty results are free. — $0.02/call, x402 (USDC on base).

NameTypeReqDescription
jobsarrayyesOne to 100 vacancies. Give either a direct ATS posting URL, or a company domain plus the exact job title.
maxConcurrencyintegerVacancies processed concurrently only in local non-monetized runs. On-platform source work and paid delivery are sequential, and Lever pacing stays at one request per second regardless of this value.
providerApiKeystringYour own key, used on your own quota. It is never stored, never logged, never reused across runs and never redistributed. Without it, no owner lookup is attempted and the vacancy returns free.
providerNamestringWhich provider your key belongs to. Only meaningful together with a provider API key.

No output schema declared.

No examples provided.

lead-list-cleaner ~360

Normalize mixed lead rows, deduplicate domains and emails, check DNS/MX evidence, score retained leads, and return every rejection, confidence gap, safe action, and run summary for auditable CRM staging. — $0.02/call, x402 (USDC on base).

NameTypeReqDescription
checksarrayPipeline stages to run, in order. 'dedupe' collapses rows sharing the same domain/email. 'email' verifies syntax + MX. 'domain' verifies the domain is alive. 'score' computes the hotness score used f…
datasetIdstringPick another Actor's dataset to clean (e.g. a Google Maps or lead-scraper run). Ignored when 'items' is set. Picking it here — not just pasting the ID — is what grants this run's token READ access to…
datasetUrlstringPublic URL returning a JSON array of lead rows. Used only when both 'items' and 'datasetId' are empty.
itemsarrayRaw lead rows to clean directly, one object per lead — any shape works (Google Maps scraper export, CSV turned into JSON, anything with an email/website/phone somewhere in it). Takes priority over 'd…
maxRowsintegerSafety cap on how many input rows this run will process, regardless of source.
minScoreintegerDrop leads scoring below this threshold (0-100) from the clean, billed output. They still show up as free rejected rows with a reason.

No output schema declared.

No examples provided.

new-opening-permit-lead-radar ~129

Detect commercial permit and license openings from five fixed Socrata datasets and return evidence-backed signals. — $0.03/call, x402 (USDC on base).

NameTypeReqDescription
detailLevelstringCompact or evidence-rich output.
freshnessMinutesintegerCache freshness window in minutes.
lookbackDaysintegerMaximum permit age in days.
maxResultsintegerMaximum useful rows to bill and return.
requestIdstringyesCorrelation key for this run.
schemaVersionstringyesInput schema version.

No output schema declared.

No examples provided.

pricing_info ~44

Free — list every paid tool in the 'lead-intelligence' bundle with its price, payTo address and network. Call this first if you don't have a wallet ready yet.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

restaurant-booking-gap-lead-finder ~143

Analyze submitted restaurant websites for booking-channel gaps with exact BYOD crawling and no discovery. — $0.05/call, x402 (USDC on base).

NameTypeReqDescription
detailLevelstringCompact or evidence-rich output.
freshnessMinutesintegerCache freshness window in minutes.
maxResultsintegerMaximum useful rows to bill and return.
minGapScoreintegerMinimum score for a useful restaurant lead.
requestIdstringyesCorrelation key for this run.
restaurantsarrayyesBuyer-submitted restaurant websites to analyze.
schemaVersionstringyesInput schema version.

No output schema declared.

No examples provided.

Common questions

What is the Lead Intelligence MCP server?

Lead Intelligence is an MCP server listed in the public MCP registry as com.timzinin.api/lead-intelligence. Pay-per-call lead intelligence tools with free MCP discovery and x402 payments. This page covers its hosted endpoint (https://api.timzinin.com/mcp/lead-intelligence).

Is the Lead Intelligence MCP server safe to use?

Lead Intelligence scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Lead Intelligence MCP server expose?

Lead Intelligence exposes 8 tools: pricing_info, careers-page-scraper, clinic-reception-gap-lead-finder, domain-to-verified-work-email, job-posting-to-hiring-manager-email, and 3 more. Their descriptions and schemas cost roughly 1,688 tokens of context every time the server is loaded.

Does the Lead Intelligence MCP server require authentication?

No. We connected to Lead Intelligence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Lead Intelligence MCP server still maintained?

Lead Intelligence is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.