Skip to content
External endpointresponds

apollo-salesforce-mapper

Apollo->Salesforce Lead mapper. No LLM. Strict-fail required fields. PASS/REPAIR/FAIL verdict.

Endpoint URL
https://cf-worker.selbyventurecap.workers.dev/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:00 AM UTC
Check
MCP initialize · 8s limit
Latency
292 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
dev.workers.selbyventurecap.cf-worker/apollo-salesforce-mapper

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
apollo-salesforce-mapper
Version
1.0.0
Capability keys
tools
Tool names
apollo_to_salesforce_lead
Instructions excerpt

Maps Apollo contact payloads to Salesforce Lead objects using deterministic TypeScript rules only — no LLM inference. Covers the full Apollo CSV export: names (pre-split or full_name), phones (cell/phone/mobile/work), address components, email, company, title, website, industry, revenue, headcount, lead source, LinkedIn, and a Description composed from headline/seniority/departments/keywords. Strict-fail on required output fields (FirstName, LastName, Phone). Optional fields are silently omitted when source data is absent or unparseable. PASS fires when all data arrives already clean; REPAIR when normalization was needed. Every call returns a Deterministic Receipt: task_id (UUID), verdict (PASS|REPAIR|FAIL), confidence (0.0–1.0), and a diff[] with one entry per mapped field. Results are SHA-256 idempotency-cached for 24 h — replays served from cache at no cost.

Reported Aug 17, 2026, 05:00 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 140ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 473ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 191ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 292ms