MCP server · registry snapshot 2026-10-24 · last tested 2026-10-24

io.usefulapi/jet-hr

Read Jet HR employees, absences, clockings, payroll; create, approve, delete leave; create expenses. — the publisher's description

4 of 4 record checks metRead-only · tools listed 2026-10-24version 1.0.0JavaScriptstreamable HTTP33 tools

Summary

io.usefulapi/jet-hr is a remote MCP server listed in the official MCP registry at version 1.0.0. On 2026-10-24 ProtocolProbe connected to it in read-only mode and read its inventory: 33 tools, 0 resources and 1 prompt.

Record checks

4 of 4 record checks met · 4 do not apply · 1 not checked

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 checked: Repository publishes a security policy (SECURITY.md)
not applicable: Package names its licence with a standard (SPDX) identifier
not applicable: The version the registry lists can be installed and is not withdrawn
not applicable: npm package carries build provenance (attestation)
not applicable: No known critical or high advisory in the package or its dependencies

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs: remote (hosted by the publisher)
Transport: streamable HTTP
Sign-in: none needed to open a session
Repository: public
Tools: 33
Last tested: 2026-10-24

Add to your client

Observed fact

This server accepted a session without any credential and lists 4 tools whose name or declaration suggests they change data (jethr_create_absence_request, jethr_update_absence_request, jethr_delete_absence_request, jethr_create_expense). That is our reading of the names; we did not call them. Source: our connection, 2026-10-24.

How fresh this is

Live-tested: yes, a real session (not a text-only review)
Last tested: 2026-10-24
Mode: read-only (no tool calls)
Latest version: 1.0.0, published 2026-10-24 (registry, as of the 2026-10-24 snapshot)
First listed version: 2026-10-24 (earliest version still in the registry; older removed versions would be earlier)
Registry data: snapshot 2026-10-24
Package and repository: checked 2026-10-24
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-23, listed on 2026-10-24 with version 1.0.0 (published 2026-10-24).

Source: the official MCP Registry list on 2026-10-23 and on 2026-10-24.

What it is

What does this server offer?

Observed inventory

33tools

0resources

1prompts

None of its 33 tools are described as changing anything. For 33 the reading was uncertain, so no mark is shown.

jethr_list_employees
“List the company's employees with the full record: name, fiscal code, work and personal email, job title and level, contract kind and dates, annual gross salary (RAL), manager, headquarters and custo…”
Publisher declares: read-only yes
2 inputs
- as_of_datestring“Resolve the employee's data as of this date (yyyy-mm-dd) instead of today.”
- pageinteger“Page number, 1-based (default 1).”
jethr_get_employee
“One employee's full record (contract, salary, manager, headquarters, custom fields).”
Publisher declares: read-only yes
2 inputs, 1 required
- idstringrequired“Employee uuid (from jethr_list_employees).”
- as_of_datestring“Resolve the employee's data as of this date (yyyy-mm-dd) instead of today.”
jethr_list_employee_overviews
“List employees with the lighter overview record: name, fiscal code, work email, job title, contract dates, probation end, manager, headquarters and custom fields (no salary or personal contact data).”
Publisher declares: read-only yes
1 input
- pageinteger“Page number, 1-based (default 1).”
jethr_get_employee_overview
“One employee's overview record (job title, contract dates, manager, headquarters, custom fields).”
Publisher declares: read-only yes
1 input, 1 required
- idstringrequired“Employee uuid (from jethr_list_employee_overviews).”
jethr_list_terminations
“List employee terminations (resignations and dismissals recorded in Jet HR).”
Publisher declares: read-only yes
1 input
- pageinteger“Page number, 1-based (default 1).”
jethr_list_hirings
“List hiring processes (drafts and onboarding in progress), optionally by status (for example INCOMPLETE or COMPLETED).”
Publisher declares: read-only yes
2 inputs
- statusstring“Only hirings in this status.”
- pageinteger“Page number, 1-based (default 1).”
jethr_get_hiring
“One hiring process with its status and data.”
Publisher declares: read-only yes
1 input, 1 required
- idstringrequired“Hiring uuid (from jethr_list_hirings).”
jethr_list_contractors
“List external contractors (collaborators) and their collaborations, optionally filtered by contractor, linked employee or a collaboration date window.”
Publisher declares: read-only yes
5 inputs
- contractor_uuidstring“Only this contractor.”
- employee_uuidstring“Only contractors linked to this employee.”
- collaboration_date_fromstring“Only collaborations overlapping this date or later (yyyy-mm-dd).”
- collaboration_date_tostring“Only collaborations overlapping this date or earlier (yyyy-mm-dd).”
- pageinteger“Page number, 1-based (default 1).”
jethr_get_contractor
“One contractor with their collaborations.”
Publisher declares: read-only yes
1 input, 1 required
- idstringrequired“Contractor uuid (from jethr_list_contractors).”
jethr_list_absence_requests
“List leave, sickness, remote-work and other presence/absence requests with status (APPROVED, REJECTED, PENDING), kind, dates, hours, note and approver.”
Publisher declares: read-only yes
9 inputs
- employeestring“Only this employee (uuid from jethr_list_employees).”
- codenamestring“Request kind codename, e.g.”
- start_date_fromstring“Only requests starting on or after this date (yyyy-mm-dd).”
- start_date_tostring“Only requests starting on or before this date (yyyy-mm-dd).”
- end_date_fromstring“Only requests ending on or after this date (yyyy-mm-dd).”
- end_date_tostring“Only requests ending on or before this date (yyyy-mm-dd).”
- created_fromstring“Only requests created at or after this timestamp.”
- created_tostring“Only requests created at or before this timestamp.”
- pageinteger“Page number, 1-based (default 1).”
jethr_list_absence_policies
“List the company's absence policies with their active request kinds (codename, name, approval and attachment rules) and the employees assigned to each.”
Publisher declares: read-only yes
1 input
- pageinteger“Page number, 1-based (default 1).”
jethr_get_absence_request_kind
“One absence request kind setting: codename, whether it needs approval or a note, whether it can be requested in hours or days, duration limits.”
Publisher declares: read-only yes
1 input, 1 required
- idstringrequired“Request kind uuid (from jethr_list_absence_policies, absence_kinds_settings).”

Show 21 more tools

jethr_list_clockings
“List time-clock events (in, out, work and break start/end, overtime) with employee, timestamp, method (web, mobile, badge, QR code), workplace and location.”
Publisher declares: read-only yes
8 inputs
- employeestring“Only this employee (uuid from jethr_list_employees).”
- kindstring“Only this clocking kind.”
- methodstring“Only this clocking method.”
- clocked_fromstring“Only clockings at or after this timestamp.”
- clocked_tostring“Only clockings at or before this timestamp.”
- created_fromstring“Only clockings created at or after this timestamp.”
- created_tostring“Only clockings created at or before this timestamp.”
- pageinteger“Page number, 1-based (default 1).”
jethr_list_payrolls
“List the company's monthly payrolls (year and month, status and totals).”
Publisher declares: read-only yes
3 inputs
- yearinteger“Payslip year, e.g.”
- monthly_payinteger“Payslip monthly pay: month number 1-12 (13 and 14 for the extra monthly payments, tredicesima and quattordicesima, where the company has them).”
- pageinteger“Page number, 1-based (default 1).”
jethr_list_payslips
“List employee payslips, optionally for one employee, year or month.”
Publisher declares: read-only yes
4 inputs
- employeestring“Only this employee (uuid from jethr_list_employees).”
- yearinteger“Payslip year, e.g.”
- monthly_payinteger“Payslip monthly pay: month number 1-12 (13 and 14 for the extra monthly payments, tredicesima and quattordicesima, where the company has them).”
- pageinteger“Page number, 1-based (default 1).”
jethr_list_bonuses
“List payroll bonuses (employee, payroll month, amount, kind, note), optionally for one employee, year or month.”
Publisher declares: read-only yes
4 inputs
- employeestring“Only this employee (uuid from jethr_list_employees).”
- yearinteger“Payslip year, e.g.”
- monthly_payinteger“Payslip monthly pay: month number 1-12 (13 and 14 for the extra monthly payments, tredicesima and quattordicesima, where the company has them).”
- pageinteger“Page number, 1-based (default 1).”
jethr_list_bonus_kinds
“List the bonus kinds (categories) the company can use in payroll.”
Publisher declares: read-only yes
1 input
- pageinteger“Page number, 1-based (default 1).”
jethr_list_fringe_benefits
“List fringe benefits assigned in payroll (employee, payroll month, amount, kind), optionally for one employee, year or month.”
Publisher declares: read-only yes
4 inputs
- employeestring“Only this employee (uuid from jethr_list_employees).”
- yearinteger“Payslip year, e.g.”
- monthly_payinteger“Payslip monthly pay: month number 1-12 (13 and 14 for the extra monthly payments, tredicesima and quattordicesima, where the company has them).”
- pageinteger“Page number, 1-based (default 1).”
jethr_list_fringe_benefit_kinds
“List the fringe benefit kinds (categories) available in payroll.”
Publisher declares: read-only yes
1 input
- pageinteger“Page number, 1-based (default 1).”
jethr_list_payslip_extra_deductions
“List extra deductions applied to payslips (employee, payroll month, amount, kind), optionally for one employee, year or month.”
Publisher declares: read-only yes
4 inputs
- employeestring“Only this employee (uuid from jethr_list_employees).”
- yearinteger“Payslip year, e.g.”
- monthly_payinteger“Payslip monthly pay: month number 1-12 (13 and 14 for the extra monthly payments, tredicesima and quattordicesima, where the company has them).”
- pageinteger“Page number, 1-based (default 1).”
jethr_list_payslip_extra_deduction_kinds
“List the extra deduction kinds (categories) available on payslips.”
Publisher declares: read-only yes
1 input
- pageinteger“Page number, 1-based (default 1).”
jethr_list_documents
“List documents stored in Jet HR (payslips, contracts and other files): metadata per document, optionally by employee, kind name, payroll period or last-update window.”
Publisher declares: read-only yes
6 inputs
- employeestring“Only this employee (uuid from jethr_list_employees).”
- kind_namestring“Only documents of this kind name.”
- periodstring“Only documents of the payroll of this month (YYYY-MM).”
- updated_afterstring“Only documents updated at or after this timestamp.”
- updated_beforestring“Only documents updated at or before this timestamp.”
- pageinteger“Page number, 1-based (default 1).”
jethr_list_expenses
“List expense reimbursement requests (employee, amount, currency, kind, description, payment date, receipts, status).”
Publisher declares: read-only yes
1 input
- pageinteger“Page number, 1-based (default 1).”
jethr_list_expense_policies
“List the company's expense policies (which expense kinds and limits apply to which employees).”
Publisher declares: read-only yes
1 input
- pageinteger“Page number, 1-based (default 1).”
jethr_list_devices
“List company devices (laptops, phones...) and the employee each is assigned to, optionally by employee or device uuid.”
Publisher declares: read-only yes
3 inputs
- employeestring“Only this employee (uuid from jethr_list_employees).”
- uuidstring“Only this device uuid.”
- pageinteger“Page number, 1-based (default 1).”
jethr_get_device
“One company device with its assignment.”
Publisher declares: read-only yes
1 input, 1 required
- idstringrequired“Device uuid (from jethr_list_devices).”
jethr_list_company_headquarters
“List the company's headquarters (legal and operative sites), optionally by kind.”
Publisher declares: read-only yes
2 inputs
- kindstring“Only legal or only operative headquarters.”
- pageinteger“Page number, 1-based (default 1).”
jethr_list_company_ccnl
“List the national collective labour agreements (CCNL) the company applies.”
Publisher declares: read-only yes
1 input
- pageinteger“Page number, 1-based (default 1).”
jethr_list_trip_refund_policies
“List the company's business-trip daily refund policies (needed as trip_name for trip absence requests).”
Publisher declares: read-only yes
1 input
- pageinteger“Page number, 1-based (default 1).”
jethr_create_absence_request
“Create a leave, sickness, remote-work or other presence/absence request for an employee.”
Publisher declares: read-only no · destructive no · idempotent no
18 inputs, 2 required
- employeestringrequired“Employee uuid (from jethr_list_employees).”
- codenamestringrequired“Request kind codename (from jethr_list_absence_policies), e.g.”
- start_datestring“First day (yyyy-mm-dd).”
- end_datestring“Last day (yyyy-mm-dd); omit for a single day.”
- start_timestring“Start time HH:MM, hourly requests only.”
- time_durationstring“Duration HH:MM, hourly requests only.”
- notestring“Note on the request.”
- send_notificationboolean“Notify the people involved (default false); needs confirm_notification=true.”
- confirm_notificationboolean“Must be true when send_notification is true: the user approved that Jet HR notifies the people involved.”
- sickness_justification_typestring“Sickness only: PUC protocol number or paper certificate.”
- pucstring“Sickness only: the PUC protocol number.”
- assisted_ssnstring“Fiscal code of the assisted person (kinds that need it, e.g.”
- donor_transfusion_center_ssnstring“Donor leave only: fiscal code of the transfusion center.”
- child_ssnstring“Child fiscal code (required for FEEDING, SICKNESS_CHILD_CHILD, SICKNESS_CHILD_INFANT).”
- child_birth_datestring“Child birth date (required for PARENTAL_PATERNAL_MANDATORY_LEAVE).”
- trip_namestring“Trip policy name (required for TRIP_* kinds; see jethr_list_trip_refund_policies).”
- trip_meals_reimbursedboolean“TRIP_* kinds: meals are reimbursed.”
- trip_accommodation_reimbursedboolean“TRIP_* kinds: accommodation is reimbursed.”
jethr_update_absence_request
“Change a presence/absence request: dates, hours, note, or its status (APPROVED, REJECTED, PENDING; give rejection_reason when rejecting).”
Publisher declares: destructive yes
13 inputs, 1 required
- idstringrequired“Request uuid (from jethr_list_absence_requests).”
- statusstring“New status.”
- rejection_reasonstring“Reason shown to the employee when status is REJECTED.”
- start_datestring or null“New first day (yyyy-mm-dd); null clears it.”
- end_datestring or null“New last day (yyyy-mm-dd); null clears it.”
- start_timestring or null“New start time HH:MM, hourly requests only; null clears it.”
- time_durationstring or null“New duration HH:MM, hourly requests only; null clears it.”
- notestring“New note.”
- pucstring“Sickness only: the PUC protocol number.”
- assisted_ssnstring“Fiscal code of the assisted person (kinds that need it, e.g.”
- donor_transfusion_center_ssnstring“Donor leave only: fiscal code of the transfusion center.”
- send_notificationboolean“Notify the people involved (default false); needs confirm_notification=true.”
- confirm_notificationboolean“Must be true when send_notification is true: the user approved that Jet HR notifies the people involved.”
jethr_delete_absence_request
“Permanently delete a presence/absence request (it disappears from the employee's calendar and balance).”
Publisher declares: destructive yes
2 inputs, 2 required
- idstringrequired“Request uuid (from jethr_list_absence_requests).”
- confirmbooleanrequired“Must be true: the user approved permanently deleting this request.”
jethr_create_expense
“Create an expense reimbursement request for an employee (no receipt files; those are uploaded in Jet HR).”
Publisher declares: read-only no · destructive no · idempotent no
14 inputs, 6 required
- employeestringrequired“Employee uuid (from jethr_list_employees).”
- kindstringrequired“Expense kind: FOOD, TRAVELS, KM, TELECOM, HOTELS, DEVICES, SERVICES, OTHER, CUSTOM.”
- descriptionstringrequired“What the expense was for.”
- amountstringrequired“Amount in EUR, e.g.”
- amount_totalstringrequired“Amount in amount_total_currency (equal to amount for EUR).”
- amount_total_currencystring“Currency of amount_total (default EUR).”
- payment_datestringrequired“Date the employee paid (yyyy-mm-dd).”
- subkindstring“Sub-kind of the expense, if the policy has one.”
- notestring“Note.”
- is_billed_to_companyboolean“The expense was billed to the company.”
- car_brandstring“Mileage (KM) only: vehicle make.”
- car_model_seriesstring“Mileage (KM) only: vehicle model and series.”
- car_cost_kmstring“Mileage (KM) only: cost per km in EUR, e.g.”
- car_kminteger“Mileage (KM) only: kilometres driven.”

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-24.

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

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description: 100% of 120
Tools with a description: 100% of 33
Typical description length: 205 characters

The tool set

Counted from the listing

Tools: 33
Size of the list: about 8,232 tokens for an agent to load (characters ÷ 4)
Naming: 33 of 33 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 33 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

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-24 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai

Settings → Connectors → Add custom connector, then paste:
https://jet-hr.usefulapi.io/mcp

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "jet-hr": {
      "url": "https://jet-hr.usefulapi.io/mcp"
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "jet-hr": {
      "type": "http",
      "url": "https://jet-hr.usefulapi.io/mcp"
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"jet-hr","type":"http","url":"https://jet-hr.usefulapi.io/mcp"}'

Claude Code

claude mcp add --transport http jet-hr https://jet-hr.usefulapi.io/mcp

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 --server-url https://jet-hr.usefulapi.io/mcp --transport http

The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

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.

Does the registry listing match what we found?

Feature #6

The 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
Remote endpoint jet-hr.usefulapi.io/mcp	Session opened	matches	our test · 2026-10-24
No credential declared as required	Opened a session without any credential	matches	our test · 2026-10-24
Repository github.com/m190/usefulapi-mcp	Opens publicly	matches	api.github.com · 2026-10-24

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace: io.usefulapi · 409 servers
GitHub owner: a personal account (m190)

Repository: github.com/m190/usefulapi-mcp
Stars: 0
Repository age: 91–180 days
Last push: 0–30 days ago
Archived: no

Source: the registry entry and api.github.com · 2026-10-24.

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 rating

4 of 4 record checks met · 4 do not apply · 1 not checked

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 checkedRepository publishes a security policy (SECURITY.md)We did not read this repository's security policy.
Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-24. 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.usefulapi/jet-hr

Answered from the data above

Is io.usefulapi/jet-hr safe to install?

We do not rate servers as safe or unsafe. 4 of its 4 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. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does io.usefulapi/jet-hr need an API key or sign-in?

It opened a session without any credential on 2026-10-24. The registry entry declares no required credential; no declaration is not a guarantee.

Has io.usefulapi/jet-hr been security tested?

Partly. 3 of the 16 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security verdict is published before verification.

Where is the source code of io.usefulapi/jet-hr?

In github.com/m190/usefulapi-mcp, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A 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.

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

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-24

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 run · an error was returned
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not run · our policy
Consent handling: not testable from outside
Sign-in metadata: exercised

3 exercised13 not run (reason given)2 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 16 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 3

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.exercised

Not run, with the reason · 13

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.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 server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.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 server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.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 returned an error when its prompts were read.not run · an error was returned
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside

Does not apply to this server · 2

14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-10-24, 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 a read-only session with the server's remote endpoint
349 msConnected after 0 redirects. No credential was sent or needed.
Read the inventory: 33 tools, 0 resources, 1 prompt.
1,543 msFinished: 3 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.

TopicAI-classified

pending: added in the weekly update

listed 2026-10-24; not classified yet

Pricing modelAI-classified

pending: added in the weekly update

the website is not read yet

Programming language

JavaScript

api.github.com · 2026-10-24

Hosting type

remote (hosted by the publisher)

registry · 2026-10-24

MCP capability

prompts, tools

our test · 2026-10-24

Transport

streamable HTTP

registry · 2026-10-24

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

does not apply

remote-only server: no package is shipped, so there is no package registry

Freshness

0–30 days

registry updatedAt · 2026-10-24

Lifecycle status

active

registry · 2026-10-24

License class

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Integrity hash

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Signature / provenance

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Dependency advisories

does not apply

ships no package, so there are no dependencies to audit

Popularity

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Publisher signals

owner: a personal account · repository age: 91–180 days · stars: 0–9

api.github.com · 2026-10-24

Maintenance

active

api.github.com · 2026-10-24

Environment

the publisher's infrastructure

where it runs, from the hosting type

“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.usefulapi/jet-hr: MCP server record.” Data checked 2026-10-24. https://protocolprobe.com/mcp/servers/io.usefulapi/jet-hr

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

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.usefulapi/jet-hr)](https://protocolprobe.com/mcp/servers/io.usefulapi/jet-hr)

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