MCP servers › io.github.vinayvobbili › jobwatch
MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23
io.github.vinayvobbili/jobwatch
Watch company job boards, rank new matches and track every application. Never auto-applies. — the publisher's description
Summary
io.github.vinayvobbili/jobwatch is a local MCP server listed in the official MCP registry at version 0.5.0. On 2026-10-23 ProtocolProbe started its published package in an isolated sandbox in read-only mode and read its inventory: 21 tools, 0 resources and 0 prompts.
Record checks
7 of 8 record checks met · 1 does not apply
- met: Registry entry is active and says how to run it
- met: Source repository link opens
- met: Repository is not archived
- met: Code pushed to the repository in the 90 days before our check
- not met: Repository publishes a security policy (SECURITY.md)
- met: Package names its licence with a standard (SPDX) identifier
- met: The version the registry lists can be installed and is not withdrawn
- not applicable: npm package carries build provenance (attestation)
- met: No known critical or high advisory in the package or its dependencies
- #13,207 of 15,112 packages by monthly downloads, tied with 32 others
- Not ranked by stars: 0 stars (ranked from 10)
From public records, not a safety rating. Each check with its reason · Is it safe to install?
Key facts
- Runs
- local package
- Transport
- standard input/output
- Package
- PyPI · listed version current
- License
- MIT
- Dependencies
- no known high or critical advisories
- Repository
- public
- Tools
- 21
- Described as changing data
- 9 of 21 toolsAI-classified
- Mainly works on
- files and code on the machine it runs on; accounts and data in outside web servicesAI-classified
- Topic
- commerce-and-marketingAI-classified
- Last tested
- 2026-10-23
Worth knowing before you connect it
- 9 tools are described as changing something (add_board, remove_board, dismiss_suggested_board, …): our AI model's reading of the descriptions, not something we tested. We did not call them.
Each line comes from a section below, with its source and date.
How fresh this is
- Live-tested
- yes, a real session (not a text-only review)
- Last tested
- 2026-10-23
- Mode
- read-only (no tool calls)
- Latest version
- 0.5.0, published 2026-10-14 (registry, as of the 2026-10-23 snapshot)
- First listed version
- 2026-10-06 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 7 versions listed, 2026-10-06 to 2026-10-14; 7 in the 90 days before the 2026-10-23 snapshot.(versions still listed in the registry only)
Most recent 7 versions
0.5.0· 2026-10-140.4.1· 2026-10-100.4.0· 2026-10-080.3.0· 2026-10-060.2.3· 2026-10-060.2.2· 2026-10-060.2.1· 2026-10-06
- Registry data
- snapshot 2026-10-23
- Package and repository
- checked 2026-10-23
- Engine
- mcp-runtime-engine@0.1.0 · sdk@1.32.0
Changes since the last refresh
New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 0.5.0 (published 2026-10-14).
Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.
What it is
What does this server offer?
Observed inventoryWhat it mainly works on, as our AI model read its tool descriptions: files and code on the machine it runs on; accounts and data in outside web services.
9 of 21 tools are described as changing something (creating, editing, deleting, sending or running).
- find_boardreads or searches
“Find a company's job board by name or by a job/careers link.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
1 input, 1 required
companystringrequired“A company name ("Stripe"), or a link to one of its job postings or its careers page.”
“The boards on the watchlist (entry, display name, careers: the board's own page, careers_link: the company's own careers site when the watchlist gives one) and where the watchlist file is.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
- add_boardcreates or changes datadescribed as changing data
“Add a company's board to the watchlist, so fetch_jobs checks it from now on.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
3 inputs, 1 required
entrystringrequired“The board as source:board, the way find_board and list_boards give it (e.g.”namestring“The company's name as it should show, when the board's own name isn't it (e.g.”careersstring“The company's own careers site (https://...), for a board whose hosted job pages are offline (fetch_jobs warns about those): its jobs then link there.”
- remove_boarddeletesdescribed as changing data
“Take a board off the watchlist, so fetch_jobs stops checking it.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
1 input, 1 required
entrystringrequired“The board as source:board, the way find_board and list_boards give it (e.g.”
- list_suggested_boardsreads or searches
“Companies to watch: those whose jobs came in from job-alert emails (import_job_alerts), add_application or posts in HN's Who is hiring thread (fetch_jobs, when it's watched) while their board isn't o…”
Publisher declares: read-only no · destructive no · idempotent yes · open-world yes
3 inputs
limitinteger or null“The most companies to return, best first.”look_up_boardsboolean“Look for the board of each listed company that hasn't been looked for yet, the way find_board does (once per company; what's found is kept).”rescanboolean“First note the companies of the HN posts already kept (still open) that pass the filters: after the filters change, or for posts fetched before they were noted.”
- dismiss_suggested_boarddeletesdescribed as changing data
“Stop suggesting a company in list_suggested_boards, when the person doesn't want to watch it.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
1 input, 1 required
companystringrequired“The company as list_suggested_boards names it (any case; Inc, LLC and the like aside), or its board.”
“Check every board in the watchlist and record new roles.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world yes
Takes no inputs.
“New jobs that pass the watchlist's filters, best first (fit score when scored, then keyword relevance), with people the user knows at each company.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
4 inputs
score_topinteger“How many of the most relevant unscored jobs to fit-score against the resume with shortlist-ai first.”include_seenboolean“Also include jobs already shown in an earlier digest, not just new ones.”limitinteger or null“The most jobs to return, best first.”mark_shownboolean“Mark the returned jobs as shown, so the next digest leaves them out.”
“Everything about one job, by key or posting id: the full posting text, pay, tracking (status, note, next step, follow-up), its fit score against the resume (score, must-haves met, gaps, and requireme…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
keystringrequired“The job: its key as other tools return it (source:board:posting id, e.g.”
- mark_jobcreates or changes datadescribed as changing data
“Record a job's status: new, shown, queued (to apply to next), applied, screening, interviewing, offer, rejected, withdrawn or skipped (omit status to keep it and only update the rest).”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes
9 inputs, 1 required
keystringrequired“The job: its key as other tools return it (source:board:posting id, e.g.”statusstring or null“The new status; omit to keep it and only update the rest.”notestring or null“Replaces the whole note.”add_notestring or null“A line to add to the note, dated today, keeping what's there ("recruiter replied: onsite only").”next_stepstring or null“What happens next ("recruiter screen Tuesday").”follow_upstring or null“A day: YYYY-MM-DD, or +N for N days from today.”applied_onstring or null“The day applied (YYYY-MM-DD), if not today.”urlstring or null“The link of a job added by hand: its posting, or the company's careers site once the posting is gone.”textstring or null“The posting's text, pasted (found later, or a copy once the posting is gone), so it can be scored and prepped.”
“Add a job jobwatch didn't find (a referral, a recruiter, LinkedIn...), so everything is in one place: an application (only after the person has applied themselves), or status queued for one they're c…”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
9 inputs
companystring“The company; may be left out when url is a job link it can read.”titlestring“The job title; may be left out when url is a job link it can read.”urlstring“A link to the job: Greenhouse, Lever, Ashby, Workable, Workday, Rippling, Google Careers, amazon.jobs, Oracle Recruiting Cloud, SmartRecruiters, Avature or Lin…”statusstring“applied (the default; only once the person has applied themselves), queued for one they're considering, or a later stage such as interviewing.”applied_onstring“The day applied (YYYY-MM-DD), if not today.”notestring or null“A note: who referred them, how they found it...”next_stepstring or null“What happens next ("hiring manager call Friday").”follow_upstring or null“A day: YYYY-MM-DD, or +N for N days from today.”textstring“The posting's text, pasted, when the link can't be read, so it can be scored and prepped.”
- import_job_alertsreads or searchesdescribed as changing data
“Track the jobs in job-alert emails (LinkedIn, Built In, Indeed; other senders with a generic reader).”
Publisher declares: read-only no · destructive no · idempotent yes · open-world yes
3 inputs, 1 required
emailsarrayrequired“The alert emails, one string each: the raw message (RFC822, as a mail connector's raw format gives it; best, since it names the sender) or just its HTML or pla…”follow_linksboolean“Look for each job that passes the filters on the company's own board, and read links robots.txt allows.”dry_runboolean“Say what would be tracked, and record nothing.”
Show 9 more tools
“Every application (applied or a later stage) and where it stands, follow-ups due soonest first; candidate_home is the company's page for checking its status, when it has one (Workday).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
due_onlyboolean“Only those whose follow-up day has come.”
- list_queued_jobsreads or searches
“Jobs queued to apply to, oldest first, with fit scores, notes, people the user knows there (ask them for a referral before applying) and warnings to check first (pay, place, flagged text).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
- check_postingsdescribed as changing data
“Check that the postings of queued jobs and open applications still take applications, and record the ones that closed or came back.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world yes
Takes no inputs.
“Tracked jobs with their tracking fields, newest first, including closed postings.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
statusstring or null“Only jobs with this status; omit for all.”
“Jobs tracked twice: pairs of tracked jobs, open or closed, where the person queued, applied to or skipped one and the other is the same opening (strong: a shared req or posting id, from a title, note…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
strong_onlyboolean“Only pairs that share a req or posting id (the same opening), not the same title alone.”
- save_application_packagecreates or changes datadescribed as changing data
“Keep what was sent with an application, as copies: files (local paths to the resume PDF, cover letter...”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
4 inputs, 1 required
keystringrequired“The job: its key as other tools return it (source:board:posting id, e.g.”filesarray or null“Local paths to the files exactly as uploaded (resume PDF, cover letter...).”answersarray or null“The form's questions and the answers given, as [{"question": ..., "answer": ...}].”notestring or null“A cover letter or message pasted into the form.”
- get_application_packagereads or searches
“What was sent with an application: files kept (with their folder), form answers, note, and the day the posting was saved as it read then (posting.md in the folder).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
keystringrequired“The job: its key as other tools return it (source:board:posting id, e.g.”
- get_interview_prepreads or searches
“A prep sheet for a recruiter call or interview: stage and next step, each requirement and responsibility in the posting next to the closest resume line (quoted, never written), gaps to be honest abou…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
keystringrequired“The job: its key as other tools return it (source:board:posting id, e.g.”draft_answersboolean“Also have jobwatch's own model (the chat's backend) draft 6-10 questions likely for this role, each with the ask it probes and an answer outline built only fro…”
- list_skill_gapsreads or searches
“Skills today's matching jobs and the person's applications ask for, most in demand first, each with on_resume, how many jobs mention it, how many scored jobs list it as a missing must-have, and ways …”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
timelinestring or null“How soon the person wants to close a gap: week, month, quarter or any.”
Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.
How well are its tools described?
Features #4 and #5
How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.
Descriptions
AI reading of each description
- Says what the tool does
- 100% of 21 tools
- Says what it returns
- 71% of 21 tools
- States limits, defaults or errors
- 10% of 20 tools
- Says when to use it
- 100% of 18 tools
- Items covered per tool
- 2.9 of 4 on average
Counted from the listing
- Parameters with a description
- 100% of 46
- Tools with a description
- 100% of 21
- Typical description length
- 638 characters
The tool set
Counted from the listing
- Tools
- 21
- Size of the list
- about 7,763 tokens for an agent to load (characters ÷ 4)
- Naming
- 21 of 21 names use snake_case
AI reading: easy to mix up
No pair found.
The AI items cover 21 of 21 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.
How do I add it to my client?
Config from the registry entry
- No config: the PyPI package declares runtime arguments (options for the runner itself), and the registry documentation gives no rule for where they go.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
Can it be installed, and is it up to date?
Version pin · advisories
Listed version
- Registry lists
- 0.5.0
- Latest stable
- 0.5.0
- Status
- current
- Withdrawn
- no
Source: pypi.org · 2026-10-23. About the version the registry lists; a manual install may resolve to a different one.
Dependency advisories
Counted in the full dependency tree as resolved on 2026-10-23 (OSV.dev). Bars share one scale. The package itself has no known vulnerability (OSV.dev).
Integrity, provenance, license
- Integrity
- sha256-697345aef9d622815…
- License
- MIT
Source: the package registry · 2026-10-23.
Usage
- Downloads
- 110 in the last month
Source: pypistats.org · 2026-10-23.
Does the registry listing match what we found?
Feature #6The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Published package can be started | Started and answered | matches | our test · 2026-10-23 |
| Version 0.5.0 on PyPI | Exists and can be installed | matches | PyPI · 2026-10-23 |
| Repository github.com/vinayvobbili/jobwatch | Opens publicly | matches | api.github.com · 2026-10-23 |
Who made it?
Feature #7 · lineage
Facts about the publisher. We do not turn them into a trust score.
- Namespace
- io.github.vinayvobbili
- GitHub owner
- a personal account (vinayvobbili)
- Repository
- github.com/vinayvobbili/jobwatch
- Stars
- 0
- Repository age
- 0–30 days
- Last push
- 0–30 days ago
- Archived
- no
- Security policy
- none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)
Source: the registry entry and api.github.com · 2026-10-23; security policy read from GitHub · 2026-10-23.
Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.
Choosing
Record checks
Public records · not a safety rating7 of 8 record checks met · 1 does not apply
- #13,207 of 15,112 packages by monthly downloads, tied with 32 others
- Not ranked by stars: 0 stars (ranked from 10)
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- MetSource repository link opensThe linked GitHub repository is public.
- MetRepository is not archivedNot archived.
- MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
- Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.
- MetPackage names its licence with a standard (SPDX) identifierMIT
- MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
- Does not applynpm package carries build provenance (attestation)PyPI packages have no npm-style attestation.
- MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards
Common questions about io.github.vinayvobbili/jobwatch
Answered from the data aboveIs io.github.vinayvobbili/jobwatch safe to install?
We do not rate servers as safe or unsafe. 7 of its 8 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. 9 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.
Has io.github.vinayvobbili/jobwatch been security tested?
Partly. 2 of the 12 checks that apply to it were exercised. We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security verdict is published before verification.
What can io.github.vinayvobbili/jobwatch do?
It lists 21 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search, create or change data and delete. We did not call any tool, so this describes the text, not the behaviour.
Can io.github.vinayvobbili/jobwatch change or delete data?
9 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.
Does io.github.vinayvobbili/jobwatch publish a security policy?
We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.
Is the listed version current?
Yes. The registry lists 0.5.0, the latest stable release on PyPI.
Where is the source code of io.github.vinayvobbili/jobwatch?
In github.com/vinayvobbili/jobwatch, which opens publicly.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Similar servers
Same topic · AI-read
- io.github.LetsFG/letsfgLetsFG — Flights & Hotelsalso has tools that creates or changes data, deletes, reads or searchescompare with this one
- io.github.avansaber/seo-monsteralso has tools that creates or changes data, deletes, reads or searchescompare with this one
- com.getadloop/adloopAdLoopalso has tools that creates or changes data, deletes, reads or searchescompare with this one
- io.github.mgwalkerjr95/texas-groceryalso has tools that creates or changes data, deletes, reads or searchescompare with this one
- io.github.ilyautov/marketplaces-mcp-ruMarketplaces MCP (RU) — Wildberries, Ozon, Yandex Market, Avitoalso has tools that creates or changes data, deletes, reads or searchescompare with this one
- com.mcparmory/apolloalso has tools that creates or changes data, deletes, reads or searchescompare with this one
Active servers whose topic is also “commerce-and-marketing” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
What did we test, and what did we leave out?
18 checks · features #1, #2
Not probed (read-only run)
We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security score is given; a check we did not run is never counted as passed.
- Inventory: exercised
- Hidden instructions: exercised
- Real execution: not run · our policy
- Secret leak: not run · nothing to check it against
- Internal addresses: not run · our policy
- Unconfirmed changes: not run · our policy
- Bad input: not run · our policy
- Model requests: not run · nothing to check it against
- Sensitive questions: not run · nothing to check it against
- Folder boundary: not run · our policy
- Log leaks: not run · nothing to check it against
- Hidden content: not run · nothing to check it against
- Fake assistant turns: not applicable
- Token passthrough: not applicable
- Token audience: not applicable
- Sign-in redirect: not applicable
- Consent handling: not applicable
- Sign-in metadata: not applicable
2 exercised10 not run (reason given)6 not applicable
Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 12 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.
- 1Inventory
tool-listReads the declared tools, resources and prompts.exercised - 2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
- 3Real execution
real-executionCalls a tool and checks what really happens.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy - 4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy - 6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy - 7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy - 8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy - 11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
- 13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable - 14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable - 15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable - 16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable - 17Consent handling
confused-deputyChecks consent handling when one service acts for another.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable - 18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
Source: our own test in an isolated sandbox, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.
What happened during the test?
Feature #8
The steps in order, as the test record holds them.
- 0 msStarted the published package in an isolated sandbox (read-only mode)
- 4,113 msConnected after 0 redirects.
- Read the inventory: 21 tools, 0 resources, 0 prompts.
- 4,632 msFinished: 2 checks exercised.
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “io.github.vinayvobbili/jobwatch: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.vinayvobbili/jobwatch
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/io.github.vinayvobbili/jobwatch)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.
Write to hello@protocolprobe.com · corrections log · methodology