MCP.Market

Company Facts MCP server

online · 96% uptime
by groundtruthtools·io.github.groundtruthtools/ats-jobs-mcp·v1.2.0·1 stars

Company data from official sources: new US businesses, registers, tech stack, open jobs, SEC.

A91/100grade A
What users say
No reviews yet
Be the first
Safety scan
A91/100

not scanned yet

Adoption
Growing

1 stars29 downloads/wk

Reviews

Write one

Nobody has reviewed Company Facts yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Company Facts tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Company Facts compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
91/100
higher than 85% of 48,243 servers
Uptime
96%
of our recent checks; the typical remote server answers 100%
Response time
174 ms
faster than 70% of 30,027 servers
GitHub stars
1
more than 65% of 28,706 servers
Downloads a week
29
more than 16% of 12,306 servers with a package

Release history: 2 versions in the registry since 2026-09-13, latest 2026-10-30, typically one every 48 days.

Install Company Facts in Claude Code, Cursor or VS Code

claude mcp add --transport http ats-jobs-mcp https://companyfacts.dev/mcp
Add to Cursor

What the publisher says

From the Company Facts repository's README, as published. We do not edit it. Read it on GitHub

ats-jobs-mcp

<!-- mcp-name: io.github.groundtruthtools/ats-jobs-mcp -->

An MCP server for open job postings, read first-hand from the applicant-tracking system behind a company's careers page. Ask your assistant what Anthropic is hiring for and get the answer from Anthropic's own board, not from a job aggregator's index.

Built on the job board APIs that Greenhouse, Ashby and Lever publish so third parties can build job sites. No scraping, no API key, no account, no personal data.

Why this exists

Those APIs are open, documented, and useless unless you already know the company's board name: that Anthropic's is anthropic, Ramp's is ramp, Mistral's is mistral.ai.

None of the vendors publishes a directory of its customers, and none could, since no vendor knows about the others. Checked 2026-08-24: sitemap.xml on job-boards.greenhouse.io, boards.greenhouse.io, jobs.lever.co and apply.workable.com all 404 or redirect.

So this ships one: 7,479 company boards, every one confirmed against the vendor's own API, each carrying the date it was confirmed.

Three tools

findcompanyboard — which system is a company on?

Give it a company name. Get the system and the board name, plus how many roles were open when the board was last confirmed.

listopenjobs — every open role at one company

Title, department, location, employment type, workplace type, posted date, a parsed salary range where the employer publishes one, and a verify_url pointing at the employer's own advert.

compare_companies — several companies, one schema

The thing no single vendor can do. Companies on Greenhouse and companies on Ashby come back with the same field names, so they can be compared directly. One company failing does not lose the others.

Salaries, parsed, and refused when unclear

Ashby prints pay as "$211.4K - $290.6K". Greenhouse prints it in cents, sometimes as several bands at once. Neither is filterable, so both are turned into numbers:

"salary_min": 211400.0, "salary_max": 290600.0,
"salary_currency": "USD", "salary_text": "$211.4K - $290.6K"

The parser refuses more often than it guesses, deliberately:

quantity and reporting it as annual would be a confident lie.

  • $50 - $80 / hour gives no salary. An hourly rate is a different
  • 600 000 kr gives no salary. kr is Swedish, Norwegian and Danish.
  • 0.5% - 1.75% - Offers Equity gives no salary. Equity is not pay.
  • Bands in two currencies are never spanned into a range that exists nowhere.

salary_text always keeps what the employer actually wrote, so nothing is lost when the parser declines.

Every parsed figure is tested against the employer's own structured baseSalary block, the one published for Google to index — not against a number someone typed into a test.

No personal data

Recruiter names are never returned. Email addresses and phone numbers are removed from job descriptions, because descriptions genuinely carry them and a column of work addresses is a marketing list rather than a job feed.

Unlisted Ashby postings are dropped, because Ashby's documentation says plainly that they should not be shown publicly.

Coverage, stated honestly

Lever is readable but has almost no boards in the directory yet, so name it directly (lever:spotify) or pass its careers URL. Workable has a confirmed endpoint but no adapter yet, so it is not listed at all: a directory entry for something nothing can read is a broken promise.

Use it with no install at all

The server runs remotely. Point any MCP client that speaks Streamable HTTP at the URL and there is nothing to download:

{
  "mcpServers": {
    "ats-jobs": {
      "url": "https://ats-jobs-api.groundtruthtools.workers.dev/mcp"
    }
  }
}

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Company Facts: common questions

Is Company Facts MCP server safe?
Yes, by our scan: it is graded A (91/100). Read the Company Facts safety report
How do I install Company Facts?
It runs remotely at companyfacts.dev. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Company Facts need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Company Facts maintained?
The last commit was 53 days ago (2026-09-13). The latest release is v1.2.0.
Is Company Facts up?
96% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Company Facts compare with other MCP servers?
safety score 91/100 (higher than 85% of 48,243 servers); uptime 96% (of our recent checks; the typical remote server answers 100%); response time 174 ms (faster than 70% of 30,027 servers). Full comparison.