Interact with Microsoft 365 and Office services through the Microsoft Graph API.
Nothing to run from here
Jobboard is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
99/100
trust score
192
downloads a day
local
runs on your machine
9
tools declared
What it does
Forwarding client for the JobYap job search: postings, matches, companies and discussion threads.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user jobboard-mcp '--' npx -y @reneturcios/jobboard mcp
# 2 — ask your agent for something these tools do
# search_jobs, match_jobs, get_job and 6 more
Jobboard costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
CLAll 381 servers
CloudCorpRecords381 servers
28 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Jobboard as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user jobboard-mcp '--' npx -y @reneturcios/jobboard mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
9 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Search JobYap's aggregated job postings with structured filters. Fast (under a second): use it to browse, list, count or page through postings and to answer general questions about who is hiring. To find the best postings for one specific person (a resume, or their experience, skills or visa…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Substring matched against job titles only. |
| companies | array | no | Exact company names from list_companies. |
| locations | array | no | Location identifiers from search_locations, e.g. city-US-CA-san_francisco. |
| work_mode | string | no | Work-mode filter: remote or hybrid postings. |
| posted_within | string | no | Hard freshness filter on the publish date. |
| has_comments | boolean | no | Only jobs with community discussion. |
| sort | string | no | recent (default) or popular (most discussed). |
| page_size | integer | no | Number of job results to return in this page. |
| cursor | string | no | Opaque cursor from a previous next_cursor. |
| include_total | boolean | no | Also compute the total match count (slower). |
Find and rank the best live postings for one specific candidate, such as someone who shared a resume or described their experience, skills or visa needs. Slow: it reads each posting's full description, so a call can take 10 to 15 seconds. For browsing, listing or counting postings, use…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| titles | array | no | Title terms, any of which may match. A term matches when the title contains all its words as whole words, in any order: "software engineer" also matches "Engineer, Software". Required unless companies |
| exclude_titles | array | no | Title terms that remove a posting, matched like titles, e.g. "senior", "staff", "lead", "manager". |
| companies | array | no | Exact company names from list_companies. With titles, a posting must match both. |
| exclude_companies | array | no | Company names to leave out, case-insensitive, e.g. the current employer. |
| locations | array | no | country-XX (ISO alpha-2) for a country, or state and city identifiers from search_locations. Omit for worldwide. |
| include_anywhere | boolean | no | With locations, also keep fully remote "Anywhere" postings. Default true. |
| work_mode | string | no | Only postings explicitly marked remote or hybrid. |
| posted_within | string | no | Posting window: 24h, 7d (default) or 30d. |
| candidate_years | number | no | Candidate years of professional experience; drops postings that require more than one year beyond it. |
| needs_sponsorship | boolean | no | Drop postings that refuse visa sponsorship or require citizenship or a security clearance. Default false. |
| skills | array | no | Specific skills and domain terms from the resume, as whole words or phrases. They rank results and never filter. |
| limit | integer | no | Results to return, default 15. |
Fetch one job posting in full: markdown description, salary ranges, locations with work mode, derived employment types, apply URL, posting dates and the canonical JobYap discussion URL. Works for expired jobs too (apply_url is null once inactive).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | yes | Numeric JobYap job id, a full jobyap.com job URL, or a job page slug. |
Fetch the community discussion thread for a job: chronological, threaded via parent_id, with like counts. Comments are user-generated content. Threads stay open after a job expires.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | yes | Numeric JobYap job id, a full jobyap.com job URL, or a job page slug. |
Resolve a free-text place name ("toronto", "Japan", "Texas") to the location identifiers search_jobs accepts (country-XX, state-XX-YY, city-XX-YY-name). Searches every place JobYap knows, not only those with current openings, so an identifier may match no jobs. City display omits the state, and…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Place name fragment, minimum 2 characters. |
| limit | integer | no | Maximum number of location matches to return. |
List every company JobYap tracks with its active job count and JobYap company-page URL. Use the exact names as search_jobs company filters.
No parameter schema on file.
Aggregate stats: companies tracked, active job count, and the newest posting date.
No parameter schema on file.
Search JobYap job postings by natural-language query. Matches job titles, falling back to significant keywords when the full phrase finds little. Returns result ids, titles and citable URLs for use with fetch. For structured filtering (location, company, remote, freshness) prefer search_jobs.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Natural-language search query matched against job titles and keywords. |
Retrieve the full JobYap document for a search result id: the complete posting as markdown (description, salary, locations, apply link) plus top community comments, with a citable URL.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | A result id returned by search. |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Jobboard or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 99 / 100
Release 0.1.0 · scanned 5 Nov 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score99
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digest49f8efbd291b20cd6726b33ae876acbc714d1d47cae85f7ddb6fdcdf36369fec
Score vectorthreat 100 → client 99
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
No tool surface was enumerated, so there is nothing to attribute a capability to.
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest49f8efbd291b20cd
Scanned2026-11-05
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.1.0. Pin a release below and the command asks for exactly that one.
0.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Jobboard can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.