accueil / serveurs / Communication / com.timzinin.api/lead-intelligence
com.timzinin.api/lead-intelligence
serveur MCP (Model Context Protocol) · zinin-m2m-hub-lead-intelligence 1.0.0
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que com.timzinin.api/lead-intelligence est sûr ?
Au dernier audit MCP Hub, le serveur MCP « com.timzinin.api/lead-intelligence » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 8 outils
- careers-page-scraper≈ 888 tokens
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).
Paramètres, retour & exemple (4)
Paramètresdomains· array · optionnel
Plain 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 ("https://www.figma.com/careers" is normalized to "figma.com"). Takes priority over 'datasetId' when both are set (by presence, even if every domain in it turns out invalid). Up to 100 domains per run.datasetId· string · optionnel
Pick 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 — is what grants this run's token READ access to that dataset. When this Actor is added as an Integration on another Actor, this field is filled in automatically from the triggering run. Domains are read from whichever field in each row looks like one (companyDomain, domain, website, url, ...).maxConcurrency· integer · optionnel
How many domains to resolve in parallel, 1-20.maxJobsPerCompany· integer · optionnel
Depth 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 board in one call and are never capped by this. Raise it if a company's board is deeper than the default and you need the rest (e.g. a large Workday tenant) — every extra page costs real run time (Workday averages ~1.1s/page). When the cap is reached, or the source's own total is untrustworthy (a proven Workday quirk), a free 'resolved-truncated' row says so explicitly on the dataset — this Actor never silently drops jobs without disclosing it.
Exemple d'appel{"name": "careers-page-scraper", "arguments": {"domains": [], "datasetId": "texte", "maxConcurrency": 1, "maxJobsPerCompany": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - clinic-reception-gap-lead-finder≈ 693 tokens
Analyze submitted clinic websites for reception-channel gaps with exact BYOD crawling and no discovery. — $0.05/call, x402 (USDC on base).
Paramètres, retour & exemple (7)
Paramètresclinics· array · requis
Buyer-submitted clinic websites to analyze.requestId· string · requis
Correlation key for this run.maxResults· integer · optionnel
Maximum useful rows to bill and return.detailLevel· string · optionnel · compact | evidence
Compact or evidence-rich output.minGapScore· integer · optionnel
Minimum score for a useful clinic lead.schemaVersion· string · requis · 1.0
Input schema version.freshnessMinutes· integer · optionnel
Cache freshness window in minutes.
Exemple d'appel{"name": "clinic-reception-gap-lead-finder", "arguments": {"clinics": [], "requestId": "texte", "schemaVersion": "1.0"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - domain-to-verified-work-email≈ 716 tokens
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).
Paramètres, retour & exemple (3)
Paramètrespeople· array · requis
One to 50 people. Each domain must be a bare public company hostname, not a URL.maxConcurrency· integer · optionnel
People processed concurrently only in local non-monetized runs. On-platform source work and paid delivery are sequential.maxPagesPerPerson· integer · optionnel
Number of pages selected from the Actor-owned fixed order: /team, /about, /contact, then /.
Exemple d'appel{"name": "domain-to-verified-work-email", "arguments": {"people": []}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - job-posting-to-hiring-manager-email≈ 1002 tokens
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).
Paramètres, retour & exemple (4)
Paramètresjobs· array · requis
One to 100 vacancies. Give either a direct ATS posting URL, or a company domain plus the exact job title.providerName· string · optionnel · hunter | apollo | prospeo | snov | rocketreach
Which provider your key belongs to. Only meaningful together with a provider API key.maxConcurrency· integer · optionnel
Vacancies 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.providerApiKey· string · optionnel
Your 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.
Exemple d'appel{"name": "job-posting-to-hiring-manager-email", "arguments": {"jobs": []}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - lead-list-cleaner≈ 1090 tokens
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).
Paramètres, retour & exemple (6)
Paramètresitems· array · optionnel
Raw 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 'datasetId' and 'datasetUrl'.checks· array · optionnel
Pipeline 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 for the 'minScore' cutoff.maxRows· integer · optionnel
Safety cap on how many input rows this run will process, regardless of source.minScore· integer · optionnel
Drop leads scoring below this threshold (0-100) from the clean, billed output. They still show up as free rejected rows with a reason.datasetId· string · optionnel
Pick 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 that dataset. When this Actor is added as an Integration on another Actor, this field is filled in automatically from the triggering run.datasetUrl· string · optionnel
Public URL returning a JSON array of lead rows. Used only when both 'items' and 'datasetId' are empty.
Exemple d'appel{"name": "lead-list-cleaner", "arguments": {"items": [], "checks": [], "maxRows": 1, "minScore": 1, "datasetId": "texte", "datasetUrl": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - new-opening-permit-lead-radar≈ 402 tokens
Detect commercial permit and license openings from five fixed Socrata datasets and return evidence-backed signals. — $0.03/call, x402 (USDC on base).
Paramètres, retour & exemple (6)
ParamètresrequestId· string · requis
Correlation key for this run.maxResults· integer · optionnel
Maximum useful rows to bill and return.detailLevel· string · optionnel · compact | evidence
Compact or evidence-rich output.lookbackDays· integer · optionnel
Maximum permit age in days.schemaVersion· string · requis · 1.0
Input schema version.freshnessMinutes· integer · optionnel
Cache freshness window in minutes.
Exemple d'appel{"name": "new-opening-permit-lead-radar", "arguments": {"requestId": "texte", "schemaVersion": "1.0"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - pricing_info≈ 106 tokens
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.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "pricing_info", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - restaurant-booking-gap-lead-finder≈ 705 tokens
Analyze submitted restaurant websites for booking-channel gaps with exact BYOD crawling and no discovery. — $0.05/call, x402 (USDC on base).
Paramètres, retour & exemple (7)
ParamètresrequestId· string · requis
Correlation key for this run.maxResults· integer · optionnel
Maximum useful rows to bill and return.detailLevel· string · optionnel · compact | evidence
Compact or evidence-rich output.minGapScore· integer · optionnel
Minimum score for a useful restaurant lead.restaurants· array · requis
Buyer-submitted restaurant websites to analyze.schemaVersion· string · requis · 1.0
Input schema version.freshnessMinutes· integer · optionnel
Cache freshness window in minutes.
Exemple d'appel{"name": "restaurant-booking-gap-lead-finder", "arguments": {"requestId": "texte", "restaurants": [], "schemaVersion": "1.0"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]}
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».