Skip to content
ProtocolProbe
Explore

MCP servers › io.usefulapi › talenta

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

io.usefulapi/talenta

Talenta 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 ↗

MCP server for Talenta — read employee, attendance, leave, payroll and recruitment data. — the publisher's description

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

Summary

io.usefulapi/talenta is a remote MCP server listed in the official MCP registry at version 1.6.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 5 prompts.

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

13,016 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 (talenta.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.6.0).

Add to your client

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.6.0, published 2026-11-03 (registry, as of the 2026-11-03 snapshot)
First listed version
2026-10-31 (earliest version still in the registry; older removed versions would be earlier)
Version history
8 versions listed, 2026-10-31 to 2026-11-03; 8 in the 90 days before the 2026-11-03 snapshot.
Most recent 8 versions
  • 1.6.0 · 2026-11-03
  • 1.5.1 · 2026-11-03
  • 1.5.0 · 2026-11-02
  • 1.4.0 · 2026-10-31
  • 1.3.0 · 2026-10-31
  • 1.2.0 · 2026-10-31
  • 1.1.0 · 2026-10-31
  • 1.0.1 · 2026-10-31
(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

Version 1.5.0 (published 2026-11-02) → 1.6.0 (published 2026-11-03), between the registry lists of 2026-11-02 and 2026-11-03.

The publisher published no GitHub release note for this version: its repository publishes no GitHub releases.

Source: the official MCP Registry list on 2026-11-02 and on 2026-11-03; release notes from the GitHub Releases API, checked 2026-11-03.

What it is

What does this server offer?

Observed inventory
30tools
0resources
5prompts

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

  • talenta_list_employees

    “List the employees of the company (Talenta Data API v3) with name, employee id, email, branch, organization, job position, employment status, join/resign dates and more.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    15 inputs
    • user_idsarray“Only these Talenta user ids.”
    • emailstring“Only the employee with this email.”
    • branch_idsarray“Only these branch ids (0 = head office).”
    • organization_idsarray“Only these organization ids.”
    • job_position_idsarray“Only these job position ids.”
    • job_level_idinteger“Only this job level id.”
    • employment_status_idinteger“Only this employment status id.”
    • join_start_datestring“Joined on or after (yyyy-mm-dd).”
    • join_end_datestring“Joined on or before (yyyy-mm-dd).”
    • modified_start_datestring“Modified on or after (yyyy-mm-dd).”
    • modified_end_datestring“Modified on or before (yyyy-mm-dd).”
    • order_join_datestring“Sort by join date.”
    • includearray“Extra sub-objects per employee.”
    • pageinteger“Page number, 1-based (default 1).”
    • limitinteger“Results per page, 1-100 (default 10).”
  • talenta_get_employee

    “One employee by Talenta user id: personal data, employment, family, education, payroll info, custom fields and access role.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input, 1 required
    • user_idintegerrequired“Talenta user id (talenta_list_employees: user_id).”
  • talenta_get_employment_info

    “Employment details of one employee (branch, class, grade, job, contract and probation dates, approval line).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    3 inputs
    • user_idinteger“Talenta user id.”
    • employee_idstring“The company's employee id (for example SDET-001).”
    • emailstring“The employee's email.”
  • talenta_list_family_info

    “Family members of one employee (name, relationship, birth date, marital status, ID number).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    4 inputs
    • user_idinteger“Talenta user id.”
    • employee_idstring“The company's employee id.”
    • pageinteger“Page number, 1-based (default 1).”
    • limitinteger“Results per page, 1-100 (default 10).”
  • talenta_list_formal_education

    “Formal education history of one employee (degree, institution, major, years, score).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    4 inputs
    • user_idinteger“Talenta user id.”
    • employee_idstring“The company's employee id.”
    • pageinteger“Page number, 1-based (default 1).”
    • limitinteger“Results per page, 1-100 (default 10).”
  • talenta_get_company_info

    “The company's profile: name, address, phone, email, BPJS and tax numbers.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input
    • company_idinteger“Talenta company id (default: the company of the connected credentials).”
  • talenta_list_branches

    “List the company's branches with address, province and tax details.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    4 inputs
    • company_idinteger“Talenta company id (default: the company of the connected credentials).”
    • include_head_officeboolean“Also return the head office (default false).”
    • pageinteger“Page number, 1-based (default 1).”
    • limitinteger“Results per page, 1-100 (default 10).”
  • talenta_list_organizations

    “List the company's organizations (departments) with parent organization and branch.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    4 inputs
    • company_idinteger“Talenta company id (default: the company of the connected credentials).”
    • searchstring“Filter by organization name.”
    • pageinteger“Page number, 1-based (default 1).”
    • limitinteger“Results per page, 1-100 (default 10).”
  • talenta_list_job_positions

    “List the company's job positions with level, parent position, branch and status.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    7 inputs
    • company_idinteger“Talenta company id (default: the company of the connected credentials).”
    • statusnumber“1 = active, 0 = inactive.”
    • branch_idinteger“Only this branch id.”
    • parent_idinteger“Only children of this job position id.”
    • searchstring“Filter by job position name.”
    • pageinteger“Page number, 1-based (default 1).”
    • limitinteger“Results per page, 1-100 (default 10).”
  • talenta_list_job_levels

    “List the company's job levels with code, status and employee count.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    4 inputs
    • searchstring“Match by job level name or code.”
    • statusnumber“1 = active, 0 = inactive.”
    • pageinteger“Page number, 1-based (default 1).”
    • limitinteger“Results per page, 1-100 (default 10).”
  • talenta_list_employment_statuses

    “List the company's employment statuses (permanent, contract, ...) with ids for employee filters.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    2 inputs
    • pageinteger“Page number, 1-based (default 1).”
    • limitinteger“Results per page, 1-100 (default 10).”
  • talenta_list_time_off_requests

    “Time off (leave) requests of the company in a date range, optionally for one user or one status.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    4 inputs, 2 required
    • start_datestringrequired“Start of the period (yyyy-mm-dd).”
    • end_datestringrequired“End of the period (yyyy-mm-dd).”
    • statusstring“Only this request status.”
    • user_idinteger“Only this Talenta user id.”
Show 18 more tools
  • talenta_time_off_balance_history

    “Per-employee time off balances over a period: beginning balance, taken, adjustment, expired, carry forward, ending balance, per policy.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    5 inputs
    • start_datestring“From this date (yyyy-mm-dd).”
    • end_datestring“To this date (yyyy-mm-dd).”
    • policy_namestring“Only this time off policy (by name).”
    • pageinteger“Page number, 1-based (default 1).”
    • limitinteger“Results per page, 1-100 (default 10).”
  • talenta_time_off_balance_log

    “The log of time off balance changes (requests, adjustments, expiries) per employee and policy.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    5 inputs
    • start_datestring“From this date (yyyy-mm-dd).”
    • end_datestring“To this date (yyyy-mm-dd).”
    • policy_namestring“Only this time off policy (by name).”
    • pageinteger“Page number, 1-based (default 1).”
    • limitinteger“Results per page, 1-100 (default 10).”
  • talenta_attendance_summary

    “The attendance summary of all employees for one day: schedule, shift, clock in/out, breaks, overtime, time off.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    11 inputs, 1 required
    • datestringrequired“The day (yyyy-mm-dd).”
    • branch_idsarray“Only these branch ids.”
    • organization_idsarray“Only these organization ids.”
    • job_level_idsarray“Only these job level ids.”
    • job_position_idsarray“Only these job position ids.”
    • clock_instring“eci = early clock in, lci = late clock in, nci = no clock in.”
    • clock_outstring“eco = early clock out, lco = late clock out, nco = no clock out.”
    • sortstring“Sort field.”
    • orderstring“Sort order.”
    • pageinteger“Page number, 1-based (default 1).”
    • limitinteger“Results per page, 1-100 (default 10).”
  • talenta_list_live_attendance

    “Live attendance records (check-in/out time, location, schedule) of one employee in a date range.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    3 inputs, 3 required
    • user_idintegerrequired“Talenta user id.”
    • start_datestringrequired“From (yyyy-mm-dd).”
    • end_datestringrequired“To (yyyy-mm-dd).”
  • talenta_list_schedules

    “The current work schedule (shift pattern) of each employee, filterable by schedule name, branch and organization.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    5 inputs
    • schedulestring“Only this schedule name.”
    • branch_idsarray“Only these branch ids.”
    • organization_idsarray“Only these organization ids.”
    • pageinteger“Page number, 1-based (default 1).”
    • limitinteger“Results per page, 1-100 (default 10).”
  • talenta_list_overtime_requests

    “Overtime requests in a date range (at most one year), with employee, date, duration, compensation type and status.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    7 inputs, 2 required
    • start_datestringrequired“From (yyyy-mm-dd).”
    • end_datestringrequired“To (yyyy-mm-dd), at most one year after start_date.”
    • user_idsarray“Only requests of these Talenta user ids.”
    • request_statusarray“Only these statuses.”
    • employee_searchstring“Search by employee name or id.”
    • pageinteger“Page number, 1-based (default 1).”
    • limitinteger“Results per page, 1-100 (default 10).”
  • talenta_list_timesheets

    “Company timesheet entries (activity, duration, task, assignee) in a date range.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    4 inputs
    • start_datestring“From (yyyy-mm-dd).”
    • end_datestring“To (yyyy-mm-dd).”
    • pageinteger“Page number, 1-based (default 1).”
    • limitinteger“Results per page, 1-100 (default 10).”
  • talenta_list_payroll_info

    “Payroll setup of the company's employees: tax status (PTKP), NPWP, BPJS numbers, bank account.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    12 inputs
    • statusnumber“0 = active employees, 1 = resigned.”
    • user_idsarray“Only these Talenta user ids.”
    • branch_idsarray“Only these branch ids.”
    • organization_idsarray“Only these organization ids.”
    • job_position_idsarray“Only these job position ids.”
    • employment_status_idsarray“Only these employment status ids.”
    • job_level_idsarray“Only these job level ids.”
    • modified_start_datestring“Modified on or after (yyyy-mm-dd).”
    • modified_end_datestring“Modified on or before (yyyy-mm-dd).”
    • orderstring“Sort direction.”
    • pageinteger“Page number, 1-based (default 1).”
    • limitinteger“Results per page, 1-100 (default 10).”
  • talenta_get_payroll_report

    “Company-wide payroll summary (salary detail) for one month.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    6 inputs, 2 required
    • yearintegerrequired“Year (yyyy).”
    • monthintegerrequired“Month, 1-12.”
    • paymentnumber“Payment method filter, 1 or 2.”
    • branch_idsarray“Only these branch ids.”
    • organization_idsarray“Only these organization ids.”
    • job_level_idsarray“Only these job level ids.”
  • talenta_list_reimbursements

    “Reimbursement requests of the company with employee, policy, amount and approval/disbursement status.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    9 inputs
    • id_employeestring“Only this employee id.”
    • full_namestring“Only employees with this name.”
    • statusstring“Request status.”
    • disbursement_statusstring“Disbursement status.”
    • policy_namestring“Only this reimbursement policy (by name).”
    • start_request_datestring“Requested on or after (yyyy-mm-dd).”
    • end_request_datestring“Requested on or before (yyyy-mm-dd).”
    • pageinteger“Page number, 1-based (default 1).”
    • limitinteger“Results per page, 1-100 (default 10).”
  • talenta_list_reprimands

    “Reprimand letters (SP 1/2/3 or custom) with the employee, dates and status.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    7 inputs
    • start_datestring“Reprimand range start (yyyy-mm-dd).”
    • end_datestring“Reprimand range end (yyyy-mm-dd).”
    • statusnumber“1 = active, 2 = canceled, 3 = expired.”
    • typenumber“1 = SP 1, 2 = SP 2, 3 = SP 3, 99 = custom.”
    • searchstring“Keyword.”
    • pageinteger“Page number, 1-based (default 1).”
    • limitinteger“Results per page, 1-100 (default 10).”
  • talenta_list_employee_transfers

    “Employee transfer and promotion requests with employee, type, effective date and approval status.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    2 inputs
    • pageinteger“Page number, 1-based (default 1).”
    • limitinteger“Results per page, 1-100 (default 10).”
  • talenta_list_delegations

    “Approval/admin/time-off delegations between employees with dates and type.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    7 inputs
    • delegate_fromarray“Only delegations from these user ids.”
    • delegate_toarray“Only delegations to these user ids.”
    • delegation_typestring“Delegation category.”
    • start_datestring“Starting on or after (yyyy-mm-dd).”
    • end_datestring“Ending before (yyyy-mm-dd).”
    • pageinteger“Page number, 1-based (default 1).”
    • limitinteger“Results per page, 1-50 (default 10).”
  • talenta_list_jobs

    “Job openings of the company, newest first.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    6 inputs
    • keywordstring“Search the job alias or id.”
    • branch_idsarray“Only these branch ids.”
    • job_position_idsarray“Only these job position ids.”
    • published_onlyboolean“Only jobs live on the career page.”
    • pageinteger“Page number, 1-based (default 1).”
    • per_pageinteger“Results per page, 1-100 (default 10).”
  • talenta_get_job

    “One job opening in full, with its hiring stages and custom questions.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input, 1 required
    • job_idintegerrequired“Job id (talenta_list_jobs: job_id).”
  • talenta_list_candidates

    “Candidate applications of the company, newest first.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    6 inputs
    • searchstring“Part of the candidate's name.”
    • application_date_startstring“Applied on or after (alone: exactly this date) (yyyy-mm-dd).”
    • application_date_endstring“Applied on or before (yyyy-mm-dd); needs application_date_start.”
    • orderstring“Sort direction (default desc).”
    • pageinteger“Page number, 1-based (default 1).”
    • limitinteger“Results per page, 1-100 (default 10).”
  • talenta_get_candidate

    “One candidate application with personal data, education and work experience.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input, 1 required
    • job_application_idintegerrequired“Application id (talenta_list_candidates: job_application_id).”
  • talenta_list_hiring_stages

    “For each job opening, how many candidates sit in each pipeline phase (screening, assessment, interview, job offer).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    5 inputs
    • branch_idsarray“Only these branch ids.”
    • job_position_idsarray“Only these job position ids.”
    • published_onlyboolean“Only published jobs.”
    • pageinteger“Page number, 1-based (default 1).”
    • per_pageinteger“Results per page, 1-100 (default 10).”

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 155
Tools with a description
100% of 30
Typical description length
159 characters

The tool set

Counted from the listing

Tools
30
Size of the list
about 8,570 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://talenta.usefulapi.io/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "talenta": {
      "url": "https://talenta.usefulapi.io/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "talenta": {
      "type": "http",
      "url": "https://talenta.usefulapi.io/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"talenta","type":"http","url":"https://talenta.usefulapi.io/mcp"}'
Claude Code
claude mcp add --transport http talenta https://talenta.usefulapi.io/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "talenta": {
      "type": "streamableHttp",
      "url": "https://talenta.usefulapi.io/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "talenta": {
      "httpUrl": "https://talenta.usefulapi.io/mcp"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.talenta]
url = "https://talenta.usefulapi.io/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "talenta": {
      "url": "https://talenta.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://talenta.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 saysWe foundResultSource · date
Remote endpoint talenta.usefulapi.io/mcpSession openedmatchesour test · 2026-11-03
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-11-03
Repository github.com/m190/usefulapi-mcpOpens publiclymatchesapi.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-01.

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.

Tool list changes

Our reads compared · no tool called

Hosted endpoint talenta.usefulapi.io/mcp

No change in the tool list across 4 reads (2026-10-31 to 2026-11-03; versions 1.1.0 to 1.6.0).

Compared from the tool lists our read-only connection recorded, separately for each hosted endpoint and each package: each tool's name, title, description, input schema and annotations (the order of keys and of tools is ignored). We see a list only when we read it: a change is shown between the two reads where we first saw it, and anything after 2026-11-03 is not known yet. No tool was called. How it is compared

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-01). 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/talenta

Answered from the data above

Who publishes io.usefulapi/talenta?

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/talenta 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/talenta 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/talenta been security tested?

Partly. 3 of the 16 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. ProtocolProbe publishes no security verdict for a named server.

Does io.usefulapi/talenta 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/talenta?

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

Not probed (we call no server's tools)

We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. 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
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not run · an error was returned
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. 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-list    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning    Looks for hidden instructions in tool descriptions.exercised
  • 18Sign-in metadata
    oauth-url-scheme    Checks the published sign-in metadata for unsafe URLs.exercised
Not run, with the reason · 13
  • 3Real execution
    real-execution    Calls 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-leak    Plants 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
    ssrf    Checks 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-confirmation    Checks 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-handling    Sends 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
    sampling    Checks 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-data    Checks 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-boundary    Checks 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-channel    Checks 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-hiding    Checks 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-turn    Checks 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-redirect    Checks 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-deputy    Checks 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-passthrough    Checks 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-validation    Checks 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.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 226 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 30 tools, 0 resources, 5 prompts.
  4. 1,553 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/talenta: MCP server record.” Data checked 2026-11-03. https://protocolprobe.com/mcp/servers/io.usefulapi/talenta

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: 4 of 5 record checks met

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

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