Skip to content
ProtocolProbe
Explore

MCP servers › io.usefulapi › teamleader-focus

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

io.usefulapi/teamleader-focus

Read Teamleader Focus contacts, companies, deals, invoices, projects; create deals, tasks. — the publisher's description

4 of 4 record checks metRead-only · tools listed 2026-10-24version 1.5.0JavaScriptstreamable HTTP36 tools

Summary

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

Record checks

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

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • not checked: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies

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

Key facts

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

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 (teamleader_create_contact, teamleader_create_company, teamleader_create_deal, teamleader_create_task, teamleader_add_note and 3 more). That is our reading of the names; we did not call them. Source: our connection, 2026-10-24.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-10-24
Mode
read-only (no tool calls)
Latest version
1.5.0, published 2026-10-24 (registry, as of the 2026-10-24 snapshot)
First listed version
2026-10-23 (earliest version still in the registry; older removed versions would be earlier)
Version history
4 versions listed, 2026-10-23 to 2026-10-24; 4 in the 90 days before the 2026-10-24 snapshot.
Most recent 4 versions
  • 1.5.0 · 2026-10-24
  • 1.4.0 · 2026-10-24
  • 1.3.0 · 2026-10-24
  • 1.0.0 · 2026-10-23
(versions still listed in the registry only)
Registry data
snapshot 2026-10-24
Package and repository
checked 2026-10-24
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-23, listed on 2026-10-24 with version 1.5.0 (published 2026-10-24).

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

What it is

What does this server offer?

Observed inventory
36tools
0resources
1prompts

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

  • teamleader_get_current_user

    “Fetch the Teamleader user the sign-in belongs to: name, email, account id, language, time zone and teams.”

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

    Takes no inputs.

  • teamleader_list_users

    “List the users (colleagues) in the Teamleader account.”

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

    4 inputs
    • termstring“Search first name, last name, email and function.”
    • statusarray“Filter by status.”
    • page_sizeinteger“Page size, 1-100 (Teamleader default 20).”
    • pageinteger“Page number, starting at 1.”
  • teamleader_list_contacts

    “List or search contacts (people).”

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

    10 inputs
    • termstring“Search first name, last name, email and telephone.”
    • emailstring“Exact primary email address.”
    • company_idstring“Only contacts linked to this company id.”
    • tagsarray“Only contacts carrying ALL of these tags.”
    • statusstring
    • updated_sincestring“Only contacts updated since (ISO 8601 with offset, e.g.”
    • sort_fieldstring
    • sort_orderstring“Sort order.”
    • page_sizeinteger“Page size, 1-100 (Teamleader default 20).”
    • pageinteger“Page number, starting at 1.”
  • teamleader_get_contact

    “Fetch one contact in full: emails, telephones, addresses, linked companies (with position), tags, custom fields and remarks.”

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

    1 input, 1 required
    • contact_idstringrequired“The contact id (a UUID).”
  • teamleader_list_companies

    “List or search companies (organisations).”

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

    10 inputs
    • termstring“Search name, VAT number, emails and telephones.”
    • emailstring“Exact primary email address.”
    • vat_numberstring“Exact VAT number, e.g.”
    • tagsarray“Only companies carrying these tag names.”
    • statusstring
    • updated_sincestring“Only companies updated since (ISO 8601 with offset, e.g.”
    • sort_fieldstring
    • sort_orderstring“Sort order.”
    • page_sizeinteger“Page size, 1-100 (Teamleader default 20).”
    • pageinteger“Page number, starting at 1.”
  • teamleader_get_company

    “Fetch one company in full: addresses, VAT number, responsible user, related contacts and companies, tags, custom fields and remarks.”

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

    1 input, 1 required
    • company_idstringrequired“The company id (a UUID).”
  • teamleader_list_deals

    “List or search deals (sales opportunities).”

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

    14 inputs
    • termstring“Search term.”
    • customer_typestring“With customer_id: the customer's type.”
    • customer_idstring“Only deals for this contact/company id.”
    • phase_idstring“Only deals in this phase.”
    • pipeline_idsarray“Only deals in these pipelines.”
    • statusarray“Deal statuses.”
    • responsible_user_idstring“Only deals this user is responsible for.”
    • estimated_closing_date_fromstring“Expected closing date from (YYYY-MM-DD).”
    • estimated_closing_date_untilstring“Expected closing date until (YYYY-MM-DD).”
    • updated_sincestring“Only deals updated since (ISO 8601 with offset, e.g.”
    • sort_fieldstring
    • sort_orderstring“Sort order.”
    • page_sizeinteger“Page size, 1-100 (Teamleader default 20).”
    • pageinteger“Page number, starting at 1.”
  • teamleader_get_deal

    “Fetch one deal in full: lead (customer + contact person), value, probability, current phase, phase history, linked quotations, responsible users, lost reason and custom fields.”

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

    1 input, 1 required
    • deal_idstringrequired“The deal id (a UUID).”
  • teamleader_list_deal_pipelines

    “List the sales pipelines; the reply's meta names the default pipeline.”

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

    4 inputs
    • termstring“Search pipeline names.”
    • statusarray
    • page_sizeinteger“Page size, 1-100 (Teamleader default 20).”
    • pageinteger“Page number, starting at 1.”
  • teamleader_list_deal_phases

    “List the phases (stages) of deal pipelines, in flow order, with their probability.”

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

    3 inputs
    • deal_pipeline_idstring“Only phases of this pipeline.”
    • page_sizeinteger“Page size, 1-100 (Teamleader default 20).”
    • pageinteger“Page number, starting at 1.”
  • teamleader_list_invoices

    “List or search outgoing invoices.”

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

    14 inputs
    • termstring“Search invoice number, PO number, payment reference and invoicee.”
    • invoice_numberstring“Full invoice number, e.g.”
    • statusarray
    • customer_typestring“With customer_id: the customer's type.”
    • customer_idstring“Only invoices for this contact/company id.”
    • deal_idstring“The deal id (a UUID).”
    • project_idstring“The project id (a UUID).”
    • invoice_date_afterstring“Invoice date from, inclusive (YYYY-MM-DD).”
    • invoice_date_beforestring“Invoice date until, inclusive (YYYY-MM-DD).”
    • updated_sincestring“Only invoices updated since (ISO 8601 with offset, e.g.”
    • sort_fieldstring
    • sort_orderstring“Sort order.”
    • page_sizeinteger“Page size, 1-100 (Teamleader default 20).”
    • pageinteger“Page number, starting at 1.”
  • teamleader_get_invoice

    “Fetch one invoice in full: invoicee, grouped line items, discounts, totals and taxes, payment term, payments received, payment reference and Peppol status.”

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

    1 input, 1 required
    • invoice_idstringrequired“The invoice id (a UUID).”
Show 24 more tools
  • teamleader_list_projects

    “List projects (the projects module).”

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

    7 inputs
    • termstring“Search project number, title, customer, assignee and owner names.”
    • statusstring
    • customer_typestring“With customer_id: the customer's type.”
    • customer_idstring“Only projects for this contact/company id.”
    • deal_idsarray“Only projects linked to these deals.”
    • page_sizeinteger“Page size, 1-100 (Teamleader default 20).”
    • pageinteger“Page number, starting at 1.”
  • teamleader_list_tasks

    “List tasks (to-dos).”

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

    12 inputs
    • user_idstring“Tasks assigned to this user or one of their teams.”
    • completedboolean
    • scheduledboolean
    • due_fromstring“Due on or after (YYYY-MM-DD).”
    • due_bystring“Due on or before (YYYY-MM-DD).”
    • termstring“Search the task description.”
    • customer_typestring“With customer_id: the customer's type.”
    • customer_idstring“Only tasks for this contact/company id.”
    • sort_fieldstring
    • sort_orderstring“Sort order.”
    • page_sizeinteger“Page size, 1-100 (Teamleader default 20).”
    • pageinteger“Page number, starting at 1.”
  • teamleader_list_time_tracking

    “List tracked time entries: who, when, duration (seconds), work type, subject, invoiceable flag and hourly rate.”

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

    8 inputs
    • user_idstring“The user id (a UUID).”
    • started_afterstring“Entries that started on/after (ISO 8601 with offset, e.g.”
    • started_beforestring“Entries that started on/before (ISO 8601 with offset, e.g.”
    • subject_typestring“With subject_id: the subject's type.”
    • subject_idstring“Only entries tracked on this subject.”
    • sort_orderstring“Sort by start time (starts_on).”
    • page_sizeinteger“Page size, 1-100 (Teamleader default 20).”
    • pageinteger“Page number, starting at 1.”
  • teamleader_list_tickets

    “List support tickets: subject, status, assignee, customer, project and last message time.”

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

    6 inputs
    • customer_typestring“With customer_id: the customer's type.”
    • customer_idstring“Only tickets relating to this contact/company id.”
    • project_idsarray
    • assignee_idsarray“Only tickets assigned to one of these users.”
    • page_sizeinteger“Page size, 1-100 (Teamleader default 20).”
    • pageinteger“Page number, starting at 1.”
  • teamleader_list_work_types

    “List work types (e.g.”

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

    3 inputs
    • termstring“Search work type names.”
    • page_sizeinteger“Page size, 1-100 (Teamleader default 20).”
    • pageinteger“Page number, starting at 1.”
  • teamleader_list_departments

    “List the account's departments (company entities that issue invoices and quotations).”

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

    3 inputs
    • statusarray“Filter by status.”
    • sort_fieldstring
    • sort_orderstring“Sort order.”
  • teamleader_list_products

    “List or search products (the price list) by name or code.”

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

    4 inputs
    • termstring“Search the product name or code.”
    • updated_sincestring“Only products updated since (ISO 8601 with offset, e.g.”
    • page_sizeinteger“Page size, 1-100 (Teamleader default 20).”
    • pageinteger“Page number, starting at 1.”
  • teamleader_get_product

    “Fetch one product in full: code, description, purchase and selling prices, tax rate, unit, stock and category.”

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

    1 input, 1 required
    • product_idstringrequired“The product id (a UUID).”
  • teamleader_list_product_categories

    “List the product categories (each one is a ledger account), optionally for one department.”

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

    1 input
    • department_idstring“Only categories of this department.”
  • teamleader_list_quotations

    “List quotations (offers) with their status, totals and deal.”

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

    3 inputs
    • idsarray“Only these quotations.”
    • page_sizeinteger“Page size, 1-100 (Teamleader default 20).”
    • pageinteger“Page number, starting at 1.”
  • teamleader_get_quotation

    “Fetch one quotation in full: deal, grouped line items, discounts, totals, taxes, status and expiry.”

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

    1 input, 1 required
    • quotation_idstringrequired“The quotation id (a UUID).”
  • teamleader_list_activity_types

    “List the activity types of calendar events (Teamleader has three: tasks, meetings and calls).”

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

    2 inputs
    • page_sizeinteger“Page size, 1-100 (Teamleader default 20).”
    • pageinteger“Page number, starting at 1.”
  • teamleader_list_events

    “List calendar events (meetings, calls) in a time window.”

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

    13 inputs
    • ends_afterstring“Start of the period: events ending after (ISO 8601 with offset, e.g.”
    • starts_beforestring“End of the period: events starting before (ISO 8601 with offset, e.g.”
    • user_idstring“Only this user's events.”
    • activity_type_idstring“The activity type id (a UUID).”
    • termstring“Search the title and description.”
    • attendee_contact_idstring“Only events this contact attends.”
    • link_typestring“With link_id: the linked record's type.”
    • link_idstring“Only events linked to this contact, company or deal.”
    • task_idstring“Only events planned for this task.”
    • doneboolean
    • sort_orderstring“Sort by start time (starts_at).”
    • page_sizeinteger“Page size, 1-100 (Teamleader default 20).”
    • pageinteger“Page number, starting at 1.”
  • teamleader_list_subscriptions

    “List subscriptions (recurring invoices): title, status, customer, billing cycle and next invoice date.”

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

    10 inputs
    • customer_typestring“With customer_id: the customer's type.”
    • customer_idstring“Only this contact's or company's subscriptions.”
    • deal_idstring“Only subscriptions created from this deal.”
    • department_idstring“The department id (a UUID).”
    • invoice_idstring“The subscription that generated this invoice.”
    • statusarray
    • sort_fieldstring
    • sort_orderstring“Sort order.”
    • page_sizeinteger“Page size, 1-100 (Teamleader default 20).”
    • pageinteger“Page number, starting at 1.”
  • teamleader_get_subscription

    “Fetch one subscription in full: invoicee, line items, totals, billing cycle, start and end dates and payment term.”

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

    1 input, 1 required
    • subscription_idstringrequired“The subscription id (a UUID).”
  • teamleader_list_notes

    “List the notes on one contact, company, deal, invoice, quotation, project and more, with their text and date.”

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

    4 inputs, 2 required
    • subject_typestringrequired“What the notes are attached to (nextgenProject = a project in the projects module).”
    • subject_idstringrequired“The subject id (a UUID).”
    • page_sizeinteger“Page size, 1-100 (Teamleader default 20).”
    • pageinteger“Page number, starting at 1.”
  • teamleader_create_contact

    “WRITE: create a new contact (person) in Teamleader.”

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

    8 inputs, 1 required
    • last_namestringrequired
    • first_namestring
    • emailstring“Primary email address.”
    • telephonesarray
    • websitestring
    • languagestring“Language code, e.g.”
    • tagsarray“Tag names.”
    • remarksstring
  • teamleader_create_company

    “WRITE: create a new company in Teamleader.”

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

    10 inputs, 1 required
    • namestringrequired
    • emailstring“Primary email address.”
    • telephonesarray
    • websitestring
    • vat_numberstring
    • languagestring“Language code, e.g.”
    • responsible_user_idstring“The user id (a UUID).”
    • business_type_idstring“Legal structure id (e.g.”
    • tagsarray“Tag names.”
    • remarksstring
  • teamleader_create_deal

    “WRITE: create a new deal for an existing contact or company.”

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

    13 inputs, 3 required
    • customer_typestringrequired“Whether the customer is a contact or a company.”
    • customer_idstringrequired“The customer's contact or company id.”
    • contact_person_idstring“For a company customer: the contact person.”
    • titlestringrequired
    • summarystring“The deal's remarks field.”
    • phase_idstring“Starting phase; defaults to the default pipeline's first phase.”
    • responsible_user_idstring“The user id (a UUID).”
    • estimated_value_amountnumber“Expected value; needs estimated_value_currency.”
    • estimated_value_currencystring
    • estimated_probabilitynumber“Win probability, 0 to 1.”
    • estimated_closing_datestring“Expected closing date (YYYY-MM-DD).”
    • source_idstring“The deal source id (a UUID).”
    • department_idstring“Department (company entity) id.”
  • teamleader_create_task

    “WRITE: create a task (to-do).”

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

    12 inputs, 3 required
    • titlestringrequired
    • due_onstringrequired“Due date (YYYY-MM-DD).”
    • work_type_idstringrequired“Work type id (required by Teamleader).”
    • descriptionstring
    • assignee_typestring“With assignee_id.”
    • assignee_idstring“The assignee id (a UUID).”
    • customer_typestring“With customer_id.”
    • customer_idstring“The customer id (a UUID).”
    • deal_idstring“The deal id (a UUID).”
    • project_idstring“The project id (a UUID).”
    • ticket_idstring“The ticket id (a UUID).”
    • estimated_duration_minutesinteger
  • teamleader_add_note

    “WRITE: add a note to a contact, company, deal, invoice, quotation, project and more, e.g.”

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

    4 inputs, 3 required
    • subject_typestringrequired“What the note is attached to (nextgenProject = a project in the projects module).”
    • subject_idstringrequired“The subject id (a UUID).”
    • contentstringrequired“The note text.”
    • notify_user_idsarray“Users to notify about this note.”
  • teamleader_create_event

    “WRITE: put a meeting or call on the Teamleader calendar.”

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

    9 inputs, 4 required
    • titlestringrequired
    • activity_type_idstringrequired“The activity type id (a UUID).”
    • starts_atstringrequired“Start (ISO 8601 with offset, e.g.”
    • ends_atstringrequired“End (ISO 8601 with offset).”
    • descriptionstring
    • locationstring
    • work_type_idstring“The work type id (a UUID).”
    • attendee_user_idsarray“Firm users who attend.”
    • linksarray“Contacts, companies or deals the event is about.”
  • teamleader_complete_task

    “WRITE: mark a task (to-do) as complete.”

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

    1 input, 1 required
    • task_idstringrequired“The task id (a UUID).”
  • teamleader_add_time_tracking

    “WRITE: record time spent, e.g.”

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

    9 inputs, 1 required
    • started_atstringrequired“Start (ISO 8601 with offset, e.g.”
    • duration_minutesinteger“Time spent, in minutes.”
    • ended_atstring“End; give this or duration_minutes (ISO 8601 with offset, e.g.”
    • work_type_idstring“The work type id (a UUID).”
    • descriptionstring
    • subject_typestring“With subject_id: what the time was spent on (todo = a task, nextgenTask = a task in the projects module).”
    • subject_idstring“The subject id (a UUID).”
    • invoiceableboolean
    • user_idstring“Record the time for another user (default: the signed-in user).”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-24.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

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

Counted from the listing

Parameters with a description
82% of 208
Tools with a description
100% of 36
Typical description length
173 characters

The tool set

Counted from the listing

Tools
36
Size of the list
about 10,960 tokens for an agent to load (characters ÷ 4)
Naming
36 of 36 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 36 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

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

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

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://teamleader-focus.usefulapi.io/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "teamleader-focus": {
      "url": "https://teamleader-focus.usefulapi.io/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "teamleader-focus": {
      "type": "http",
      "url": "https://teamleader-focus.usefulapi.io/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"teamleader-focus","type":"http","url":"https://teamleader-focus.usefulapi.io/mcp"}'
Claude Code
claude mcp add --transport http teamleader-focus https://teamleader-focus.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://teamleader-focus.usefulapi.io/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint teamleader-focus.usefulapi.io/mcpSession openedmatchesour test · 2026-10-24
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-10-24
Repository github.com/m190/usefulapi-mcpOpens publiclymatchesapi.github.com · 2026-10-24

Who made it?

Feature #7 · lineage

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

Namespace
io.usefulapi · 409 servers
GitHub owner
a personal account (m190)
Repository
github.com/m190/usefulapi-mcp
Stars
0
Repository age
91–180 days
Last push
0–30 days ago
Archived
no

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

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

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

  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • Not checkedRepository publishes a security policy (SECURITY.md)We did not read this repository's security policy.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-24. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.usefulapi/teamleader-focus

Answered from the data above

Is io.usefulapi/teamleader-focus safe to install?

We do not rate servers as safe or unsafe. 4 of its 4 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does io.usefulapi/teamleader-focus need an API key or sign-in?

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

Has io.usefulapi/teamleader-focus been security tested?

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

Where is the source code of io.usefulapi/teamleader-focus?

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

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

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

The 18 checks at a glanceour test · 2026-10-24
  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-10-24, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 397 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 36 tools, 0 resources, 1 prompt.
  4. 1,357 msFinished: 3 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added in the weekly update
listed 2026-10-24; not classified yet
Pricing modelAI-classified
pending: added in the weekly update
the website is not read yet
Programming language
JavaScript
api.github.com · 2026-10-24
Hosting type
remote (hosted by the publisher)
registry · 2026-10-24
MCP capability
prompts, tools
our test · 2026-10-24
Transport
streamable HTTP
registry · 2026-10-24
Required credentials
none declared
registry · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-10-24
Lifecycle status
active
registry · 2026-10-24
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
owner: a personal account · repository age: 91–180 days · stars: 0–9
api.github.com · 2026-10-24
Maintenance
active
api.github.com · 2026-10-24
Environment
the publisher's infrastructure
where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.usefulapi/teamleader-focus: MCP server record.” Data checked 2026-10-24. https://protocolprobe.com/mcp/servers/io.usefulapi/teamleader-focus

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

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

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