# FieldPulse MCP by usefulapi (remote · fieldpulse.usefulapi.io)

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

- Trust score: 62/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-25

## Components

- remote · `fieldpulse.usefulapi.io`: 62/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-fieldpulse/fieldpulse.md), [page](https://verifymcp.io/servers/io-usefulapi-fieldpulse/fieldpulse)

## Channel facts

- Endpoint: `https://fieldpulse.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.4.3`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-25.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 81/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 89/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 66% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 43 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 44 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

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

### Claude

```bash
claude mcp add --transport http io-usefulapi-fieldpulse 'https://fieldpulse.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-fieldpulse": {
      "url": "https://fieldpulse.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-fieldpulse": {
      "type": "http",
      "url": "https://fieldpulse.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-fieldpulse]
url = "https://fieldpulse.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-fieldpulse": {
      "type": "remote",
      "url": "https://fieldpulse.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-fieldpulse --url 'https://fieldpulse.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-fieldpulse:
    url: "https://fieldpulse.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-fieldpulse": {
      "Transport": "http",
      "Url": "https://fieldpulse.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-fieldpulse -t streamable-http -u 'https://fieldpulse.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-fieldpulse": {
      "type": "http",
      "url": "https://fieldpulse.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-25 (score 62, 0)

- [functional] Server version: 1.4.1 → 1.4.3
- [functional] Server version: 1.4.0 → 1.4.1

### 2026-10-24 (score 62, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: pass → fail
- [functional improvement] 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

### 2026-10-23 (score 61)

First indexed and scored.

## MCP tools (43)

### `fieldpulse_list_customers` (~106 tokens)

List customers

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

Input parameters:

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

### `fieldpulse_get_customer` (~33 tokens)

Get customer

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

Input parameters:

- `customer_id` (integer, required): FieldPulse customer id.

### `fieldpulse_list_customer_contacts` (~86 tokens)

List customer contacts

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

Input parameters:

- `customer_id` (integer, required): 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.

### `fieldpulse_get_customer_contact` (~53 tokens)

Get customer contact

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

Input parameters:

- `contact_id` (integer, required): Customer contact id.
- `customer_id` (integer, required): FieldPulse customer id.

### `fieldpulse_list_jobs` (~205 tokens)

List jobs

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

Input parameters:

- `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).

### `fieldpulse_get_job` (~53 tokens)

Get job

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

Input parameters:

- `job_id` (integer, required): FieldPulse job id.
- `with_custom_fields` (boolean): Include custom field values.

### `fieldpulse_list_job_status_workflows` (~64 tokens)

List job status workflows

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

Input parameters:

- `limit` (integer): Records per page, 1-100 (default 25).

### `fieldpulse_list_job_workflow_statuses` (~62 tokens)

List job workflow statuses

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

Input parameters:

- `limit` (integer): Records per page, 1-100 (default 25).

### `fieldpulse_list_estimates` (~114 tokens)

List estimates

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

Input parameters:

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

### `fieldpulse_get_estimate` (~35 tokens)

Get estimate

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

Input parameters:

- `estimate_id` (integer, required): FieldPulse estimate id.

### `fieldpulse_list_invoices` (~114 tokens)

List invoices

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

Input parameters:

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

### `fieldpulse_get_invoice` (~34 tokens)

Get invoice

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

Input parameters:

- `invoice_id` (integer, required): FieldPulse invoice id.

### `fieldpulse_list_payments` (~101 tokens)

List payments

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

Input parameters:

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

### `fieldpulse_get_payment` (~33 tokens)

Get payment

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

Input parameters:

- `payment_id` (integer, required): FieldPulse payment id.

### `fieldpulse_list_assets` (~88 tokens)

List assets

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

Input parameters:

- `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)

### `fieldpulse_get_asset` (~33 tokens)

Get asset

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

Input parameters:

- `asset_id` (integer, required): FieldPulse asset id.

### `fieldpulse_list_asset_categories` (~75 tokens)

List asset categories

List asset categories. GET /assets-category.

Input parameters:

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

### `fieldpulse_list_locations` (~97 tokens)

List locations

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

Input parameters:

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

### `fieldpulse_get_location` (~33 tokens)

Get location

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

Input parameters:

- `location_id` (integer, required): FieldPulse location id.

### `fieldpulse_list_projects` (~96 tokens)

List projects

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

Input parameters:

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

### `fieldpulse_get_project` (~33 tokens)

Get project

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

Input parameters:

- `project_id` (integer, required): FieldPulse project id.

### `fieldpulse_list_contracts` (~40 tokens)

List contracts

List contracts (maintenance agreements). GET /contracts.

Input parameters:

- `limit` (integer): Records per page, 1-100 (default 25).

### `fieldpulse_get_contract` (~33 tokens)

Get contract

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

Input parameters:

- `contract_id` (integer, required): FieldPulse contract id.

### `fieldpulse_list_items` (~70 tokens)

List items

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

Input parameters:

- `limit` (integer): Records per page, 1-100 (default 25).
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.

### `fieldpulse_get_item` (~34 tokens)

Get item

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

Input parameters:

- `item_id` (integer, required): FieldPulse item id.

### `fieldpulse_list_purchase_orders` (~64 tokens)

List purchase orders

List purchase orders. GET /purchase-orders.

Input parameters:

- `limit` (integer): Records per page, 1-100 (default 25).
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.

### `fieldpulse_get_purchase_order` (~38 tokens)

Get purchase order

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

Input parameters:

- `purchase_order_id` (integer, required): FieldPulse purchase order id.

### `fieldpulse_list_vendors` (~51 tokens)

List vendors

List vendors (suppliers). GET /vendors.

Input parameters:

- `limit` (integer): Records per page, 1-100 (default 25).
- `search` (string): Free-text search string.

### `fieldpulse_get_vendor` (~33 tokens)

Get vendor

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

Input parameters:

- `vendor_id` (integer, required): FieldPulse vendor id.

### `fieldpulse_list_company_profiles` (~91 tokens)

List company profiles

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

Input parameters:

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

### `fieldpulse_list_users` (~47 tokens)

List users

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

Input parameters:

- `limit` (integer): Records per page, 1-100 (default 25).

### `fieldpulse_list_teams` (~65 tokens)

List teams

List the account's teams. GET /teams.

Input parameters:

- `limit` (integer): Records per page, 1-100 (default 25).
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.

### `fieldpulse_list_tags` (~73 tokens)

List tags

List tags for customers or jobs. GET /tags.

Input parameters:

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

### `fieldpulse_list_lead_sources` (~66 tokens)

List lead sources

List customer lead sources. GET /lead-source.

Input parameters:

- `limit` (integer): Records per page, 1-100 (default 25).
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.

### `fieldpulse_list_pipeline_statuses` (~66 tokens)

List pipeline statuses

List customer pipeline statuses. GET /pipeline-status.

Input parameters:

- `limit` (integer): Records per page, 1-100 (default 25).
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.

### `fieldpulse_list_custom_fields` (~79 tokens)

List custom fields

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

Input parameters:

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

### `fieldpulse_list_comments` (~99 tokens)

List comments

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

Input parameters:

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

### `fieldpulse_list_subtasks` (~116 tokens)

List subtasks

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

Input parameters:

- `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)

### `fieldpulse_list_timesheets` (~115 tokens)

List timesheets

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

Input parameters:

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

### `fieldpulse_create_customer` (~356 tokens)

Create customer

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.

Input parameters:

- `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.
- `email` (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).

### `fieldpulse_update_customer` (~361 tokens)

Update customer

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

Input parameters:

- `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, required): FieldPulse customer id.
- `display_name` (string): Required by FieldPulse when first and last name are empty; must be unique.
- `email` (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).

### `fieldpulse_create_job` (~352 tokens)

Create job

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.

Input parameters:

- `assignments` (array): Who the job is assigned to.
- `billing` (integer, required): The integer billing value FieldPulse requires for a job.
- `customer_contact_id`
- `customer_id` (integer, required): 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, required): 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).

### `fieldpulse_update_job` (~360 tokens)

Update job

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

Input parameters:

- `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, required): 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).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-fieldpulse/fieldpulse#diagnostics

## Score history

- 2026-10-25: 62
- 2026-10-24: 62
- 2026-10-23: 61

## Common questions

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

## Links

- Remote endpoint: https://fieldpulse.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/fieldpulse/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-fieldpulse/fieldpulse.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-fieldpulse/fieldpulse.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-fieldpulse/fieldpulse