FieldPulse MCP by usefulapi
REMOTE · FIELDPULSE.USEFULAPI.IO
Read FieldPulse customers, jobs, estimates, invoices, assets and projects; create and update jobs.
Available components
Last scanned (2 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 Usability81
- 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 4429 tokens (~103/item across 43 items; 43 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 Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 66% 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 43 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 44 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.1 → 1.4.3 functional
- Server version: 1.4.0 → 1.4.1 functional
- 24 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: pass → fail ▼ functional
- 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.1 → 1.2.0 functional
- 23 Oct 26 61
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://fieldpulse.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 fieldpulse.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://fieldpulse.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://fieldpulse.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://fieldpulse.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://fieldpulse.usefulapi.io/mcp |
| Authorisation server | https://fieldpulse.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://fieldpulse.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/fieldpulse/ |
| http (plaintext) | http://fieldpulse.usefulapi.io/mcp | Inconclusive | 302 | http://fieldpulse.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 →
fieldpulse_create_customer Create customer ~356
WRITE: create a customer (lead or account). Give first_name and/or last_name, or a unique display_name. Creates a new record every call; check fieldpulse_list_customers first to avoid duplicates. POST /customers.
| Name | Type | Req | Description |
|---|---|---|---|
| account_type | string | – | – |
| alt_email | string | – | – |
| assigned_to | – | – | User id the customer is assigned to (see fieldpulse_list_users); null clears it. |
| billing_address_1 | string | – | – |
| billing_address_2 | string | – | – |
| billing_city | string | – | – |
| billing_state | string | – | – |
| billing_zip_code | string | – | – |
| company_name | string | – | – |
| display_name | string | – | Required by FieldPulse when first and last name are empty; must be unique. |
| string | – | – | |
| first_name | string | – | – |
| has_different_billing_address | boolean | – | – |
| job_notes | string | – | – |
| last_name | string | – | – |
| lead_source_id | integer | – | See fieldpulse_list_lead_sources. |
| notes | string | – | – |
| phone | string | – | A valid phone number. |
| pipeline_status_id | integer | – | See fieldpulse_list_pipeline_statuses. |
| secondary_email | string | – | – |
| secondary_phone | string | – | A valid phone number. |
| service_address_1 | string | – | – |
| service_address_2 | string | – | – |
| service_address_city | string | – | – |
| service_address_state | string | – | – |
| service_address_zip_code | string | – | – |
| status | string | – | – |
| tags | array | – | Existing customer tag ids (see fieldpulse_list_tags). |
No output schema declared.
No examples provided.
fieldpulse_create_job Create job ~352
WRITE: create a job for an existing customer. Needs customer_id, job_type and the numeric billing value FieldPulse requires; set a status (1-6) or a custom status_id + status_workflow_id. Creates a new job every call. POST /jobs.
| Name | Type | Req | Description |
|---|---|---|---|
| assignments | array | – | Who the job is assigned to. |
| billing | integer | yes | The integer billing value FieldPulse requires for a job. |
| customer_contact_id | – | – | – |
| customer_id | integer | yes | Existing customer id. |
| due_date | string|null | – | Due date, yyyy-mm-dd or ISO 8601 with a timezone. |
| end_time | string|null | – | End, yyyy-mm-dd or ISO 8601 with a timezone. |
| field_notes | string | – | – |
| job_type | string | yes | Job type label, e.g. the service name. |
| location_id | – | – | A location of the customer (see fieldpulse_list_locations). |
| notes | string | – | – |
| project_id | – | – | – |
| start_time | string|null | – | Start, yyyy-mm-dd or ISO 8601 with a timezone. |
| status | integer | – | 1 = new, 2 = in progress, 3 = pending, 4 = completed, 5 = canceled, 6 = on the way. |
| status_id | integer | – | A custom status id (see fieldpulse_list_job_workflow_statuses); needs status_workflow_id. |
| status_workflow_id | integer | – | The status workflow of status_id (see fieldpulse_list_job_status_workflows). |
| subtitle | string | – | – |
| tags | array | – | Existing job tag ids (see fieldpulse_list_tags). |
No output schema declared.
No examples provided.
fieldpulse_get_asset Get asset ~33
One asset by id. GET /assets/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_id | integer | yes | FieldPulse asset id. |
No output schema declared.
No examples provided.
fieldpulse_get_contract Get contract ~33
One contract by id. GET /contracts/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| contract_id | integer | yes | FieldPulse contract id. |
No output schema declared.
No examples provided.
fieldpulse_get_customer Get customer ~33
One customer by id. GET /customers/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | integer | yes | FieldPulse customer id. |
No output schema declared.
No examples provided.
fieldpulse_get_customer_contact Get customer contact ~53
One contact of a customer. GET /customers/{customerId}/customer-contact/{contactId}.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | integer | yes | Customer contact id. |
| customer_id | integer | yes | FieldPulse customer id. |
No output schema declared.
No examples provided.
fieldpulse_get_estimate Get estimate ~35
One estimate by id. GET /estimates/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| estimate_id | integer | yes | FieldPulse estimate id. |
No output schema declared.
No examples provided.
fieldpulse_get_invoice Get invoice ~34
One invoice by id. GET /invoices/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice_id | integer | yes | FieldPulse invoice id. |
No output schema declared.
No examples provided.
fieldpulse_get_item Get item ~34
One invoice item by id. GET /items/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| item_id | integer | yes | FieldPulse item id. |
No output schema declared.
No examples provided.
fieldpulse_get_job Get job ~53
One job by id, optionally with its custom field values. GET /jobs/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | integer | yes | FieldPulse job id. |
| with_custom_fields | boolean | – | Include custom field values. |
No output schema declared.
No examples provided.
fieldpulse_get_location Get location ~33
One location by id. GET /locations/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| location_id | integer | yes | FieldPulse location id. |
No output schema declared.
No examples provided.
fieldpulse_get_payment Get payment ~33
One payment by id. GET /payments/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| payment_id | integer | yes | FieldPulse payment id. |
No output schema declared.
No examples provided.
fieldpulse_get_project Get project ~33
One project by id. GET /projects/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | integer | yes | FieldPulse project id. |
No output schema declared.
No examples provided.
fieldpulse_get_purchase_order Get purchase order ~38
One purchase order by id. GET /purchase-orders/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| purchase_order_id | integer | yes | FieldPulse purchase order id. |
No output schema declared.
No examples provided.
fieldpulse_get_vendor Get vendor ~33
One vendor by id. GET /vendors/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| vendor_id | integer | yes | FieldPulse vendor id. |
No output schema declared.
No examples provided.
fieldpulse_list_asset_categories List asset categories ~75
List asset categories. GET /assets-category.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Records per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| search | string | – | Free-text search string. |
No output schema declared.
No examples provided.
fieldpulse_list_assets List assets ~88
List or search customer assets (equipment) by install status. GET /assets.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Records per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| search | string | – | Free-text search string. |
| status | string | – | – |
No output schema declared.
No examples provided.
fieldpulse_list_comments List comments ~99
List comments on a record (customer, job, project, subtasks, invoice). GET /comments.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Records per page, 1-100 (default 25). |
| object_id | integer | – | Id of the record (needs object_type). |
| object_type | string | – | – |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
fieldpulse_list_company_profiles List company profiles ~91
The company profile(s) of this FieldPulse account (name, address, contact details, settings). GET /company-profile.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Records per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| search | string | – | Free-text search string. |
No output schema declared.
No examples provided.
fieldpulse_list_contracts List contracts ~40
List contracts (maintenance agreements). GET /contracts.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Records per page, 1-100 (default 25). |
No output schema declared.
No examples provided.
fieldpulse_list_custom_fields List custom fields ~79
List custom field definitions, optionally for one object type. GET /custom-fields.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Records per page, 1-100 (default 25). |
| object_type | string | – | – |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
fieldpulse_list_customer_contacts List customer contacts ~86
The contacts (people) of one customer. GET /customers/{customerId}/customer-contact.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | integer | yes | FieldPulse customer id. |
| limit | integer | – | Records per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
fieldpulse_list_customers List customers ~106
List or search customers (name, email, phone, address, status, assigned user). GET /customers.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Records per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| search | string | – | Free-text search string. |
| sort_by | string | – | – |
| sort_dir | string | – | Sort direction. |
No output schema declared.
No examples provided.
fieldpulse_list_estimates List estimates ~114
List or search estimates (customer, status, totals, line items). GET /estimates.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Records per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| search | string | – | Free-text search string. |
| sort_by | string | – | An attribute of the record, e.g. created_at. |
| sort_dir | string | – | Sort direction. |
No output schema declared.
No examples provided.
fieldpulse_list_invoices List invoices ~114
List or search invoices (customer, status, totals, due dates). GET /invoices.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Records per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| search | string | – | Free-text search string. |
| sort_by | string | – | An attribute of the record, e.g. created_at. |
| sort_dir | string | – | Sort direction. |
No output schema declared.
No examples provided.
fieldpulse_list_items List items ~70
List the invoice item catalog (products and services with prices). GET /items.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Records per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
fieldpulse_list_job_status_workflows List job status workflows ~64
The job status workflows (use their ids with fieldpulse_list_job_workflow_statuses and when setting a custom job status). GET /jobs/status-workflows.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Records per page, 1-100 (default 25). |
No output schema declared.
No examples provided.
fieldpulse_list_job_workflow_statuses List job workflow statuses ~62
The custom job statuses of all workflows, with their ids (for filtering jobs or setting a status). GET /jobs/status-workflow-statuses.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Records per page, 1-100 (default 25). |
No output schema declared.
No examples provided.
fieldpulse_list_jobs List jobs ~205
List or search jobs (type, status, customer, schedule, assignments), optionally within a created-at range or by custom status ids. GET /jobs.
| Name | Type | Req | Description |
|---|---|---|---|
| created_from | string | – | Only jobs created at or after this time (yyyy-mm-dd or ISO 8601 with a timezone). |
| created_to | string | – | Only jobs created at or before this time. |
| limit | integer | – | Records per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| search | string | – | Free-text search string. |
| sort_by | string | – | – |
| sort_dir | string | – | Sort direction. |
| status_ids | array | – | Only jobs in these custom status ids (see fieldpulse_list_job_workflow_statuses). |
| with_custom_fields | boolean | – | Include each job's custom field values (customfields_with_related_data). |
No output schema declared.
No examples provided.
fieldpulse_list_lead_sources List lead sources ~66
List customer lead sources. GET /lead-source.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Records per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
fieldpulse_list_locations List locations ~97
List locations (service addresses) of a customer or a job. GET /locations.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Records per page, 1-100 (default 25). |
| object_id | integer | – | Id of the customer or job (needs object_type). |
| object_type | string | – | – |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
fieldpulse_list_payments List payments ~101
List or search payments (amount, method, date, invoice). GET /payments.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Records per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| search | string | – | Free-text search string. |
| sort_by | string | – | – |
| sort_dir | string | – | Sort direction. |
No output schema declared.
No examples provided.
fieldpulse_list_pipeline_statuses List pipeline statuses ~66
List customer pipeline statuses. GET /pipeline-status.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Records per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
fieldpulse_list_projects List projects ~96
List or search projects (status, completion). GET /projects.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Records per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| search | string | – | Free-text search string. |
| sort_by | string | – | – |
| sort_dir | string | – | Sort direction. |
No output schema declared.
No examples provided.
fieldpulse_list_purchase_orders List purchase orders ~64
List purchase orders. GET /purchase-orders.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Records per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
fieldpulse_list_subtasks List subtasks ~116
List subtasks (job checklist items) by status or assigned user. GET /subtasks.
| Name | Type | Req | Description |
|---|---|---|---|
| assigned_user_id | integer | – | Only subtasks assigned to this user id. |
| limit | integer | – | Records per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| sort_by | string | – | – |
| sort_dir | string | – | Sort direction. |
| status | string | – | – |
No output schema declared.
No examples provided.
fieldpulse_list_tags List tags ~73
List tags for customers or jobs. GET /tags.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Records per page, 1-100 (default 25). |
| object_type | string | – | – |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
fieldpulse_list_teams List teams ~65
List the account's teams. GET /teams.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Records per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
fieldpulse_list_timesheets List timesheets ~115
List timesheet entries (clock in/out), optionally for one user or a time window. GET /timesheets.
| Name | Type | Req | Description |
|---|---|---|---|
| in_time | string | – | Clock-in time filter (yyyy-mm-dd or ISO 8601 with a timezone). |
| limit | integer | – | Records per page, 1-100 (default 25). |
| out_time | string | – | Clock-out time filter. |
| type | string | – | Entry type, e.g. job. |
| user_id | integer | – | Only this user's entries. |
No output schema declared.
No examples provided.
fieldpulse_list_users List users ~47
List the account's users (team members) with ids for assignments. GET /users.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Records per page, 1-100 (default 25). |
No output schema declared.
No examples provided.
fieldpulse_list_vendors List vendors ~51
List vendors (suppliers). GET /vendors.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Records per page, 1-100 (default 25). |
| search | string | – | Free-text search string. |
No output schema declared.
No examples provided.
fieldpulse_update_customer Update customer ~361
WRITE: change fields of one customer (only the fields you pass). If FieldPulse asks for a name, include first_name/last_name or display_name. PUT /customers/{customerId}.
| Name | Type | Req | Description |
|---|---|---|---|
| account_type | string | – | – |
| alt_email | string | – | – |
| assigned_to | – | – | User id the customer is assigned to (see fieldpulse_list_users); null clears it. |
| billing_address_1 | string | – | – |
| billing_address_2 | string | – | – |
| billing_city | string | – | – |
| billing_state | string | – | – |
| billing_zip_code | string | – | – |
| company_name | string | – | – |
| customer_id | integer | yes | FieldPulse customer id. |
| display_name | string | – | Required by FieldPulse when first and last name are empty; must be unique. |
| string | – | – | |
| first_name | string | – | – |
| has_different_billing_address | boolean | – | – |
| job_notes | string | – | – |
| last_name | string | – | – |
| lead_source_id | integer | – | See fieldpulse_list_lead_sources. |
| notes | string | – | – |
| phone | string | – | A valid phone number. |
| pipeline_status_id | integer | – | See fieldpulse_list_pipeline_statuses. |
| secondary_email | string | – | – |
| secondary_phone | string | – | A valid phone number. |
| service_address_1 | string | – | – |
| service_address_2 | string | – | – |
| service_address_city | string | – | – |
| service_address_state | string | – | – |
| service_address_zip_code | string | – | – |
| status | string | – | – |
| tags | array | – | Existing customer tag ids (see fieldpulse_list_tags). |
No output schema declared.
No examples provided.
fieldpulse_update_job Update job ~360
WRITE: change a job: status, schedule, notes, assignments, location. FieldPulse requires customer_id, job_type and billing on every update, so this reads the job first and keeps those (and its current status) unless you pass new values. The read and the write are two requests; FieldPulse offers no version check. PUT /jobs/{jobId}.
| Name | Type | Req | Description |
|---|---|---|---|
| assignments | array | – | Who the job is assigned to. |
| billing | integer | – | – |
| customer_contact_id | – | – | – |
| customer_id | integer | – | – |
| due_date | string|null | – | Due date, yyyy-mm-dd or ISO 8601 with a timezone. |
| end_time | string|null | – | End, yyyy-mm-dd or ISO 8601 with a timezone. |
| field_notes | string | – | – |
| job_id | integer | yes | FieldPulse job id. |
| job_type | string | – | – |
| location_id | – | – | A location of the customer (see fieldpulse_list_locations). |
| notes | string | – | – |
| project_id | – | – | – |
| start_time | string|null | – | Start, yyyy-mm-dd or ISO 8601 with a timezone. |
| status | integer | – | 1 = new, 2 = in progress, 3 = pending, 4 = completed, 5 = canceled, 6 = on the way. |
| status_id | integer | – | A custom status id (see fieldpulse_list_job_workflow_statuses); needs status_workflow_id. |
| status_workflow_id | integer | – | The status workflow of status_id (see fieldpulse_list_job_status_workflows). |
| subtitle | string | – | – |
| tags | array | – | Existing job tag ids (see fieldpulse_list_tags). |
No output schema declared.
No examples provided.
How do I install the FieldPulse MCP by usefulapi server?
FieldPulse MCP by usefulapi is a hosted endpoint at https://fieldpulse.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 · fieldpulse.usefulapi.io
claude mcp add --transport http io-usefulapi-fieldpulse 'https://fieldpulse.usefulapi.io/mcp'
What is the FieldPulse MCP by usefulapi server?
FieldPulse MCP by usefulapi is listed in the public MCP registry as io.usefulapi/fieldpulse. Read FieldPulse customers, jobs, estimates, invoices, assets and projects; create and update jobs. This page covers its hosted endpoint (https://fieldpulse.usefulapi.io/mcp).
Is the FieldPulse MCP by usefulapi server safe to use?
FieldPulse MCP by usefulapi scores 62 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 FieldPulse MCP by usefulapi server expose?
FieldPulse MCP by usefulapi exposes 43 tools: fieldpulse_list_customers, fieldpulse_get_customer, fieldpulse_list_customer_contacts, fieldpulse_get_customer_contact, fieldpulse_list_jobs, and 38 more. Their descriptions and schemas cost roughly 4,157 tokens of context every time the server is loaded.
Does the FieldPulse MCP by usefulapi server require authentication?
Yes. FieldPulse 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 FieldPulse MCP by usefulapi server still maintained?
FieldPulse 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.