Name: FieldPulse MCP by usefulapi
Author: usefulapi

FieldPulse MCP by usefulapi

Read FieldPulse customers, jobs, estimates, invoices, assets and projects; create and update jobs.

Tool-list grade A Remote · Streamable HTTP No auth needed 43 tools v1.16.0 MIT

No reviews yet by usefulapiGitHub The publisher’s own endpoint — this marketplace is not in the path

93/100

tool-list score

tools declared

remote

at its publisher

—

calls last 7d

What it does

Read FieldPulse customers, jobs, estimates, invoices, assets and projects; create and update jobs.

Quickstart

# 1 — add it to Claude Code
claude mcp add --scope user --transport http fieldpulse-mcp-by-usefulapi https://fieldpulse.usefulapi.io/mcp

# 2 — ask your agent for something these tools do
#   fieldpulse_list_customers, fieldpulse_get_customer, fieldpulse_list_customer_contacts and 40 more

FieldPulse MCP by usefulapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.

Publishernot claimed

usefulapi449 servers

24 categories

All 449 servers

Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.

Tool surface

What the model actually sees. Descriptions are diffed on every release — see version history.

Only tools that write or reach the network

List or search customers (name, email, phone, address, status, assigned user). GET /customers.

Parameter	Type	Required	Notes
search	string	no	Free-text search string.
sort_by	string	no	—
sort_dir	string	no	Sort direction.
page	integer	no	Page number, from 1 (default 1). Pass the previous reply's next_page.
limit	integer	no	Records per page, 1-100 (default 25).

One customer by id. GET /customers/{id}.

Parameter	Type	Required	Notes
customer_id	integer	yes	FieldPulse customer id.

The contacts (people) of one customer. GET /customers/{customerId}/customer-contact.

Parameter	Type	Required	Notes
customer_id	integer	yes	FieldPulse customer id.
page	integer	no	Page number, from 1 (default 1). Pass the previous reply's next_page.
limit	integer	no	Records per page, 1-100 (default 25).

One contact of a customer. GET /customers/{customerId}/customer-contact/{contactId}.

Parameter	Type	Required	Notes
customer_id	integer	yes	FieldPulse customer id.
contact_id	integer	yes	Customer contact id.

List or search jobs (type, status, customer, schedule, assignments), optionally within a created-at range or by custom status ids. GET /jobs.

Parameter	Type	Required	Notes
search	string	no	Free-text search string.
sort_by	string	no	—
sort_dir	string	no	Sort direction.
created_from	string	no	Only jobs created at or after this time (yyyy-mm-dd or ISO 8601 with a timezone).
created_to	string	no	Only jobs created at or before this time.
status_ids	array	no	Only jobs in these custom status ids (see fieldpulse_list_job_workflow_statuses).
with_custom_fields	boolean	no	Include each job's custom field values (customfields_with_related_data).
page	integer	no	Page number, from 1 (default 1). Pass the previous reply's next_page.
limit	integer	no	Records per page, 1-100 (default 25).

One job by id, optionally with its custom field values. GET /jobs/{id}.

Parameter	Type	Required	Notes
job_id	integer	yes	FieldPulse job id.
with_custom_fields	boolean	no	Include custom field values.

The job status workflows (use their ids with fieldpulse_list_job_workflow_statuses and when setting a custom job status). GET /jobs/status-workflows.

Parameter	Type	Required	Notes
limit	integer	no	Records per page, 1-100 (default 25).

The custom job statuses of all workflows, with their ids (for filtering jobs or setting a status). GET /jobs/status-workflow-statuses.

Parameter	Type	Required	Notes
limit	integer	no	Records per page, 1-100 (default 25).

List or search estimates (customer, status, totals, line items). GET /estimates.

Parameter	Type	Required	Notes
search	string	no	Free-text search string.
sort_by	string	no	An attribute of the record, e.g. created_at.
sort_dir	string	no	Sort direction.
page	integer	no	Page number, from 1 (default 1). Pass the previous reply's next_page.
limit	integer	no	Records per page, 1-100 (default 25).

One estimate by id. GET /estimates/{id}.

Parameter	Type	Required	Notes
estimate_id	integer	yes	FieldPulse estimate id.

List or search invoices (customer, status, totals, due dates). GET /invoices.

Parameter	Type	Required	Notes
search	string	no	Free-text search string.
sort_by	string	no	An attribute of the record, e.g. created_at.
sort_dir	string	no	Sort direction.
page	integer	no	Page number, from 1 (default 1). Pass the previous reply's next_page.
limit	integer	no	Records per page, 1-100 (default 25).

One invoice by id. GET /invoices/{id}.

Parameter	Type	Required	Notes
invoice_id	integer	yes	FieldPulse invoice id.

List or search payments (amount, method, date, invoice). GET /payments.

Parameter	Type	Required	Notes
search	string	no	Free-text search string.
sort_by	string	no	—
sort_dir	string	no	Sort direction.
page	integer	no	Page number, from 1 (default 1). Pass the previous reply's next_page.
limit	integer	no	Records per page, 1-100 (default 25).

One payment by id. GET /payments/{id}.

Parameter	Type	Required	Notes
payment_id	integer	yes	FieldPulse payment id.

List or search customer assets (equipment) by install status. GET /assets.

Parameter	Type	Required	Notes
search	string	no	Free-text search string.
status	string	no	—
page	integer	no	Page number, from 1 (default 1). Pass the previous reply's next_page.
limit	integer	no	Records per page, 1-100 (default 25).

One asset by id. GET /assets/{id}.

Parameter	Type	Required	Notes
asset_id	integer	yes	FieldPulse asset id.

List asset categories. GET /assets-category.

Parameter	Type	Required	Notes
search	string	no	Free-text search string.
page	integer	no	Page number, from 1 (default 1). Pass the previous reply's next_page.
limit	integer	no	Records per page, 1-100 (default 25).

List locations (service addresses) of a customer or a job. GET /locations.

Parameter	Type	Required	Notes
object_type	string	no	—
object_id	integer	no	Id of the customer or job (needs object_type).
page	integer	no	Page number, from 1 (default 1). Pass the previous reply's next_page.
limit	integer	no	Records per page, 1-100 (default 25).

One location by id. GET /locations/{id}.

Parameter	Type	Required	Notes
location_id	integer	yes	FieldPulse location id.

List or search projects (status, completion). GET /projects.

Parameter	Type	Required	Notes
search	string	no	Free-text search string.
sort_by	string	no	—
sort_dir	string	no	Sort direction.
page	integer	no	Page number, from 1 (default 1). Pass the previous reply's next_page.
limit	integer	no	Records per page, 1-100 (default 25).

One project by id. GET /projects/{id}.

Parameter	Type	Required	Notes
project_id	integer	yes	FieldPulse project id.

List contracts (maintenance agreements). GET /contracts.

Parameter	Type	Required	Notes
limit	integer	no	Records per page, 1-100 (default 25).

One contract by id. GET /contracts/{id}.

Parameter	Type	Required	Notes
contract_id	integer	yes	FieldPulse contract id.

List the invoice item catalog (products and services with prices). GET /items.

Parameter	Type	Required	Notes
page	integer	no	Page number, from 1 (default 1). Pass the previous reply's next_page.
limit	integer	no	Records per page, 1-100 (default 25).

One invoice item by id. GET /items/{id}.

Parameter	Type	Required	Notes
item_id	integer	yes	FieldPulse item id.

List purchase orders. GET /purchase-orders.

Parameter	Type	Required	Notes
page	integer	no	Page number, from 1 (default 1). Pass the previous reply's next_page.
limit	integer	no	Records per page, 1-100 (default 25).

One purchase order by id. GET /purchase-orders/{id}.

Parameter	Type	Required	Notes
purchase_order_id	integer	yes	FieldPulse purchase order id.

List vendors (suppliers). GET /vendors.

Parameter	Type	Required	Notes
search	string	no	Free-text search string.
limit	integer	no	Records per page, 1-100 (default 25).

One vendor by id. GET /vendors/{id}.

Parameter	Type	Required	Notes
vendor_id	integer	yes	FieldPulse vendor id.

The company profile(s) of this FieldPulse account (name, address, contact details, settings). GET /company-profile.

Parameter	Type	Required	Notes
search	string	no	Free-text search string.
page	integer	no	Page number, from 1 (default 1). Pass the previous reply's next_page.
limit	integer	no	Records per page, 1-100 (default 25).

List the account's users (team members) with ids for assignments. GET /users.

Parameter	Type	Required	Notes
limit	integer	no	Records per page, 1-100 (default 25).

List the account's teams. GET /teams.

Parameter	Type	Required	Notes
page	integer	no	Page number, from 1 (default 1). Pass the previous reply's next_page.
limit	integer	no	Records per page, 1-100 (default 25).

List tags for customers or jobs. GET /tags.

Parameter	Type	Required	Notes
object_type	string	no	—
page	integer	no	Page number, from 1 (default 1). Pass the previous reply's next_page.
limit	integer	no	Records per page, 1-100 (default 25).

List customer lead sources. GET /lead-source.

Parameter	Type	Required	Notes
page	integer	no	Page number, from 1 (default 1). Pass the previous reply's next_page.
limit	integer	no	Records per page, 1-100 (default 25).

List customer pipeline statuses. GET /pipeline-status.

Parameter	Type	Required	Notes
page	integer	no	Page number, from 1 (default 1). Pass the previous reply's next_page.
limit	integer	no	Records per page, 1-100 (default 25).

List custom field definitions, optionally for one object type. GET /custom-fields.

Parameter	Type	Required	Notes
object_type	string	no	—
page	integer	no	Page number, from 1 (default 1). Pass the previous reply's next_page.
limit	integer	no	Records per page, 1-100 (default 25).

List comments on a record (customer, job, project, subtasks, invoice). GET /comments.

Parameter	Type	Required	Notes
object_type	string	no	—
object_id	integer	no	Id of the record (needs object_type).
page	integer	no	Page number, from 1 (default 1). Pass the previous reply's next_page.
limit	integer	no	Records per page, 1-100 (default 25).

List subtasks (job checklist items) by status or assigned user. GET /subtasks.

Parameter	Type	Required	Notes
status	string	no	—
assigned_user_id	integer	no	Only subtasks assigned to this user id.
sort_by	string	no	—
sort_dir	string	no	Sort direction.
page	integer	no	Page number, from 1 (default 1). Pass the previous reply's next_page.
limit	integer	no	Records per page, 1-100 (default 25).

List timesheet entries (clock in/out), optionally for one user or a time window. GET /timesheets.

Parameter	Type	Required	Notes
user_id	integer	no	Only this user's entries.
in_time	string	no	Clock-in time filter (yyyy-mm-dd or ISO 8601 with a timezone).
out_time	string	no	Clock-out time filter.
type	string	no	Entry type, e.g. job.
limit	integer	no	Records per page, 1-100 (default 25).

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.

Parameter	Type	Required	Notes
first_name	string	no	—
last_name	string	no	—
display_name	string	no	Required by FieldPulse when first and last name are empty; must be unique.
company_name	string	no	—
account_type	string	no	—
email	string	no	—
alt_email	string	no	—
secondary_email	string	no	—
phone	string	no	A valid phone number.
secondary_phone	string	no	A valid phone number.
status	string	no	—
notes	string	no	—
job_notes	string	no	—
assigned_to		no	User id the customer is assigned to (see fieldpulse_list_users); null clears it.
lead_source_id	integer	no	See fieldpulse_list_lead_sources.
pipeline_status_id	integer	no	See fieldpulse_list_pipeline_statuses.
tags	array	no	Existing customer tag ids (see fieldpulse_list_tags).
has_different_billing_address	boolean	no	—
billing_address_1	string	no	—
billing_address_2	string	no	—

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}.

Parameter	Type	Required	Notes
customer_id	integer	yes	FieldPulse customer id.
first_name	string	no	—
last_name	string	no	—
display_name	string	no	Required by FieldPulse when first and last name are empty; must be unique.
company_name	string	no	—
account_type	string	no	—
email	string	no	—
alt_email	string	no	—
secondary_email	string	no	—
phone	string	no	A valid phone number.
secondary_phone	string	no	A valid phone number.
status	string	no	—
notes	string	no	—
job_notes	string	no	—
assigned_to		no	User id the customer is assigned to (see fieldpulse_list_users); null clears it.
lead_source_id	integer	no	See fieldpulse_list_lead_sources.
pipeline_status_id	integer	no	See fieldpulse_list_pipeline_statuses.
tags	array	no	Existing customer tag ids (see fieldpulse_list_tags).
has_different_billing_address	boolean	no	—
billing_address_1	string	no	—

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.

Parameter	Type	Required	Notes
customer_id	integer	yes	Existing customer id.
job_type	string	yes	Job type label, e.g. the service name.
billing	integer	yes	The integer billing value FieldPulse requires for a job.
subtitle	string	no	—
notes	string	no	—
field_notes	string	no	—
status	integer	no	1 = new, 2 = in progress, 3 = pending, 4 = completed, 5 = canceled, 6 = on the way.
status_id	integer	no	A custom status id (see fieldpulse_list_job_workflow_statuses); needs status_workflow_id.
status_workflow_id	integer	no	The status workflow of status_id (see fieldpulse_list_job_status_workflows).
start_time	string/null	no	Start, yyyy-mm-dd or ISO 8601 with a timezone.
end_time	string/null	no	End, yyyy-mm-dd or ISO 8601 with a timezone.
due_date	string/null	no	Due date, yyyy-mm-dd or ISO 8601 with a timezone.
location_id		no	A location of the customer (see fieldpulse_list_locations).
project_id		no	—
customer_contact_id		no	—
assignments	array	no	Who the job is assigned to.
tags	array	no	Existing job tag ids (see fieldpulse_list_tags).

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}.

Parameter	Type	Required	Notes
job_id	integer	yes	FieldPulse job id.
customer_id	integer	no	—
job_type	string	no	—
billing	integer	no	—
subtitle	string	no	—
notes	string	no	—
field_notes	string	no	—
status	integer	no	1 = new, 2 = in progress, 3 = pending, 4 = completed, 5 = canceled, 6 = on the way.
status_id	integer	no	A custom status id (see fieldpulse_list_job_workflow_statuses); needs status_workflow_id.
status_workflow_id	integer	no	The status workflow of status_id (see fieldpulse_list_job_status_workflows).
start_time	string/null	no	Start, yyyy-mm-dd or ISO 8601 with a timezone.
end_time	string/null	no	End, yyyy-mm-dd or ISO 8601 with a timezone.
due_date	string/null	no	Due date, yyyy-mm-dd or ISO 8601 with a timezone.
location_id		no	A location of the customer (see fieldpulse_list_locations).
project_id		no	—
customer_contact_id		no	—
assignments	array	no	Who the job is assigned to.
tags	array	no	Existing job tag ids (see fieldpulse_list_tags).

Free

$0 forever

Every tool — any call limit is its publisher’s, not ours
No card, and mcprush charges nothing for it
Runs at its publisher’s own address — this marketplace is not in the path
Nothing to cap, because mcprush bills nothing

Nothing here is billable: mcprush charges nothing to install FieldPulse MCP by usefulapi or to call it, at any volume.

ATool-list grade · score 93 / 100

Release 1.16.0 · scanned 1 Nov 2026

Graded from the tools this server lists, not from its source code.

Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.

Threat score100

Client score93

Findings0 threat · 1 capability

Capabilitymoderate

Coveragemanifest

Verificationnot in this report

Surface digest9019977775725ebd55b93e48cdb517946eab3b92513910d075cc05c69a3d1878

Score vectorthreat 100 → client 93

Term	Level	What it prices	Points
capability-exposure	moderate	capability blast radius (moderate) — client exposure if the model is manipulated	−3
coverage-honesty	manifest	inspection depth (manifest) — how much of the target the scan could see	−4

score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.

What the scan could actually read

A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.

The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.

Tool surfaceread

Implementation sourcenot available

Package metadatanot available

Live transportnot available

The implementation source was not read — this reflects the declared tool metadata only.

Capability — what it could do if the model were manipulated

Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.

Tool	Capability tags	Why the tag was assigned
fieldpulse_list_customers	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
fieldpulse_get_customer	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
fieldpulse_list_customer_contacts	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
fieldpulse_get_customer_contact	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
fieldpulse_list_jobs	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
fieldpulse_get_job	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
fieldpulse_list_job_status_workflows	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
fieldpulse_list_job_workflow_statuses	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
fieldpulse_list_estimates	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
fieldpulse_get_estimate	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
fieldpulse_list_invoices	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
fieldpulse_get_invoice	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
fieldpulse_list_payments	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
fieldpulse_get_payment	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
fieldpulse_list_assets	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
fieldpulse_get_asset	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
fieldpulse_list_asset_categories	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
fieldpulse_list_locations	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
fieldpulse_get_location	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
fieldpulse_list_projects	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
fieldpulse_get_project	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
fieldpulse_list_contracts	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
fieldpulse_get_contract	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
fieldpulse_list_items	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
fieldpulse_get_item	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
fieldpulse_list_purchase_orders	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
fieldpulse_get_purchase_order	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
fieldpulse_list_vendors	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
fieldpulse_get_vendor	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
fieldpulse_list_company_profiles	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
fieldpulse_list_users	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
fieldpulse_list_teams	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
fieldpulse_list_tags	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
fieldpulse_list_lead_sources	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
fieldpulse_list_pipeline_statuses	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
fieldpulse_list_custom_fields	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
fieldpulse_list_comments	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
fieldpulse_list_subtasks	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
fieldpulse_list_timesheets	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
fieldpulse_create_customer	external-sink	external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true
fieldpulse_update_customer	external-sink	external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true
fieldpulse_create_job	external-sink	external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true
fieldpulse_update_job	external-sink	external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true

Toxic-flow graph

The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.

flow-1

Untrusted input can drive an external action even though no sensitive source is exposed.

Supply chain and provenance

Integrityfirst-seen

Surface digest9019977775725ebd

Scanned2026-11-01

This is the first scan of this surface here, so there is nothing yet to compare it against.

Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.

Where are you running it?

Tool surface

Release history

FieldPulse MCP by usefulapi

What it does

Quickstart

Where are you running it?

Tool surface

What counts against your monthly calls

What the scan could actually read

Capability — what it could do if the model were manipulated

Toxic-flow graph

Supply chain and provenance

Release history

See also