Server definition
- Hash
- sha256:a994c30623648c3c6ce896374974f2891e167d597180686ca1be8c0cfd069362
- What it is
- What a remote MCP server returned when asked what it offers: 2 tools
The blob, as servednamed by its sha256
{
"instructions": null,
"tools": [
{
"description": "Enrich a person's profile with additional data from their email address, name, domain, or LinkedIn URL. Alternative to Apollo people-enrich at 5x lower cost. Returns structured JSON with full contact and professional details.\n\n1. fullName (string) -- first and last name\n2. jobTitle (string) -- current role / position\n3. company (string) -- current employer\n4. linkedin (string) -- LinkedIn profile URL\n5. github (string) -- GitHub profile URL\n6. twitter (string) -- Twitter/X handle\n7. location (string) -- city, state, country\n8. bio (string) -- professional summary\n9. avatar (string) -- profile picture URL\n10. domain (string) -- company domain\n\nExample output: {\"fullName\":\"Jane Smith\",\"jobTitle\":\"VP Engineering\",\"company\":\"Acme Corp\",\"linkedin\":\"https://linkedin.com/in/janesmith\",\"github\":\"https://github.com/janesmith\",\"location\":\"San Francisco, CA\",\"avatar\":\"https://gravatar.com/abc123\",\"domain\":\"acme.com\"}\n\nUse this BEFORE outreach to personalize emails, enrich CRM records, search for people/contacts, or research decision-makers. Essential for sales prospecting, lead qualification, and account mapping. Drop-in replacement for Apollo person enrichment.\n\nDo NOT use for email validation -- use email_verify_address instead. Do NOT use for company data -- use company_enrich_from_domain instead. Do NOT use for social profiles by username -- use social_lookup_profile instead. Do NOT use for finding email addresses -- use email_find_by_name instead.",
"inputSchema": {
"properties": {
"email": {
"description": "Email address to enrich (e.g. [email protected])",
"type": "string"
}
},
"required": [
"email"
],
"type": "object"
},
"name": "person_enrich_from_email",
"outputSchema": null
},
{
"description": "Enrich a person's profile with additional data from their email address, name, domain, or LinkedIn URL. Alternative to Apollo people-enrich at 5x lower cost. Returns structured JSON with full contact and professional details.\n\n1. fullName (string) -- first and last name\n2. jobTitle (string) -- current role / position\n3. company (string) -- current employer\n4. linkedin (string) -- LinkedIn profile URL\n5. github (string) -- GitHub profile URL\n6. twitter (string) -- Twitter/X handle\n7. location (string) -- city, state, country\n8. bio (string) -- professional summary\n9. avatar (string) -- profile picture URL\n10. domain (string) -- company domain\n\nExample output: {\"fullName\":\"Jane Smith\",\"jobTitle\":\"VP Engineering\",\"company\":\"Acme Corp\",\"linkedin\":\"https://linkedin.com/in/janesmith\",\"github\":\"https://github.com/janesmith\",\"location\":\"San Francisco, CA\",\"avatar\":\"https://gravatar.com/abc123\",\"domain\":\"acme.com\"}\n\nUse this BEFORE outreach to personalize emails, enrich CRM records, search for people/contacts, or research decision-makers. Essential for sales prospecting, lead qualification, and account mapping. Drop-in replacement for Apollo person enrichment.\n\nDo NOT use for email validation -- use email_verify_address instead. Do NOT use for company data -- use company_enrich_from_domain instead. Do NOT use for social profiles by username -- use social_lookup_profile instead. Do NOT use for finding email addresses -- use email_find_by_name instead.\n\nPOST variant of person_enrich_from_email -- same params passed as JSON body instead of query string.",
"inputSchema": {
"properties": {
"email": {
"description": "Email address to enrich (e.g. [email protected])",
"type": "string"
}
},
"required": [
"email"
],
"type": "object"
},
"name": "person_enrich_from_email",
"outputSchema": null
}
]
}Verify it yourself
curl -s https://api.teppi.xyz/v1/evidence/sha256:a994c30623648c3c6ce896374974f2891e167d597180686ca1be8c0cfd069362 | sha256sum