Company Jobs Finder
app.openkrill/company-jobs · 1.2.0
Open jobs at the companies you name, read straight from their public careers boards.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 45 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://jobs.openkrill.app/mcpstreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 7 tools.
- Protocol
- 2025-06-18
- Calls itself
- company-jobs 1.2.0
- Handshake time
- 337 ms
- HTTP status
- 200
The tools it lists (7, as of 3 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
find_company_jobsFind open jobs at specific companies. Use it for questions like "jobs at Stripe", "is Notion hiring designers?", "remote backend jobs at Ramp and Linear" or "which Spotify jobs list a salary?". Pass company names as the user says them, or careers page links, up to 5 at a time. Covers companies whose careers pages run on Greenhouse, Lever, Ashby, Workable or SmartRecruiters; others come back as not_found. Optional filters: keyword, location, remote, department, postedSince, withSalary. Returns each job's title, locations, workplace type, salary when published, posting date, a short summary and
rank_jobs_for_profileRank the open jobs at up to 3 companies for a person's profile. Use it when the user wants to know which jobs suit them, for questions like "which of these jobs fit a senior backend engineer with 7 years of Go?". Pass companies and the profile the user gave: targetTitles, and where known recentTitles, level, yearsExperience, skills, locations and openToRemote. Every posting is scored on title, level, location and then, for the best ones, skills and years asked. Returns the jobs ranked with a score, a level-fit verdict (match, step_up, stretch, step_down), the reasons it fits and the gaps. A ru
job_fit_briefGet the facts of one job and a checklist for tailoring a resume to it. Use it for questions like "what does the senior backend job at Stripe require?" or "how should I tailor my resume for this role?". Pass company and job (the applyUrl from find_company_jobs, or the title). Returns the posting's must-haves, nice-to-haves, level and the words that signal it, terms to mirror, the years asked, location, process and referral facts it states, and a short tailoring checklist based on general recruiter practice, which is no guarantee of a result. To compare the user's own profile text with a job's k
profile_keyword_checkCompare recruiter keywords and LinkedIn search words with profile text, headline, About or resume. Use it for "does my profile have the right keywords for backend jobs?", "what words am I missing for this job?" or "how do I make my LinkedIn headline findable?". Pass profileText (headline on the first line) and either targetTitles or company and job (the applyUrl or the title). Returns, per role, the title variants, skills, tools and seniority words present or missing, an example boolean search string and whether the text would match it, and short tips for writing the headline and About section
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
app.openkrill/company-jobs, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 4 days ago. The registry entry · tools.openkrill.app