Service Fusion MCP by usefulapi
REMOTE · SERVICE-FUSION.USEFULAPI.IO
Read Service Fusion customers, jobs, estimates, invoices and schedule; create customers and jobs.
Available components
Last scanned (5 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 25 Oct 2026.
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability74
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 5681 tokens (~218/item across 26 items; 26 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 75% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 26 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 27 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Oct 26 0
- Server version: 1.4.0 → 1.4.3 functional
- 24 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.3.0 → 1.4.0 functional
- Server version: 1.2.0 → 1.3.0 functional
- Server version: 1.0.0 → 1.2.0 functional
- 23 Oct 26 60
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Oct 2026 · Probed https://service-fusion.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of service-fusion.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690, 57355 | 8, 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://service-fusion.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://service-fusion.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://service-fusion.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://service-fusion.usefulapi.io/mcp |
| Authorisation server | https://service-fusion.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://service-fusion.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/service-fusion/ |
| http (plaintext) | http://service-fusion.usefulapi.io/mcp | Inconclusive | 302 | http://service-fusion.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
servicefusion_create_customer Create customer ~296
WRITE: create a customer in Service Fusion, optionally with contacts (phones, emails) and service locations. It is visible to the whole team and cannot be deleted through this API; creating the same name twice makes two customers, so search with servicefusion_list_customers first. POST /customers.
| Name | Type | Req | Description |
|---|---|---|---|
| account_number | string | – | – |
| agent | string | – | Sales agent name. |
| assigned_contract | string | – | – |
| contacts | array | – | – |
| credit_rating | string | – | – |
| custom_fields | array | – | Custom fields: [{name, value}] with names as configured in Service Fusion. |
| customer_name | string | yes | Customer (company or person) name. |
| discount | number | – | – |
| discount_type | string | – | – |
| industry | string | – | – |
| is_bill_for_drive_time | boolean | – | – |
| is_taxable | boolean | – | – |
| is_vip | boolean | – | – |
| labor_charge_default_rate | number | – | – |
| labor_charge_type | string | – | – |
| locations | array | – | – |
| parent_customer | string | – | Name of an existing parent customer. |
| payment_terms | string | – | – |
| payment_type | string | – | – |
| private_notes | string | – | Internal notes. |
| public_notes | string | – | Notes shown on customer-facing documents. |
| referral_source | string | – | – |
| tax_item_name | string | – | – |
No output schema declared.
No examples provided.
servicefusion_create_estimate Create estimate ~508
WRITE: create an estimate (quote) for a customer, optionally with address, category, source, technicians, tasks, notes, products, services, other charges and tags. It cannot be deleted through this API; creating twice makes two estimates. POST /estimates.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Job category name (see servicefusion_list_job_categories). |
| city | string | – | – |
| contact_first_name | string | – | – |
| contact_last_name | string | – | – |
| contract | string | – | – |
| custom_fields | array | – | Custom fields: [{name, value}] with names as configured in Service Fusion. |
| customer_name | string | yes | Customer name exactly as in Service Fusion (see servicefusion_list_customers); an unknown name is created as a new customer. |
| description | string | – | Job/estimate description (max 500 characters). |
| duration | integer | – | Duration in seconds, 0-86400 (3600 = 1 hour). |
| gate_instructions | string | – | – |
| is_gated | boolean | – | – |
| location_name | string | – | – |
| note_to_customer | string | – | – |
| notes | array | – | Internal notes: [{notes}]. |
| opportunity_owner | string | – | Name of the opportunity owner. |
| opportunity_rating | integer | – | Opportunity rating, 0-5. |
| other_charges | array | – | – |
| phase | string | – | – |
| po_number | string | – | – |
| postal_code | string | – | – |
| products | array | – | – |
| project | string | – | – |
| services | array | – | – |
| source | string | – | Lead source name (see servicefusion_list_sources). |
| start_date | string | – | Start date, yyyy-mm-dd. |
| state_prov | string | – | – |
| status | string | – | Status name (see servicefusion_list_job_statuses). |
| street_1 | string | – | – |
| street_2 | string | – | – |
| tags | array | – | Tags: [{tag}]. |
| tasks | array | – | – |
| tech_notes | string | – | Notes for the technician. |
| techs_assigned | array | – | Technicians to assign: [{id}] or [{first_name, last_name}]. |
| time_frame_promised_end | string | – | Promised arrival window end, HH:MM. |
| time_frame_promised_start | string | – | Promised arrival window start, HH:MM. |
No output schema declared.
No examples provided.
servicefusion_create_job Create job ~559
WRITE: create a job (work order) for a customer, optionally with address, category, source, assigned technicians, tasks, notes, products, services and other charges. It appears on the team's schedule and cannot be deleted through this API; creating twice makes two jobs. Look up category, source and status names with the list tools first. POST /jobs.
| Name | Type | Req | Description |
|---|---|---|---|
| called_in_by | string | – | – |
| category | string | – | Job category name (see servicefusion_list_job_categories). |
| check_number | string | – | – |
| city | string | – | – |
| completion_notes | string | – | – |
| contact_first_name | string | – | – |
| contact_last_name | string | – | – |
| contract | string | – | – |
| custom_fields | array | – | Custom fields: [{name, value}] with names as configured in Service Fusion. |
| customer_name | string | yes | Customer name exactly as in Service Fusion (see servicefusion_list_customers); an unknown name is created as a new customer. |
| customer_payment_terms | string | – | – |
| description | string | – | Job/estimate description (max 500 characters). |
| duration | integer | – | Duration in seconds, 0-86400 (3600 = 1 hour). |
| end_date | string | – | End date, yyyy-mm-dd. |
| gate_instructions | string | – | – |
| is_gated | boolean | – | – |
| is_requires_follow_up | boolean | – | – |
| location_name | string | – | – |
| note_to_customer | string | – | – |
| notes | array | – | Internal notes: [{notes}]. |
| other_charges | array | – | – |
| payment_type | string | – | – |
| phase | string | – | – |
| po_number | string | – | – |
| postal_code | string | – | – |
| priority | string | – | – |
| products | array | – | – |
| project | string | – | – |
| services | array | – | – |
| source | string | – | Lead source name (see servicefusion_list_sources). |
| start_date | string | – | Start date, yyyy-mm-dd. |
| state_prov | string | – | – |
| status | string | – | Status name (see servicefusion_list_job_statuses). |
| street_1 | string | – | – |
| street_2 | string | – | – |
| tasks | array | – | – |
| tech_notes | string | – | Notes for the technician. |
| techs_assigned | array | – | Technicians to assign: [{id}] or [{first_name, last_name}]. |
| time_frame_promised_end | string | – | Promised arrival window end, HH:MM. |
| time_frame_promised_start | string | – | Promised arrival window start, HH:MM. |
No output schema declared.
No examples provided.
servicefusion_get_availability Get technician availability ~339
Open time slots for technicians and/or crews over up to 8 days (end_date at most 7 days after start_date). Filter by technician, crew, department, experience level and slot length. GET /availability.
| Name | Type | Req | Description |
|---|---|---|---|
| crew_ids | array | – | Only these crew ids. |
| departments | array | – | Technician departments (any may match). |
| end_date | string | yes | Last day (inclusive), yyyy-mm-dd; at most 7 days after start_date. |
| end_time | string | – | Only slots ending at or before this time of day, HH:MM. |
| experience_levels | array | – | Experience levels 0-10 (any may match). |
| ignore_work_schedule | boolean | – | Ignore each technician's work schedule; only the time window limits the slots. |
| max_duration | integer | – | Maximum slot length in minutes. |
| min_duration | integer | – | Minimum slot length in minutes. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Slots per page, 1-100. |
| scope | string | – | Individual technician slots, crew slots, or both (the API default is techs; pass all to include crews). |
| sort | string | – | Sort by date and/or duration, e.g. date,-duration (API default: date). |
| start_date | string | yes | First day (inclusive), yyyy-mm-dd. |
| start_time | string | – | Only slots starting at or after this time of day, HH:MM. |
| tech_ids | array | – | Only these technician ids. |
No output schema declared.
No examples provided.
servicefusion_get_calendar_task Get calendar task ~75
One calendar task by id. GET /calendar-tasks/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| calendar_task_id | integer | yes | Calendar task id. |
| expand | array | – | Extra data to include: repeat. |
| fields | string | – | Only return these fields, comma-separated (for example id,customer_name). Default: all. |
No output schema declared.
No examples provided.
servicefusion_get_crew Get crew ~79
One crew by id, optionally with its technicians. GET /crews/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| crew_id | integer | yes | Service Fusion crew id. |
| expand | array | – | Extra data to include: techs. |
| fields | string | – | Only return these fields, comma-separated (for example id,customer_name). Default: all. |
No output schema declared.
No examples provided.
servicefusion_get_customer Get customer ~97
One customer by id, optionally with contacts, phones, emails, locations and custom fields. GET /customers/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | integer | yes | Service Fusion customer id. |
| expand | array | – | Extra data to include: contacts, contacts.phones, contacts.emails, locations, custom_fields. |
| fields | string | – | Only return these fields, comma-separated (for example id,customer_name). Default: all. |
No output schema declared.
No examples provided.
servicefusion_get_customer_equipment Get customer equipment ~101
One piece of equipment of a customer. GET /customers/{customer_id}/equipment/{equipment_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | integer | yes | Service Fusion customer id. |
| equipment_id | integer | yes | Equipment id (from servicefusion_list_customer_equipment). |
| expand | array | – | Extra data to include: custom_fields. |
| fields | string | – | Only return these fields, comma-separated (for example id,customer_name). Default: all. |
No output schema declared.
No examples provided.
servicefusion_get_estimate Get estimate ~126
One estimate by id, optionally with line items, technicians, notes, tags and more. GET /estimates/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| estimate_id | integer | yes | Service Fusion estimate id. |
| expand | array | – | Extra data to include: agents, custom_fields, pictures, documents, equipment, equipment.custom_fields, techs_assigned, tasks, notes, products, services, other_charges, payments, signatures, printable… |
| fields | string | – | Only return these fields, comma-separated (for example id,customer_name). Default: all. |
No output schema declared.
No examples provided.
servicefusion_get_invoice Get invoice ~59
One invoice by id. GET /invoices/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | string | – | Only return these fields, comma-separated (for example id,customer_name). Default: all. |
| invoice_id | integer | yes | Service Fusion invoice id. |
No output schema declared.
No examples provided.
servicefusion_get_job Get job ~146
One job by id, optionally with technicians, line items, labor, expenses, payments, invoices, notes, visits and more. GET /jobs/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| expand | array | – | Extra data to include: agents, custom_fields, pictures, documents, equipment, equipment.custom_fields, techs_assigned, tasks, notes, products, services, other_charges, labor_charges, expenses, paymen… |
| fields | string | – | Only return these fields, comma-separated (for example id,customer_name). Default: all. |
| job_id | integer | yes | Service Fusion job id. |
No output schema declared.
No examples provided.
servicefusion_get_me Get current user ~37
The Service Fusion user the API credentials belong to: id, name and email. Use it to check the connection. GET /me.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
servicefusion_get_tech Get technician ~60
One technician by id. GET /techs/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | string | – | Only return these fields, comma-separated (for example id,customer_name). Default: all. |
| tech_id | integer | yes | Service Fusion technician id. |
No output schema declared.
No examples provided.
servicefusion_list_calendar_tasks List calendar tasks ~269
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. A task is returned when it overlaps the range. GET /calendar-tasks.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | – | Range end, yyyy-mm-dd. Give BOTH start_date and end_date for a range; with only one of them the API returns tasks on that single day. |
| expand | array | – | Extra data to include: repeat. |
| fields | string | – | Only return these fields, comma-separated (for example id,customer_name). Default: all. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-50 (default 10). |
| sort | string | – | Sort fields, comma-separated; a leading - sorts descending (for example -updated_at,customer_name). |
| start_date | string | – | Range start, yyyy-mm-dd. Give BOTH start_date and end_date for a range; with only one of them the API returns tasks on that single day. |
| user_ids | array | – | Only tasks assigned to these user (technician) ids. |
No output schema declared.
No examples provided.
servicefusion_list_crews List crews ~140
List crews (named groups of technicians), optionally with their members. GET /crews.
| Name | Type | Req | Description |
|---|---|---|---|
| expand | array | – | Extra data to include: techs. |
| fields | string | – | Only return these fields, comma-separated (for example id,customer_name). Default: all. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-50 (default 10). |
| sort | string | – | Sort fields, comma-separated; a leading - sorts descending (for example -updated_at,customer_name). |
No output schema declared.
No examples provided.
servicefusion_list_customer_equipment List customer equipment ~166
List the equipment on file for a customer (type, make, model, serial number, warranty and install dates). GET /customers/{id}/equipment.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | integer | yes | Service Fusion customer id. |
| expand | array | – | Extra data to include: custom_fields. |
| fields | string | – | Only return these fields, comma-separated (for example id,customer_name). Default: all. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-50 (default 10). |
| sort | string | – | Sort fields, comma-separated; a leading - sorts descending (for example -updated_at,customer_name). |
No output schema declared.
No examples provided.
servicefusion_list_customers List customers ~343
List customers (newest id order unless sorted). Filter by name, contact, address, city, postal code, phone, email, tags or last-serviced date. Add expand=contacts,locations,custom_fields to include them. GET /customers.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Street address (partial match). |
| city | string | – | City (exact match). |
| contact_first_name | string | – | Contact first name (partial match). |
| contact_last_name | string | – | Contact last name (partial match). |
| string | – | Email (exact match). | |
| expand | array | – | Extra data to include: contacts, contacts.phones, contacts.emails, locations, custom_fields. |
| fields | string | – | Only return these fields, comma-separated (for example id,customer_name). Default: all. |
| last_serviced_from | string | – | Last serviced on or after this date, yyyy-mm-dd. |
| last_serviced_to | string | – | Last serviced on or before this date, yyyy-mm-dd. |
| name | string | – | Customer name (partial match). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-50 (default 10). |
| phone | string | – | Phone (partial match). |
| postal_code | string | – | Postal/ZIP code (exact match). |
| sort | string | – | Sort fields, comma-separated; a leading - sorts descending (for example -updated_at,customer_name). |
| tags | string | – | Tags, comma-separated (exact match). |
No output schema declared.
No examples provided.
servicefusion_list_estimates List estimates ~501
List estimates (quotes). Filter by status, number, PO number, customer, contact, address, phone, email, category, source and start/end/requested dates. GET /estimates.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Street address (partial match). |
| category | string | – | Categories, comma-separated (exact match). |
| city | string | – | City (exact match). |
| contact_first_name | string | – | Contact first name (partial match). |
| contact_last_name | string | – | Contact last name (partial match). |
| customer_name | string | – | Customer name (partial match). |
| string | – | Email (exact match). | |
| end_date_from | string | – | End date on or after, yyyy-mm-dd. |
| end_date_to | string | – | End date on or before, yyyy-mm-dd. |
| expand | array | – | Extra data to include: agents, custom_fields, pictures, documents, equipment, equipment.custom_fields, techs_assigned, tasks, notes, products, services, other_charges, payments, signatures, printable… |
| fields | string | – | Only return these fields, comma-separated (for example id,customer_name). Default: all. |
| number | string | – | Estimate number (partial match). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| parent_customer_name | string | – | Parent customer name (partial match). |
| per_page | integer | – | Results per page, 1-50 (default 10). |
| phone | string | – | Phone (partial match). |
| po_number | string | – | PO number (partial match). |
| requested_from | string | – | Requested at or after (RFC 3339 date-time with timezone). |
| requested_to | string | – | Requested at or before (RFC 3339 date-time with timezone). |
| sort | string | – | Sort fields, comma-separated; a leading - sorts descending (for example -updated_at,customer_name). |
| source | string | – | Sources, comma-separated (exact match). |
| start_date_from | string | – | Start date on or after, yyyy-mm-dd. |
| start_date_to | string | – | Start date on or before, yyyy-mm-dd. |
| status | string | – | Estimate status names, comma-separated (exact match). |
| zip_code | string | – | Postal/ZIP code (exact match). |
No output schema declared.
No examples provided.
servicefusion_list_invoices List invoices ~146
List invoices with number, total, paid flag, dates and the customer. The API has no invoice filters: sort and page instead (for example sort=-date). GET /invoices.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | string | – | Only return these fields, comma-separated (for example id,customer_name). Default: all. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-50 (default 10). |
| sort | string | – | Sort fields, comma-separated; a leading - sorts descending (for example -updated_at,customer_name). |
No output schema declared.
No examples provided.
servicefusion_list_job_categories List job categories ~126
The job category names to use when creating or filtering jobs. GET /job-categories.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | string | – | Only return these fields, comma-separated (for example id,customer_name). Default: all. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-50 (default 10). |
| sort | string | – | Sort fields, comma-separated; a leading - sorts descending (for example -updated_at,customer_name). |
No output schema declared.
No examples provided.
servicefusion_list_job_statuses List job statuses ~137
The job status names (code, name, custom flag, category) to use when creating or filtering jobs. GET /job-statuses.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | string | – | Only return these fields, comma-separated (for example id,customer_name). Default: all. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-50 (default 10). |
| sort | string | – | Sort fields, comma-separated; a leading - sorts descending (for example -updated_at,customer_name). |
No output schema declared.
No examples provided.
servicefusion_list_jobs List jobs ~610
List jobs (work orders). Filter by status, number, PO or invoice number, customer, contact, address, phone, email, category, source and start/end/updated/closed dates. Add expand (techs_assigned, services, products, payments, invoices, visits, notes, ...) for detail. GET /jobs.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Street address (partial match). |
| category | string | – | Job categories, comma-separated (exact match). |
| city | string | – | City (exact match). |
| closed_from | string | – | Closed at or after (RFC 3339 date-time with timezone). |
| closed_to | string | – | Closed at or before (RFC 3339 date-time with timezone). |
| contact_first_name | string | – | Contact first name (partial match). |
| contact_last_name | string | – | Contact last name (partial match). |
| customer_name | string | – | Customer name (partial match). |
| string | – | Email (exact match). | |
| end_date_from | string | – | Job end date on or after, yyyy-mm-dd. |
| end_date_to | string | – | Job end date on or before, yyyy-mm-dd. |
| expand | array | – | Extra data to include: agents, custom_fields, pictures, documents, equipment, equipment.custom_fields, techs_assigned, tasks, notes, products, services, other_charges, labor_charges, expenses, paymen… |
| fields | string | – | Only return these fields, comma-separated (for example id,customer_name). Default: all. |
| invoice_number | string | – | Invoice number (partial match). |
| number | string | – | Job number (partial match). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| parent_customer_name | string | – | Parent customer name (partial match). |
| per_page | integer | – | Results per page, 1-50 (default 10). |
| phone | string | – | Phone (partial match). |
| po_number | string | – | PO number (partial match). |
| sort | string | – | Sort fields, comma-separated; a leading - sorts descending (for example -updated_at,customer_name). |
| source | string | – | Sources, comma-separated (exact match). |
| start_date_from | string | – | Job start date on or after, yyyy-mm-dd. |
| start_date_to | string | – | Job start date on or before, yyyy-mm-dd. |
| status | string | – | Job status names, comma-separated (exact match; see servicefusion_list_job_statuses). |
| updated_from | string | – | Updated at or after (RFC 3339 date-time with timezone). |
| updated_to | string | – | Updated at or before (RFC 3339 date-time with timezone). |
| zip_code | string | – | Postal/ZIP code (exact match). |
No output schema declared.
No examples provided.
servicefusion_list_payment_types List payment types ~121
The payment types configured in the account. GET /payment-types.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | string | – | Only return these fields, comma-separated (for example id,customer_name). Default: all. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-50 (default 10). |
| sort | string | – | Sort fields, comma-separated; a leading - sorts descending (for example -updated_at,customer_name). |
No output schema declared.
No examples provided.
servicefusion_list_sources List lead sources ~132
The lead/referral sources (short and long names) to use when creating or filtering jobs and estimates. GET /sources.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | string | – | Only return these fields, comma-separated (for example id,customer_name). Default: all. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-50 (default 10). |
| sort | string | – | Sort fields, comma-separated; a leading - sorts descending (for example -updated_at,customer_name). |
No output schema declared.
No examples provided.
servicefusion_list_tech_departments List technician departments ~36
The technician department names configured in the account (useful for availability filters). GET /techs/departments.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
servicefusion_list_techs List technicians ~212
List technicians and sales reps (name, contact details, department, title, color, field-worker and sales-rep flags). GET /techs.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Email (partial match). | |
| fields | string | – | Only return these fields, comma-separated (for example id,customer_name). Default: all. |
| first_name | string | – | First name (partial match). |
| last_name | string | – | Last name (partial match). |
| nickname_on_dispatch | string | – | Nickname on the dispatch board (partial match). |
| nickname_on_workorder | string | – | Nickname on work orders (partial match). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-50 (default 10). |
| sort | string | – | Sort fields, comma-separated; a leading - sorts descending (for example -updated_at,customer_name). |
No output schema declared.
No examples provided.
How do I install the Service Fusion MCP by usefulapi server?
Service Fusion MCP by usefulapi is a hosted endpoint at https://service-fusion.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · service-fusion.usefulapi.io
claude mcp add --transport http io-usefulapi-service-fusion 'https://service-fusion.usefulapi.io/mcp'
What is the Service Fusion MCP by usefulapi server?
Service Fusion MCP by usefulapi is listed in the public MCP registry as io.usefulapi/service-fusion. Read Service Fusion customers, jobs, estimates, invoices and schedule; create customers and jobs. This page covers its hosted endpoint (https://service-fusion.usefulapi.io/mcp).
Is the Service Fusion MCP by usefulapi server safe to use?
Service Fusion MCP by usefulapi scores 61 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Service Fusion MCP by usefulapi server expose?
Service Fusion MCP by usefulapi exposes 26 tools: servicefusion_get_me, servicefusion_list_customers, servicefusion_get_customer, servicefusion_list_customer_equipment, servicefusion_get_customer_equipment, and 21 more. Their descriptions and schemas cost roughly 5,421 tokens of context every time the server is loaded.
Does the Service Fusion MCP by usefulapi server require authentication?
Yes. Service Fusion MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Service Fusion MCP by usefulapi server still maintained?
Service Fusion MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.