Company Enrichment MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| enrich_companyA | Enrich one or more companies from their DOMAIN into a unified record, read live from the company's own public site + public DNS + public ATS JSON (no resold database, no API key). Each record carries: company_name, legal_name_guess, description, industry, founded_year, employee_size_hint, hq_country, logo_url, social_links[], tech_stack[] (fingerprinted), contacts{emails[] with MX deliverability grade, phones[]}, and a live hiring{} block (ATS vendor, open_reqs_count, departments/locations hiring, remote_share, hiring_intensity, newest_posting_at). Records are deduped by canonical domain; thin crawls are flagged (enrichment_status), never fabricated. Input accepts domains ("stripe.com") or bare names ("stripe"). |
| company_hiring_signalA | Return ONLY the live hiring signal for one company — a cheap buying-intent probe that skips the full site crawl. Resolves the company to its applicant-tracking system across 8 ATS platforms (Greenhouse, Lever, Ashby, SmartRecruiters, Workday, Recruitee, Workable, BambooHR) and returns {ats_vendor, ats_token, careers_url, open_reqs_count, departments_hiring[], locations_hiring[], remote_share, hiring_intensity (none/low/med/high), newest_posting_at}. This is the category-unique signal no resold-database enricher carries. Keyless, live from public ATS JSON. |
| check_email_domainA | Grade the email deliverability posture of a domain from its public DNS, keyless and free (no paid verification API). Returns {domain, resolves, has_mx, mx_hosts[], grade}. Grades: B = valid MX present (mailbox existence not probed), D = resolves but no MX (mail unlikely), F = does not resolve. Use before trusting a role inbox or scoring a lead. Accepts a bare domain or an email address (the domain part is used). |
| list_capabilitiesA | Describe the enrichment record schema, the 8 ATS platforms behind the hiring signal, the live/keyless/free-COGS data policy, and the public-business-data-only legal scope. No network call. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a distinct action (probe hiring, describe schema, full enrich, grade email domain), and descriptions explicitly frame the lighter tools as cheap pre-checks versus the full enrich_company crawl. The only residual ambiguity is that company_hiring_signal and check_email_domain surface data already contained inside enrich_company's output, so an agent must judge when the lite path is worth it.
Three of four tools use a clean verb_noun snake_case pattern (list_capabilities, enrich_company, check_email_domain). company_hiring_signal breaks the pattern as a noun phrase, a minor deviation in an otherwise predictable scheme.
Four tools is small but well matched to a focused enrichment server: one meta/help tool, one heavy enrichment call, and two cheap probes. It sits at the lean edge of the 3-15 range, with the two probe tools arguably being extractable features of enrich_company rather than independent capabilities.
The surface covers the core enrichment lifecycle well: schema discovery, full domain-based enrichment with contacts/tech/hiring, plus targeted hiring and email-deliverability probes. Gaps are minor, e.g. no explicit bulk/batch status retrieval or follow-up lookup by a previously returned canonical domain, but agents can work around these by re-calling enrich_company.