Vendor: https://www.leadfeeder.com · entry id 05-leadfeeder · source 05-signals-intent-abm.md line 372
The vendor ships and maintains the server itself. A wrapper built by Zapier, Composio or a similar third party does not count as official. The status was established on 2026-08-24 and has not been re-fetched since.
mcp_status, verbatim from the file:
official
mcp_url, verbatim from the file:
https://www.leadfeeder.com/features/mcp-server/ ; docs: https://docs.leadfeeder.com/api/public/connect-your-ai-tool-370534m0
api_gate, verbatim from the file:
free (limited)
No documentation URL recorded.
263 of 293 entries are in the same position. Blank is legal and it is published as blank.
Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build.
The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale.
A github.com URL already appears somewhere in this entry, which is a seed for that rail and not a measurement of repo health:
A job tag means the vendor says the tool does this. It is not a test result, not proof the capability is reachable through the tool's MCP server, and not proof it is available on the gate this entry records.
Tagged by machine-pass on 2026-08-25 against the closed 55 job vocabulary. 271 of 293 entries carry at least one tag; 827 tags are assigned in total.
5 source URLs. Raw sources field, verbatim:
https://www.leadfeeder.com/features/mcp-server/, https://docs.leadfeeder.com/api/public/connect-your-ai-tool-370534m0, https://www.leadfeeder.com/pricing/, https://mcp.pipedream.com/app/leadfeeder, https://github.com/ever-works/awesome-mcp-servers/blob/master/details/leadfeeder-mcp-server.md
Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the methodology page.