Vendor: https://theirstack.com · entry id 05-theirstack · source 05-signals-intent-abm.md line 544
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 by hand on 2026-09-07. On 2026-09-04 the recorded URL served a documentation page, not an MCP endpoint. That is where to read about the server, not where to connect to it. An agent needs the second.
mcp_status, verbatim from the file:
official
mcp_url, verbatim from the file:
https://api.theirstack.com/mcp/ ; https://theirstack.com/en/job-posting-mcp (also technographics-mcp and buying-intent-mcp at the same domain)
The harvest recorded this server against the cross listing TheirStack in Data & Enrichment. It is the same server, so the list is shown here rather than left blank.
A tool below is one the server NAMES. Nobody has called it. That is the same two tier honesty rule the rest of the directory runs on: a named tool is research, and BENCH-TESTED stays the only claim that anybody ran anything.
141 of the 741 entries that record an official or community MCP server carry a harvested tool list. The other 600 are unmeasured, which is not the same as empty. Harvest last run 2026-09-27. Every name across every server is on the tools index.
No CLI found by the 2026-09-27 harvest across vendor docs, npm, PyPI, Homebrew and GitHub. That is a probe result, not proof of absence.
api_gate, verbatim from the file:
free (limited)
No documentation URL recorded.
727 of 1252 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.
No GitHub organisation could be tied to theirstack.com with evidence on 2026-09-08.
Recorded by the harvest: github candidates were seen but none passed the evidence rules.
1 candidate account seen and rejected by the evidence rules: TheirStack. A name match alone is never accepted; the account has to point at the vendor domain.
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 56 job vocabulary. 271 of 1,252 entries carry at least one tag; 849 tags are assigned in total.
This page is the canonical home. The listing below is the same product, counted separately in the source markdown.
What that listing says it does: A job-postings and technographic-data API that tracks live job listings and the tech stack/hiring signals behind them across 195 countries (claims 223M+ jobs, 352K+ sources), queryable for GTM timing/intent signals.
16 of the 1252 entries are cross listed like this. They are why the entry count is 1252 and the unique product count is 1236. The canonical home is declared in INDEX.md, not chosen by the parser.
4 source URLs. Raw sources field, verbatim:
https://theirstack.com/, https://theirstack.com/en/pricing, https://theirstack.com/en/job-posting-mcp, https://api.theirstack.com/mcp/
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.