MCP servers › io.usefulapi › service-fusion

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

io.usefulapi/service-fusion

Read Service Fusion customers, jobs, estimates, invoices and schedule; create customers and jobs. — the publisher's description

4 of 4 record checks metRead-only · tools listed 2026-10-24version 1.4.0JavaScriptstreamable HTTP26 tools

Summary

io.usefulapi/service-fusion is a remote MCP server listed in the official MCP registry at version 1.4.0. On 2026-10-24 ProtocolProbe connected to it in read-only mode and read its inventory: 26 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: 26
Last tested: 2026-10-24

Add to your client

Observed fact

This server accepted a session without any credential and lists 3 tools whose name or declaration suggests they change data (servicefusion_create_customer, servicefusion_create_job, servicefusion_create_estimate). 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.4.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.4.0 · 2026-10-24
1.3.0 · 2026-10-24
1.2.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.4.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

26tools

0resources

1prompts

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

servicefusion_get_me
“The Service Fusion user the API credentials belong to: id, name and email.”
Publisher declares: read-only yes · destructive no · open-world yes
Takes no inputs.
servicefusion_list_customers
“List customers (newest id order unless sorted).”
Publisher declares: read-only yes · destructive no · open-world yes
16 inputs
- namestring“Customer name (partial match).”
- contact_first_namestring“Contact first name (partial match).”
- contact_last_namestring“Contact last name (partial match).”
- addressstring“Street address (partial match).”
- citystring“City (exact match).”
- postal_codestring“Postal/ZIP code (exact match).”
- phonestring“Phone (partial match).”
- emailstring“Email (exact match).”
- tagsstring“Tags, comma-separated (exact match).”
- last_serviced_fromstring“Last serviced on or after this date, yyyy-mm-dd.”
- last_serviced_tostring“Last serviced on or before this date, yyyy-mm-dd.”
- expandarray“Extra data to include: contacts, contacts.phones, contacts.emails, locations, custom_fields.”
- sortstring“Sort fields, comma-separated; a leading - sorts descending (for example -updated_at,customer_name).”
- fieldsstring“Only return these fields, comma-separated (for example id,customer_name).”
- pageinteger“Page number, from 1 (default 1).”
- per_pageinteger“Results per page, 1-50 (default 10).”
servicefusion_get_customer
“One customer by id, optionally with contacts, phones, emails, locations and custom fields.”
Publisher declares: read-only yes · destructive no · open-world yes
3 inputs, 1 required
- customer_idintegerrequired“Service Fusion customer id.”
- expandarray“Extra data to include: contacts, contacts.phones, contacts.emails, locations, custom_fields.”
- fieldsstring“Only return these fields, comma-separated (for example id,customer_name).”
servicefusion_list_customer_equipment
“List the equipment on file for a customer (type, make, model, serial number, warranty and install dates).”
Publisher declares: read-only yes · destructive no · open-world yes
6 inputs, 1 required
- customer_idintegerrequired“Service Fusion customer id.”
- expandarray“Extra data to include: custom_fields.”
- sortstring“Sort fields, comma-separated; a leading - sorts descending (for example -updated_at,customer_name).”
- fieldsstring“Only return these fields, comma-separated (for example id,customer_name).”
- pageinteger“Page number, from 1 (default 1).”
- per_pageinteger“Results per page, 1-50 (default 10).”
servicefusion_get_customer_equipment
“One piece of equipment of a customer.”
Publisher declares: read-only yes · destructive no · open-world yes
4 inputs, 2 required
- customer_idintegerrequired“Service Fusion customer id.”
- equipment_idintegerrequired“Equipment id (from servicefusion_list_customer_equipment).”
- expandarray“Extra data to include: custom_fields.”
- fieldsstring“Only return these fields, comma-separated (for example id,customer_name).”
servicefusion_list_jobs
“List jobs (work orders).”
Publisher declares: read-only yes · destructive no · open-world yes
28 inputs
- statusstring“Job status names, comma-separated (exact match; see servicefusion_list_job_statuses).”
- numberstring“Job number (partial match).”
- po_numberstring“PO number (partial match).”
- invoice_numberstring“Invoice number (partial match).”
- customer_namestring“Customer name (partial match).”
- parent_customer_namestring“Parent customer name (partial match).”
- contact_first_namestring“Contact first name (partial match).”
- contact_last_namestring“Contact last name (partial match).”
- addressstring“Street address (partial match).”
- citystring“City (exact match).”
- zip_codestring“Postal/ZIP code (exact match).”
- phonestring“Phone (partial match).”
- emailstring“Email (exact match).”
- categorystring“Job categories, comma-separated (exact match).”
- sourcestring“Sources, comma-separated (exact match).”
- start_date_fromstring“Job start date on or after, yyyy-mm-dd.”
- start_date_tostring“Job start date on or before, yyyy-mm-dd.”
- end_date_fromstring“Job end date on or after, yyyy-mm-dd.”
- end_date_tostring“Job end date on or before, yyyy-mm-dd.”
- updated_fromstring“Updated at or after (RFC 3339 date-time with timezone).”
- updated_tostring“Updated at or before (RFC 3339 date-time with timezone).”
- closed_fromstring“Closed at or after (RFC 3339 date-time with timezone).”
- closed_tostring“Closed at or before (RFC 3339 date-time with timezone).”
- expandarray“Extra data to include: agents, custom_fields, pictures, documents, equipment, equipment.custom_fields, techs_assigned, tasks, notes, products, services, other_…”
- sortstring“Sort fields, comma-separated; a leading - sorts descending (for example -updated_at,customer_name).”
and 3 more not listed here.
servicefusion_get_job
“One job by id, optionally with technicians, line items, labor, expenses, payments, invoices, notes, visits and more.”
Publisher declares: read-only yes · destructive no · open-world yes
3 inputs, 1 required
- job_idintegerrequired“Service Fusion job id.”
- expandarray“Extra data to include: agents, custom_fields, pictures, documents, equipment, equipment.custom_fields, techs_assigned, tasks, notes, products, services, other_…”
- fieldsstring“Only return these fields, comma-separated (for example id,customer_name).”
servicefusion_list_estimates
“List estimates (quotes).”
Publisher declares: read-only yes · destructive no · open-world yes
25 inputs
- statusstring“Estimate status names, comma-separated (exact match).”
- numberstring“Estimate number (partial match).”
- po_numberstring“PO number (partial match).”
- customer_namestring“Customer name (partial match).”
- parent_customer_namestring“Parent customer name (partial match).”
- contact_first_namestring“Contact first name (partial match).”
- contact_last_namestring“Contact last name (partial match).”
- addressstring“Street address (partial match).”
- citystring“City (exact match).”
- zip_codestring“Postal/ZIP code (exact match).”
- phonestring“Phone (partial match).”
- emailstring“Email (exact match).”
- categorystring“Categories, comma-separated (exact match).”
- sourcestring“Sources, comma-separated (exact match).”
- start_date_fromstring“Start date on or after, yyyy-mm-dd.”
- start_date_tostring“Start date on or before, yyyy-mm-dd.”
- end_date_fromstring“End date on or after, yyyy-mm-dd.”
- end_date_tostring“End date on or before, yyyy-mm-dd.”
- requested_fromstring“Requested at or after (RFC 3339 date-time with timezone).”
- requested_tostring“Requested at or before (RFC 3339 date-time with timezone).”
- expandarray“Extra data to include: agents, custom_fields, pictures, documents, equipment, equipment.custom_fields, techs_assigned, tasks, notes, products, services, other_…”
- sortstring“Sort fields, comma-separated; a leading - sorts descending (for example -updated_at,customer_name).”
- fieldsstring“Only return these fields, comma-separated (for example id,customer_name).”
- pageinteger“Page number, from 1 (default 1).”
- per_pageinteger“Results per page, 1-50 (default 10).”
servicefusion_get_estimate
“One estimate by id, optionally with line items, technicians, notes, tags and more.”
Publisher declares: read-only yes · destructive no · open-world yes
3 inputs, 1 required
- estimate_idintegerrequired“Service Fusion estimate id.”
- expandarray“Extra data to include: agents, custom_fields, pictures, documents, equipment, equipment.custom_fields, techs_assigned, tasks, notes, products, services, other_…”
- fieldsstring“Only return these fields, comma-separated (for example id,customer_name).”
servicefusion_list_invoices
“List invoices with number, total, paid flag, dates and the customer.”
Publisher declares: read-only yes · destructive no · open-world yes
4 inputs
- sortstring“Sort fields, comma-separated; a leading - sorts descending (for example -updated_at,customer_name).”
- fieldsstring“Only return these fields, comma-separated (for example id,customer_name).”
- pageinteger“Page number, from 1 (default 1).”
- per_pageinteger“Results per page, 1-50 (default 10).”
servicefusion_get_invoice
“One invoice by id.”
Publisher declares: read-only yes · destructive no · open-world yes
2 inputs, 1 required
- invoice_idintegerrequired“Service Fusion invoice id.”
- fieldsstring“Only return these fields, comma-separated (for example id,customer_name).”
servicefusion_list_calendar_tasks
“List calendar tasks (appointments and to-dos on the schedule) for one day (start_date or end_date alone), a date range (both) and/or given users.”
Publisher declares: read-only yes · destructive no · open-world yes
8 inputs
- start_datestring“Range start, yyyy-mm-dd.”
- end_datestring“Range end, yyyy-mm-dd.”
- user_idsarray“Only tasks assigned to these user (technician) ids.”
- expandarray“Extra data to include: repeat.”
- sortstring“Sort fields, comma-separated; a leading - sorts descending (for example -updated_at,customer_name).”
- fieldsstring“Only return these fields, comma-separated (for example id,customer_name).”
- pageinteger“Page number, from 1 (default 1).”
- per_pageinteger“Results per page, 1-50 (default 10).”

Show 14 more tools

servicefusion_get_calendar_task
“One calendar task by id.”
Publisher declares: read-only yes · destructive no · open-world yes
3 inputs, 1 required
- calendar_task_idintegerrequired“Calendar task id.”
- expandarray“Extra data to include: repeat.”
- fieldsstring“Only return these fields, comma-separated (for example id,customer_name).”
servicefusion_get_availability
“Open time slots for technicians and/or crews over up to 8 days (end_date at most 7 days after start_date).”
Publisher declares: read-only yes · destructive no · open-world yes
15 inputs, 2 required
- start_datestringrequired“First day (inclusive), yyyy-mm-dd.”
- end_datestringrequired“Last day (inclusive), yyyy-mm-dd; at most 7 days after start_date.”
- scopestring“Individual technician slots, crew slots, or both (the API default is techs; pass all to include crews).”
- start_timestring“Only slots starting at or after this time of day, HH:MM.”
- end_timestring“Only slots ending at or before this time of day, HH:MM.”
- tech_idsarray“Only these technician ids.”
- crew_idsarray“Only these crew ids.”
- departmentsarray“Technician departments (any may match).”
- experience_levelsarray“Experience levels 0-10 (any may match).”
- min_durationinteger“Minimum slot length in minutes.”
- max_durationinteger“Maximum slot length in minutes.”
- sortstring“Sort by date and/or duration, e.g.”
- ignore_work_scheduleboolean“Ignore each technician's work schedule; only the time window limits the slots.”
- pageinteger“Page number, from 1 (default 1).”
- per_pageinteger“Slots per page, 1-100.”
servicefusion_list_techs
“List technicians and sales reps (name, contact details, department, title, color, field-worker and sales-rep flags).”
Publisher declares: read-only yes · destructive no · open-world yes
9 inputs
- first_namestring“First name (partial match).”
- last_namestring“Last name (partial match).”
- emailstring“Email (partial match).”
- nickname_on_workorderstring“Nickname on work orders (partial match).”
- nickname_on_dispatchstring“Nickname on the dispatch board (partial match).”
- sortstring“Sort fields, comma-separated; a leading - sorts descending (for example -updated_at,customer_name).”
- fieldsstring“Only return these fields, comma-separated (for example id,customer_name).”
- pageinteger“Page number, from 1 (default 1).”
- per_pageinteger“Results per page, 1-50 (default 10).”
servicefusion_get_tech
“One technician by id.”
Publisher declares: read-only yes · destructive no · open-world yes
2 inputs, 1 required
- tech_idintegerrequired“Service Fusion technician id.”
- fieldsstring“Only return these fields, comma-separated (for example id,customer_name).”
servicefusion_list_tech_departments
“The technician department names configured in the account (useful for availability filters).”
Publisher declares: read-only yes · destructive no · open-world yes
Takes no inputs.
servicefusion_list_crews
“List crews (named groups of technicians), optionally with their members.”
Publisher declares: read-only yes · destructive no · open-world yes
5 inputs
- expandarray“Extra data to include: techs.”
- sortstring“Sort fields, comma-separated; a leading - sorts descending (for example -updated_at,customer_name).”
- fieldsstring“Only return these fields, comma-separated (for example id,customer_name).”
- pageinteger“Page number, from 1 (default 1).”
- per_pageinteger“Results per page, 1-50 (default 10).”
servicefusion_get_crew
“One crew by id, optionally with its technicians.”
Publisher declares: read-only yes · destructive no · open-world yes
3 inputs, 1 required
- crew_idintegerrequired“Service Fusion crew id.”
- expandarray“Extra data to include: techs.”
- fieldsstring“Only return these fields, comma-separated (for example id,customer_name).”
servicefusion_list_job_categories
“The job category names to use when creating or filtering jobs.”
Publisher declares: read-only yes · destructive no · open-world yes
4 inputs
- sortstring“Sort fields, comma-separated; a leading - sorts descending (for example -updated_at,customer_name).”
- fieldsstring“Only return these fields, comma-separated (for example id,customer_name).”
- pageinteger“Page number, from 1 (default 1).”
- per_pageinteger“Results per page, 1-50 (default 10).”
servicefusion_list_job_statuses
“The job status names (code, name, custom flag, category) to use when creating or filtering jobs.”
Publisher declares: read-only yes · destructive no · open-world yes
4 inputs
- sortstring“Sort fields, comma-separated; a leading - sorts descending (for example -updated_at,customer_name).”
- fieldsstring“Only return these fields, comma-separated (for example id,customer_name).”
- pageinteger“Page number, from 1 (default 1).”
- per_pageinteger“Results per page, 1-50 (default 10).”
servicefusion_list_payment_types
“The payment types configured in the account.”
Publisher declares: read-only yes · destructive no · open-world yes
4 inputs
- sortstring“Sort fields, comma-separated; a leading - sorts descending (for example -updated_at,customer_name).”
- fieldsstring“Only return these fields, comma-separated (for example id,customer_name).”
- pageinteger“Page number, from 1 (default 1).”
- per_pageinteger“Results per page, 1-50 (default 10).”
servicefusion_list_sources
“The lead/referral sources (short and long names) to use when creating or filtering jobs and estimates.”
Publisher declares: read-only yes · destructive no · open-world yes
4 inputs
- sortstring“Sort fields, comma-separated; a leading - sorts descending (for example -updated_at,customer_name).”
- fieldsstring“Only return these fields, comma-separated (for example id,customer_name).”
- pageinteger“Page number, from 1 (default 1).”
- per_pageinteger“Results per page, 1-50 (default 10).”
servicefusion_create_customer
“WRITE: create a customer in Service Fusion, optionally with contacts (phones, emails) and service locations.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
23 inputs, 1 required
- customer_namestringrequired“Customer (company or person) name.”
- parent_customerstring“Name of an existing parent customer.”
- account_numberstring
- private_notesstring“Internal notes.”
- public_notesstring“Notes shown on customer-facing documents.”
- credit_ratingstring
- labor_charge_typestring
- labor_charge_default_ratenumber
- is_bill_for_drive_timeboolean
- is_vipboolean
- referral_sourcestring
- agentstring“Sales agent name.”
- discountnumber
- discount_typestring
- payment_typestring
- payment_termsstring
- assigned_contractstring
- industrystring
- is_taxableboolean
- tax_item_namestring
- contactsarray
- locationsarray
- custom_fieldsarray“Custom fields: [{name, value}] with names as configured in Service Fusion.”
servicefusion_create_job
“WRITE: create a job (work order) for a customer, optionally with address, category, source, assigned technicians, tasks, notes, products, services and other charges.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
40 inputs, 1 required
- descriptionstring“Job/estimate description (max 500 characters).”
- tech_notesstring“Notes for the technician.”
- durationinteger“Duration in seconds, 0-86400 (3600 = 1 hour).”
- time_frame_promised_startstring“Promised arrival window start, HH:MM.”
- time_frame_promised_endstring“Promised arrival window end, HH:MM.”
- start_datestring“Start date, yyyy-mm-dd.”
- customer_namestringrequired“Customer name exactly as in Service Fusion (see servicefusion_list_customers); an unknown name is created as a new customer.”
- statusstring“Status name (see servicefusion_list_job_statuses).”
- contact_first_namestring
- contact_last_namestring
- street_1string
- street_2string
- citystring
- state_provstring
- postal_codestring
- location_namestring
- is_gatedboolean
- gate_instructionsstring
- categorystring“Job category name (see servicefusion_list_job_categories).”
- sourcestring“Lead source name (see servicefusion_list_sources).”
- projectstring
- phasestring
- po_numberstring
- contractstring
- note_to_customerstring
and 15 more not listed here.
servicefusion_create_estimate
“WRITE: create an estimate (quote) for a customer, optionally with address, category, source, technicians, tasks, notes, products, services, other charges and tags.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
35 inputs, 1 required
- descriptionstring“Job/estimate description (max 500 characters).”
- tech_notesstring“Notes for the technician.”
- durationinteger“Duration in seconds, 0-86400 (3600 = 1 hour).”
- time_frame_promised_startstring“Promised arrival window start, HH:MM.”
- time_frame_promised_endstring“Promised arrival window end, HH:MM.”
- start_datestring“Start date, yyyy-mm-dd.”
- customer_namestringrequired“Customer name exactly as in Service Fusion (see servicefusion_list_customers); an unknown name is created as a new customer.”
- statusstring“Status name (see servicefusion_list_job_statuses).”
- contact_first_namestring
- contact_last_namestring
- street_1string
- street_2string
- citystring
- state_provstring
- postal_codestring
- location_namestring
- is_gatedboolean
- gate_instructionsstring
- categorystring“Job category name (see servicefusion_list_job_categories).”
- sourcestring“Lead source name (see servicefusion_list_sources).”
- projectstring
- phasestring
- po_numberstring
- contractstring
- note_to_customerstring
and 10 more not listed here.

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: 75% of 253
Tools with a description: 100% of 26
Typical description length: 143 characters

The tool set

Counted from the listing

Tools: 26
Size of the list: about 12,371 tokens for an agent to load (characters ÷ 4)
Naming: 26 of 26 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 26 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://service-fusion.usefulapi.io/mcp

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

{
  "mcpServers": {
    "service-fusion": {
      "url": "https://service-fusion.usefulapi.io/mcp"
    }
  }
}

VS Code · .vscode/mcp.json

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

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

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

Claude Code

claude mcp add --transport http service-fusion https://service-fusion.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://service-fusion.usefulapi.io/mcp --transport http

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

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

Does the registry listing match what we found?

Feature #6

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

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

Who made it?

Feature #7 · lineage

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

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

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

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

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

Choosing

Record checks

Public records · not a safety rating

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

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

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

Common questions about io.usefulapi/service-fusion

Answered from the data above

Is io.usefulapi/service-fusion 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/service-fusion 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/service-fusion 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/service-fusion?

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

Found this page useful?

Anonymous · no sign-in

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

Compare with another server

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

Security testing

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

18 checks · features #1, #2

Open without sign-in

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

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

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: not run · nothing to check it against
Fake assistant turns: not run · an error was returned
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not run · our policy
Consent handling: not testable from outside
Sign-in metadata: exercised

3 exercised13 not run (reason given)2 not applicable

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

Exercised · 3

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

Not run, with the reason · 13

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server returned an error when its prompts were read.not run · an error was returned
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside

Does not apply to this server · 2

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

Source: our own test, 2026-10-24, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

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

0 msStarted a read-only session with the server's remote endpoint
403 msConnected after 0 redirects. No credential was sent or needed.
Read the inventory: 26 tools, 0 resources, 1 prompt.
1,601 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/service-fusion: MCP server record.” Data checked 2026-10-24. https://protocolprobe.com/mcp/servers/io.usefulapi/service-fusion

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

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