Jisr MCP by usefulapi
REMOTE · JISR.USEFULAPI.IO
Read employees, attendance, leave and payroll; create employee records and import device punches.
Available components
Last scanned (3 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Productivity and Notes
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Nov 26 −47
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Stability: 0.03 → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 1 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 64
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://jisr.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of jisr.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://jisr.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/jisr/ |
| http (plaintext) | http://jisr.usefulapi.io/mcp | Inconclusive | 302 | http://jisr.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
jisr_create_attendance_punches Import attendance punches ~93
WRITE: send a batch of raw clock-in/out punches (at most 100) from a punch device into Jisr attendance. Jisr processes them asynchronously; check the result with jisr_list_attendance_punches. Each punch carries the unique id its device generated; do not invent ids. POST /openapi/v1/attendance_logs.
| Name | Type | Req | Description |
|---|---|---|---|
| punches | array | yes | – |
No output schema declared.
No examples provided.
jisr_create_employee Create employee ~323
WRITE: register a new employee in Jisr (they are invited to the system by email). Not reversible through this server: there is no delete tool. Get department_id, employment_type_id, location_id and nationality_id from jisr_list_lookup first. Names need at least two parts. POST /openapi/v1/employees.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Employee code, unique within the organization. |
| contract_end_date | string | – | Contract end date (yyyy-mm-dd), for fixed-term contracts. |
| contract_period | string | yes | Contract period. |
| contract_type | string | yes | Contract type. |
| department_id | integer | yes | Department id (jisr_list_lookup departments). |
| document_number | string | yes | National ID or Iqama number. |
| string | yes | Work email. | |
| employment_type_id | integer | yes | Employment type id (jisr_list_lookup employment_types). |
| full_name_ar | string | yes | Full name in Arabic (at least two words). |
| full_name_en | string | yes | Full name in English (at least two words). |
| gender | string | yes | – |
| joining_date | string | yes | Joining date (yyyy-mm-dd). |
| location_id | integer | yes | Location id (jisr_list_lookup locations). |
| marital_status | string | yes | – |
| nationality_id | integer | yes | Nationality id (jisr_list_lookup nationalities). |
| outsourcing_company_id | integer | – | Outsourcing company id, for outsourced staff. |
| personal_email | string | – | Personal email (unique among active employees). |
No output schema declared.
No examples provided.
jisr_get_annual_leave_balances Get annual leave balances ~135
Annual leave balance summaries per employee (all employees, or only the given employee codes, at most 100). Only the annual leave type is supported by Jisr. GET /openapi/v1/employee_leaves/summary.
| Name | Type | Req | Description |
|---|---|---|---|
| employee_codes | array | – | Employee codes (not ids) to include; omit for everyone. |
| limit | integer | – | Results per page, 1-100 (Jisr's default is 100). Sent as `limit`. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
jisr_get_employee Get employee ~90
One employee's profile by id (UUID from jisr_list_employees): names, code, gender, marital status, phone, emails, date of birth, passport/ID number, address, line manager, department, business unit, employment type, location, nationality and contract. GET /openapi/v1/employees/basic_info?id=.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Employee id (UUID). |
No output schema declared.
No examples provided.
jisr_get_employee_financial_info Get employee financial info ~73
One employee's financial details by id: salary components and bank account (IBAN). Sensitive payroll data; needs the 'Get Employee Financial Info' permission on the API key. GET /openapi/v1/employees/financial_info?id=.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Employee id (UUID). |
No output schema declared.
No examples provided.
jisr_get_employee_monthly_payables Get employee monthly payables ~97
One employee's payables for a month: net salary, earnings, additions and deductions with breakdowns. Only available to organizations Jisr has whitelisted for this API. Sensitive payroll data. GET /openapi/v1/employee_monthly_payables.
| Name | Type | Req | Description |
|---|---|---|---|
| employee_id | string | yes | Employee id (UUID). |
| pay_period_start | string | yes | First day of the month (yyyy-mm-01). |
No output schema declared.
No examples provided.
jisr_list_accrual_transactions List accrual transactions ~177
Accruals per employee for a confirmed pay period: vacations, end_of_service or tickets_provision (amount, vacation days). Sensitive payroll data. GET /openapi/v1/accrual_transactions.
| Name | Type | Req | Description |
|---|---|---|---|
| accrual_type | string | yes | Accrual type. |
| employee_ids | array | – | Only these employees (UUIDs). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| pay_period | string | yes | First day of a confirmed month (yyyy-mm-01). |
| paygroup_id | string | yes | Pay group id (UUID, jisr_list_paygroups). |
| rpp | integer | – | Results per page, 1-100 (Jisr's default is 100). Sent as `rpp`. |
No output schema declared.
No examples provided.
jisr_list_attendance_punches List attendance punches ~194
List raw clock-in/out punches that were received from punch devices, either the ones that were processed successfully or the ones that failed, in a time window (Jisr's default: the last hour). Each punch has id, punch_time, employee_code, terminal_sn and clocking_id. GET /openapi/v1/attendance_logs.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Window start, yyyy-mm-dd hh:mm:ss. Default: one hour ago. |
| limit | integer | – | Results per page, 1-100 (Jisr's default is 100). Sent as `limit`. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| status | string | yes | Which punches: processed successfully, or failed. |
| to | string | – | Window end, yyyy-mm-dd hh:mm:ss. Default: now. |
No output schema declared.
No examples provided.
jisr_list_attendance_summary List attendance summary ~184
Attendance summary per employee for a date range (default: the current month): total working hours, late arrival, early departure, extra and approved overtime, absence days and records. Filter by one employee or by active/inactive status. GET /openapi/v1/attendance/summary.
| Name | Type | Req | Description |
|---|---|---|---|
| employee_id | string | – | Only this employee (UUID). |
| from | string | – | Period start (yyyy-mm-dd). Default: start of the current month. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| rpp | integer | – | Results per page, 1-100 (Jisr's default is 100). Sent as `rpp`. |
| status | string | – | Only active or inactive employees. |
| to | string | – | Period end (yyyy-mm-dd). |
No output schema declared.
No examples provided.
jisr_list_audit_events List audit events ~216
The organization's audit trail: who did what and when (module, feature, action, actor, success). Filter by module, event name, event type and a time range. GET /openapi/v1/audit_events.
| Name | Type | Req | Description |
|---|---|---|---|
| event_name | array | – | Event names, e.g. login. |
| event_type | array | – | Event types, e.g. updated. |
| from | string | – | Only events created at or after this ISO 8601 date-time, e.g. 2026-10-01T00:00:00Z. |
| module_name | array | – | Module names, e.g. security. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-100 (Jisr's default is 100). Sent as `per_page`. |
| to | string | – | Only events created at or before this ISO 8601 date-time. |
No output schema declared.
No examples provided.
jisr_list_employees List employees ~311
List the organization's employees (active by default) with code, names (English/Arabic), job title, department, business unit, employment type, line manager, joining date and status. Filter by active/inactive status, creation date and joining, termination or deletion date ranges. If the API key also has the 'Get Employee Financial Info' / 'Accounting Info' permissions, Jisr adds salary, bank (IBAN) and accounting fields: sensitive HR data. GET /openapi/v1/employees.
| Name | Type | Req | Description |
|---|---|---|---|
| created_from | string | – | Only employees created on or after this date (yyyy-mm-dd). |
| deleted_from | string | – | Only employees deleted from the system on or after this date. |
| deleted_to | string | – | Only employees deleted from the system on or before this date. |
| joining_from | string | – | Only employees who joined on or after this date. |
| joining_to | string | – | Only employees who joined on or before this date. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| rpp | integer | – | Results per page, 1-100 (Jisr's default is 100). Sent as `rpp`. |
| status | string | – | Only active or only inactive employees. |
| terminated_from | string | – | Only employees off-boarded on or after this date. |
| terminated_to | string | – | Only employees off-boarded on or before this date. |
No output schema declared.
No examples provided.
jisr_list_gl_transaction_types List transaction types ~116
List the payroll (GL) transaction types: id, category (allowances, loan types...), English/Arabic name and status. Use the ids to filter jisr_list_payroll_transactions. GET /openapi/v1/gl_transaction_types.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| rpp | integer | – | Results per page, 1-100 (Jisr's default is 100). Sent as `rpp`. |
No output schema declared.
No examples provided.
jisr_list_lookup List lookup values ~129
List one of the organization's lookup tables: departments, employment_types, business_units, locations, nationalities or outsourcing_companies, with their ids and English/Arabic names. Use the ids when creating an employee. GET /openapi/v1/lookups/{table}.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| rpp | integer | – | Results per page, 1-100 (Jisr's default is 100). Sent as `rpp`. |
| table | string | yes | Which lookup table. |
No output schema declared.
No examples provided.
jisr_list_paygroups List pay groups ~99
List the organization's pay groups (id and name). The pay group id is needed for payroll and accrual queries. GET /openapi/v1/paygroups.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| rpp | integer | – | Results per page, 1-100 (Jisr's default is 100). Sent as `rpp`. |
No output schema declared.
No examples provided.
jisr_list_payroll_transactions List payroll transactions ~283
Payroll transactions per employee for one settlement type. type 'payrun' (the regular payroll) needs pay_period and paygroup_id; 'final_settlements', 'vacations_settlements' and 'out_off_payroll_transactions' need a from/to date range. Optionally filter by employee ids or transaction type ids (jisr_list_gl_transaction_types). Sensitive payroll data. GET /openapi/v1/payroll_transactions.
| Name | Type | Req | Description |
|---|---|---|---|
| employee_ids | array | – | Only these employees (UUIDs). |
| from | string | – | Start date (yyyy-mm-dd). Required for the other types. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| pay_period | string | – | First day of a confirmed month (yyyy-mm-01). Required for type payrun. |
| paygroup_id | string | – | Pay group id (UUID, jisr_list_paygroups). Required for type payrun. |
| rpp | integer | – | Results per page, 1-100 (Jisr's default is 100). Sent as `rpp`. |
| to | string | – | End date (yyyy-mm-dd). Required for the other types. |
| transaction_type_ids | array | – | Only these transaction types (UUIDs). |
| type | string | yes | Which settlement. |
No output schema declared.
No examples provided.
jisr_list_webhooks List webhooks ~73
List the webhooks registered for the organization: name, endpoint host, method, status. Authentication data, custom header values and the endpoint's path and query (they can hold secrets) are hidden. Read-only; this server does not create or change webhooks. GET /openapi/v1/webhooks.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Jisr MCP by usefulapi server?
Jisr MCP by usefulapi is a hosted endpoint at https://jisr.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · jisr.usefulapi.io
claude mcp add --transport http io-usefulapi-jisr 'https://jisr.usefulapi.io/mcp'
What is the Jisr MCP by usefulapi server?
Jisr MCP by usefulapi is listed in the public MCP registry as io.usefulapi/jisr. Read employees, attendance, leave and payroll; create employee records and import device punches. This page covers its hosted endpoint (https://jisr.usefulapi.io/mcp).
Is the Jisr MCP by usefulapi server safe to use?
Jisr MCP by usefulapi scores 18 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Jisr MCP by usefulapi server expose?
Jisr MCP by usefulapi exposes 16 tools: jisr_list_employees, jisr_get_employee, jisr_get_employee_financial_info, jisr_list_lookup, jisr_list_attendance_summary, and 11 more. Their descriptions and schemas cost roughly 2,593 tokens of context every time the server is loaded.
Does the Jisr MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Jisr MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Jisr MCP by usefulapi server still maintained?
Jisr MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Jisr MCP by usefulapi server?
VerifyMCP ran 4 checks on Jisr MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about Jisr MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.