MCP server · registry snapshot 2026-11-03 · last tested 2026-11-03

io.usefulapi/kolay-ik

Kolay IK MCP by usefulapi — the publisher's title

by usefulapi.io · domain (the registry's namespace rule)repository owner on GitHub: m190 (personal account)Source ↗Website ↗

Read employees, leave and payroll; create leave, time records and events in Kolay IK. — the publisher's description

4 of 5 record checks metRead-only · tools listed 2026-11-03version 1.1.0JavaScriptstreamable HTTP30 tools

Summary

io.usefulapi/kolay-ik is a remote MCP server listed in the official MCP registry at version 1.1.0, under the namespace of the domain usefulapi.io. Its linked repository is github.com/m190/usefulapi-mcp; GitHub reports its owner as m190, a personal account. On 2026-11-03 ProtocolProbe connected to it in read-only mode and read its inventory: 30 tools, 0 resources and 1 prompt.

Record checks

4 of 5 record checks met · 4 do 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)
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

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: 1 star (ranked from 10)

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

Operate this server? Correct a fact · README badge · Run the checks yourself

Key facts

Runs: remote (hosted by the publisher)
Transport: streamable HTTP
Your own values: none declared (not a guarantee)
Sign-in: none needed to open a session
Repository: public
Tools: 30
Last tested: 2026-11-03

Tool list size

9,784 tokens on Claude Opus 5.5

Added to every request that loads this server's tools (30 tools). Counted with Anthropic's token counter on 2026-11-03, from the tool list we read on 2026-11-03. Median across 25,738 counted servers: 2,858 tokens. How it is counted

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-03 (kolay-ik.usefulapi.io), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (1.1.0).

Add to your client

Observed fact

This server accepted a session without any credential and lists 8 tools whose name or declaration suggests they change data (kolayik_create_leave, kolayik_create_timelog, kolayik_delete_timelog, kolayik_create_event, kolayik_update_event and 3 more). That is our reading of the names; we did not call them. Source: our connection, 2026-11-03.

How fresh this is

Live-tested

yes, a real session (not a text-only review)

Last tested

2026-11-03

Mode

read-only (no tool calls)

Latest version

1.1.0, published 2026-11-03 (registry, as of the 2026-11-03 snapshot)

First listed version

2026-11-02 (earliest version still in the registry; older removed versions would be earlier)

Version history

3 versions listed, 2026-11-02 to 2026-11-03; 3 in the 90 days before the 2026-11-03 snapshot.

Most recent 3 versions

1.1.0 · 2026-11-03
1.0.1 · 2026-11-03
1.0.0 · 2026-11-02

(versions still listed in the registry only)

Registry data

snapshot 2026-11-03

Package and repository

checked 2026-11-03

Engine

mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; repository link does not open; repository archived; no push in over 365 days. Does not apply: listed version cannot be installed or is withdrawn. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

New in the registry: not in the list of 2026-11-02, listed on 2026-11-03 with version 1.1.0 (published 2026-11-03).

Source: the official MCP Registry list on 2026-11-02 and on 2026-11-03.

What it is

What does this server offer?

Observed inventory

30tools

0resources

1prompts

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

kolayik_get_me
“The Kolay IK user the API token belongs to: id, name, email, work email.”
Publisher declares: read-only yes · destructive no · open-world yes
Takes no inputs.
kolayik_list_people
“List employees (id, first and last name), 60 per page.”
Publisher declares: read-only yes · destructive no · open-world yes
7 inputs
- statusstring“active (default) or terminated.”
- qstring“Search text in first and last name (or the national id number).”
- hired_fromstring“Active people hired on or after this date.”
- hired_tostring“Active people hired on or before this date.”
- terminated_fromstring“Terminated people who left on or after this date.”
- terminated_tostring“Terminated people who left on or before this date.”
- pageinteger“Page number, from 1 (default 1).”
kolayik_get_person
“Full profile of one employee: contact data, employment dates, contract, units, compensation and custom data fields.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- person_idstringrequired“Person id (from kolayik_list_people).”
kolayik_get_person_summary
“Short profile of one employee: name, contact data, current units (company, location, department, position) and manager.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- person_idstringrequired“Person id.”
kolayik_get_person_leave_balances
“Leave entitlement of one employee per leave type: earned, used, carried over and unused days.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- person_idstringrequired“Person id.”
kolayik_list_person_trainings
“Trainings assigned to one employee.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- person_idstringrequired“Person id.”
kolayik_list_person_fields
“The custom data fields a person can have (fieldToken, type, category).”
Publisher declares: read-only yes · destructive no · open-world yes
Takes no inputs.
kolayik_list_units
“The organization tree: unit types (company, branch, department, position ...) and their items with ids.”
Publisher declares: read-only yes · destructive no · open-world yes
Takes no inputs.
kolayik_list_approval_processes
“The approval chains configured in the account (leave, expense and similar), with their steps and approvers.”
Publisher declares: read-only yes · destructive no · open-world yes
2 inputs
- searchstring“Name contains this text.”
- person_idstring“Only chains with this person in a step.”
kolayik_list_leaves
“List leave (time off) records, newest data first as the vendor orders them.”
Publisher declares: read-only yes · destructive no · open-world yes
6 inputs
- statusstring“waiting, approved, rejected or cancelled.”
- start_datestring“Leaves from this date on.”
- end_datestring“Leaves up to this date.”
- person_idstring“Only this person.”
- include_inactive_employeesboolean“Include people who have left (default false).”
- limitinteger“Results per page, 1-100.”
kolayik_get_leave
“One leave record with type, dates, return date, comment, person, replacement person, status and used days.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- leave_idstringrequired“Leave id (from kolayik_list_leaves).”
kolayik_create_leave
“WRITE: records leave for an employee and deducts the used days from their balance.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
6 inputs, 4 required
- person_idstringrequired“The employee taking leave.”
- leave_type_idstringrequired“Leave type id (for example from kolayik_get_person_leave_balances).”
- start_datestringrequired“Start, yyyy-mm-dd hh:mm:ss.”
- end_datestringrequired“End, yyyy-mm-dd hh:mm:ss.”
- commentstring“Note on the leave record.”
- replacement_person_idstring“Colleague covering during the leave.”

Show 18 more tools

kolayik_list_timelogs
“List time records (work hours, overtime) with person, start and end, minutes used, status and type.”
Publisher declares: read-only yes · destructive no · open-world yes
9 inputs
- person_idstring“Only this person.”
- typestring“work or overtime.”
- statusstring“waiting, approved, rejected or cancelled.”
- start_datestring“Records from this date on.”
- end_datestring“Records up to this date.”
- sort_typestring“Sort by startDate (default) or endDate.”
- sort_orderstring“Sort direction (default desc).”
- limitinteger“Results per page, 1-100.”
- pageinteger“Page number, from 1 (default 1).”
kolayik_get_timelog
“One time record by id.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- timelog_idstringrequired“Timelog id (from kolayik_list_timelogs).”
kolayik_create_timelog
“WRITE: adds a time record (work hours or overtime) for an employee.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
6 inputs, 4 required
- person_idstringrequired“The employee.”
- start_datestringrequired“Start, yyyy-mm-dd hh:mm:ss.”
- end_datestringrequired“End, yyyy-mm-dd hh:mm:ss.”
- typestring“work or overtime.”
- statusstringrequired“waiting (goes through the approval process), approved (counts immediately), rejected or cancelled.”
- descriptionstring“Note on the record.”
kolayik_delete_timelog
“WRITE (destructive): permanently deletes one time record.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes
1 input, 1 required
- timelog_idstringrequired“Timelog id to delete.”
kolayik_list_transactions
“List employee transactions (expenses, advance payments, bonuses, overtime pay, deductions) with amount, currency, status, paid flag and items.”
Publisher declares: read-only yes · destructive no · open-world yes
8 inputs
- person_idstring“Only this person.”
- typestring“Transaction type.”
- statusstring“draft, waiting, approved or rejected.”
- paidboolean“true = only paid, false = only unpaid.”
- start_datestring“Transactions from this date on.”
- end_datestring“Transactions up to this date.”
- limitinteger“Results per page, 1-100.”
- pageinteger“Page number, from 1 (default 1).”
kolayik_get_transaction
“One transaction (expense, advance, bonus ...) with its items.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- transaction_idstringrequired“Transaction id (from kolayik_list_transactions).”
kolayik_list_expense_categories
“Expense categories of the account (for example taxi, meals), optionally filtered by title or enabled state.”
Publisher declares: read-only yes · destructive no · open-world yes
2 inputs
- titlestring“Category title contains this text.”
- enabledboolean“true = only enabled categories, false = only disabled.”
kolayik_list_payrolls
“Payroll runs of a year: id, period, number of employees, payslips created, errors and total employer cost.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input
- yearinteger“Year (default: the current year).”
kolayik_get_payroll_sheet
“The full payroll sheet (carsaf bordro) of one payroll run: every employee's gross, net, tax and insurance columns.”
Publisher declares: read-only yes · destructive no · open-world yes
5 inputs, 1 required
- payroll_idstringrequired“Payroll run id (from kolayik_list_payrolls).”
- searchstring“Employee name contains this text.”
- statusarray“Calculation statuses (OR).”
- salary_periodarray“Salary period types (OR).”
- unit_item_idsarray“Groups of unit item ids from kolayik_list_units.”
kolayik_list_events
“List company calendar events (meetings, holidays) with title, start, end and comment.”
Publisher declares: read-only yes · destructive no · open-world yes
5 inputs
- searchstring“Title contains this text.”
- startstring“Events from this date on.”
- endstring“Events up to this date.”
- limitinteger“Results per page, 1-100.”
- pageinteger“Page number, from 1 (default 1).”
kolayik_get_event
“One calendar event.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- event_idstringrequired“Event id (from kolayik_list_events).”
kolayik_create_event
“WRITE: adds an event to the company calendar, visible to the employees who see it.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
4 inputs, 3 required
- titlestringrequired“Event title.”
- startstringrequired“Start, yyyy-mm-dd hh:mm:ss.”
- endstringrequired“End, yyyy-mm-dd hh:mm:ss.”
- commentstring“Event description.”
kolayik_update_event
“WRITE: changes the title, times or comment of a calendar event (the vendor requires title, start and end).”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes
5 inputs, 4 required
- event_idstringrequired“Event id.”
- titlestringrequired“Event title.”
- startstringrequired“Start, yyyy-mm-dd hh:mm:ss.”
- endstringrequired“End, yyyy-mm-dd hh:mm:ss.”
- commentstring“Event description.”
kolayik_delete_event
“WRITE (destructive): permanently deletes one calendar event.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes
1 input, 1 required
- event_idstringrequired“Event id to delete.”
kolayik_list_trainings
“List the trainings defined in the account.”
Publisher declares: read-only yes · destructive no · open-world yes
3 inputs
- searchstring“Title contains this text.”
- limitinteger“Results per page, 1-100.”
- pageinteger“Page number, from 1 (default 1).”
kolayik_get_training
“One training with its details.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- training_idstringrequired“Training id (from kolayik_list_trainings).”
kolayik_create_person
“WRITE: adds a new employee (only first and last name are required).”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
7 inputs, 2 required
- first_namestringrequired“First name.”
- last_namestringrequired“Last name.”
- emailstring“Personal email.”
- work_emailstring“Work email.”
- employment_start_datestring“First day of employment.”
- birthdaystring“Date of birth.”
- data_fieldsarray“Extra data fields as {fieldToken, value}.”
kolayik_update_person
“WRITE: changes basic data of one employee; only the fields you pass change.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes
6 inputs, 1 required
- person_idstringrequired“Person id.”
- first_namestring“First name.”
- last_namestring“Last name.”
- emailstring or null“Personal email; null clears it.”
- work_emailstring or null“Work email; null clears it.”
- data_fieldsarray“Data fields as {fieldToken, value}.”

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-11-03.

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 93
Tools with a description: 100% of 30
Typical description length: 178 characters

The tool set

Counted from the listing

Tools: 30
Size of the list: about 6,470 tokens for an agent to load (characters ÷ 4)
Naming: 30 of 30 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 30 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-11-03 (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://kolay-ik.usefulapi.io/mcp

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

{
  "mcpServers": {
    "kolay-ik": {
      "url": "https://kolay-ik.usefulapi.io/mcp"
    }
  }
}

VS Code · .vscode/mcp.json

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

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

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

Claude Code

claude mcp add --transport http kolay-ik https://kolay-ik.usefulapi.io/mcp

Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)

{
  "mcpServers": {
    "kolay-ik": {
      "type": "streamableHttp",
      "url": "https://kolay-ik.usefulapi.io/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}

Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project

{
  "mcpServers": {
    "kolay-ik": {
      "httpUrl": "https://kolay-ik.usefulapi.io/mcp"
    }
  }
}

OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project

[mcp_servers.kolay-ik]
url = "https://kolay-ik.usefulapi.io/mcp"

Zed · Zed settings file (command: zed: open settings file)

{
  "context_servers": {
    "kolay-ik": {
      "url": "https://kolay-ik.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://kolay-ik.usefulapi.io/mcp --transport http

The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
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; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). 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 checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Remote endpoint kolay-ik.usefulapi.io/mcp	Session opened	matches	our test · 2026-11-03
No credential declared as required	Opened a session without any credential	matches	our test · 2026-11-03
Repository github.com/m190/usefulapi-mcp	Opens publicly	matches	api.github.com · 2026-11-03

Who made it?

Feature #7 · lineage

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

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

Repository: github.com/m190/usefulapi-mcp
Stars: 1
Repository age: 91–180 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-11-03; security policy read from GitHub · 2026-11-03.

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 5 record checks met · 4 do not apply

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: 1 star (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.What changes this check: GitHub's documentation describes adding a SECURITY.md from the repository's security settings: under Reporting, Security policy, Start setup. GitHub: adding a 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-11-03 (security policy 2026-11-03). 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, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about io.usefulapi/kolay-ik

Answered from the data above

Who publishes io.usefulapi/kolay-ik?

The registry ties the namespace io.usefulapi to the domain usefulapi.io; only its owner can publish under it. Its linked repository is github.com/m190/usefulapi-mcp; GitHub reports its owner as m190, a personal account. These are facts from the registry and GitHub, not a rating.

Is io.usefulapi/kolay-ik safe to install?

We do not rate servers as safe or unsafe. 4 of its 5 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/kolay-ik need an API key or sign-in?

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

Has io.usefulapi/kolay-ik 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. ProtocolProbe publishes no security verdict for a named server.

Does io.usefulapi/kolay-ik publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Where is the source code of io.usefulapi/kolay-ik?

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-11-03

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-11-03, 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
317 msConnected after 0 redirects. No credential was sent or needed.
Read the inventory: 30 tools, 0 resources, 1 prompt.
1,341 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-11-03; 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-11-03

Hosting type

remote (hosted by the publisher)

registry · 2026-11-03

MCP capability

prompts, tools

our test · 2026-11-03

Transport

streamable HTTP

registry · 2026-11-03

Required credentials

none declared

registry · 2026-11-03 · 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-11-03

Lifecycle status

active

registry · 2026-11-03

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-11-03

Maintenance

active

api.github.com · 2026-11-03

Environment

the publisher's infrastructure

where it runs, from the hosting type · 2026-11-03

“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/kolay-ik: MCP server record.” Data checked 2026-11-03. https://protocolprobe.com/mcp/servers/io.usefulapi/kolay-ik

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/kolay-ik)](https://protocolprobe.com/mcp/servers/io.usefulapi/kolay-ik)

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