EDF MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EDF_CDP_PORT | No | Local automation port. | 9335 |
| EDF_DATA_DIR | No | Saved jobs and exports. Defaults to this checkout's `data/` folder. | |
| AHREFS_API_KEY | No | Optional process-environment credential; EDF tools do not need it. | |
| EDF_INSTALL_DIR | Yes | Folder containing the executable and `resources/app.asar`. | |
| EDF_EXPECTED_ASAR_SHA256 | No | Reviewed package hash; see compatibility documentation before changing it. | |
| AHREFS_API_KEY_PROTECTED_FILE | No | Optional Windows DPAPI credential file; see Ahrefs setup documentation. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| edf_statusA | Check the EDF installation, exact inspected package, live connection, and manual UI activity. Does not start the app. |
| edf_launchA | Start EDF with a loopback automation connection, or reuse the exact installed EDF page. Leaves existing manual work intact; reports if EDF must first be closed. |
| edf_get_configurationA | Read the EDF native DNS and WHOIS configuration. Optionally inspect one TLD. Does not change settings. |
| edf_dns_lookupA | Run native EDF batch A-record DNS checks (up to 100 domains). Missing DNS is not proof of domain availability. |
| edf_whois_lookupA | Run the installed EDF WHOIS lookup for one domain. Returns conservative classification, native evidence and optional raw text. No expiry-history or purchase guarantee. |
| edf_check_domainsA | Start one saved background domain-check job (up to 1000 domains), with 1–7 parallel workers (default 7). WHOIS dispatches to the bridge share the configured delay across all workers; only one saved job may run at a time. Returns job ID immediately. Poll edf_get_job; export with edf_export_results. dns_then_whois uses WHOIS only if A DNS does not resolve; whois_all checks every domain through WHOIS. Candidates are provisional. |
| edf_crawl_siteA | Start a bounded EDF crawl of one public website or sitemap, discover external hostnames, and optionally check them. Same-origin page queue, at most 500 pages/1000 domains. Returns job ID; poll edf_get_job. Native regex crawler does not render JavaScript. |
| edf_list_jobsA | List saved EDF automation jobs and their progress. Jobs interrupted by server shutdown are retained. |
| edf_get_jobA | Get saved job progress and paginated result rows. Repeat until completed, cancelled, failed or interrupted. Optional status filter applies to result rows. |
| edf_cancel_jobA | Request cancellation of a job owned by this server. Starts no further lookups and retains all already-started EDF answers before stopping. |
| edf_export_resultsA | Export a saved job to local CSV or JSON and return its absolute path. Optional status filter, e.g. candidate_available. Writes only inside the EDF data exports folder. |
| edf_get_app_resultsB | Read paginated results currently in the manual EDF app UI. EDF native labels are provisional. Automated jobs use edf_get_job instead. |
| edf_ahrefs_domain_ratingA | Get Domain Rating (DR) for up to 1000 public registrable domains using only the official FREE Ahrefs public endpoint. Requires AHREFS_API_KEY in the server environment. Independent of the EDF app; no launch or job is needed. Normalizes URLs/subdomains to ICANN roots. Returns DR, attribution and license; missing metrics are null and DR zero is valid. DR is not DA, PA, traffic, backlink-quality or availability proof. |
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 13 tools
Tools are mostly distinct: direct lookups (edf_dns_lookup, edf_whois_lookup) are separated from background jobs (edf_check_domains), and manual app results (edf_get_app_results) from automated job results (edf_get_job). Some potential overlap remains between edf_check_domains and the direct lookup tools, but descriptions clarify when to use each.
All tools use a consistent edf_ snake_case prefix with predictable verb_noun or noun_verb forms. Minor variations like edf_status and edf_launch are still clear and follow the same prefix convention.
13 tools is well-scoped for an EDF automation/domain-checking server, covering status, launch, config, lookups, job lifecycle, export, and crawl without excessive surface.
The job lifecycle is well covered (start, list, get, cancel, export) alongside direct lookups, config read, crawl, and Ahrefs rating. Minor gaps exist, such as no job deletion/purge and configuration is read-only, but these are likely intentional or workable.