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

io.usefulapi/fieldpulse

Read FieldPulse customers, jobs, estimates, invoices, assets and projects; create and update jobs. — the publisher's description

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

Summary

io.usefulapi/fieldpulse is a remote MCP server listed in the official MCP registry at version 1.4.0. On 2026-10-24 ProtocolProbe connected to it in read-only mode and read its inventory: 43 tools, 0 resources and 1 prompt.

Record checks

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

met: Registry entry is active and says how to run it
met: Source repository link opens
met: Repository is not archived
met: Code pushed to the repository in the 90 days before our check
not checked: Repository publishes a security policy (SECURITY.md)
not applicable: Package names its licence with a standard (SPDX) identifier
not applicable: The version the registry lists can be installed and is not withdrawn
not applicable: npm package carries build provenance (attestation)
not applicable: No known critical or high advisory in the package or its dependencies

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs: remote (hosted by the publisher)
Transport: streamable HTTP
Sign-in: none needed to open a session
Repository: public
Tools: 43
Last tested: 2026-10-24

Add to your client

Observed fact

This server accepted a session without any credential and lists 4 tools whose name or declaration suggests they change data (fieldpulse_create_customer, fieldpulse_update_customer, fieldpulse_create_job, fieldpulse_update_job). That is our reading of the names; we did not call them. Source: our connection, 2026-10-24.

How fresh this is

Live-tested

yes, a real session (not a text-only review)

Last tested

2026-10-24

Mode

read-only (no tool calls)

Latest version

1.4.0, published 2026-10-24 (registry, as of the 2026-10-24 snapshot)

First listed version

2026-10-23 (earliest version still in the registry; older removed versions would be earlier)

Version history

4 versions listed, 2026-10-23 to 2026-10-24; 4 in the 90 days before the 2026-10-24 snapshot.

Most recent 4 versions

1.4.0 · 2026-10-24
1.3.0 · 2026-10-24
1.2.0 · 2026-10-24
1.0.1 · 2026-10-23

(versions still listed in the registry only)

Registry data

snapshot 2026-10-24

Package and repository

checked 2026-10-24

Engine

mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-23, listed on 2026-10-24 with version 1.4.0 (published 2026-10-24).

Source: the official MCP Registry list on 2026-10-23 and on 2026-10-24.

What it is

What does this server offer?

Observed inventory

43tools

0resources

1prompts

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

fieldpulse_list_customers
“List or search customers (name, email, phone, address, status, assigned user).”
Publisher declares: read-only yes · destructive no · open-world yes
5 inputs
- searchstring“Free-text search string.”
- sort_bystring
- sort_dirstring“Sort direction.”
- pageinteger“Page number, from 1 (default 1).”
- limitinteger“Records per page, 1-100 (default 25).”
fieldpulse_get_customer
“One customer by id.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- customer_idintegerrequired“FieldPulse customer id.”
fieldpulse_list_customer_contacts
“The contacts (people) of one customer.”
Publisher declares: read-only yes · destructive no · open-world yes
3 inputs, 1 required
- customer_idintegerrequired“FieldPulse customer id.”
- pageinteger“Page number, from 1 (default 1).”
- limitinteger“Records per page, 1-100 (default 25).”
fieldpulse_get_customer_contact
“One contact of a customer.”
Publisher declares: read-only yes · destructive no · open-world yes
2 inputs, 2 required
- customer_idintegerrequired“FieldPulse customer id.”
- contact_idintegerrequired“Customer contact id.”
fieldpulse_list_jobs
“List or search jobs (type, status, customer, schedule, assignments), optionally within a created-at range or by custom status ids.”
Publisher declares: read-only yes · destructive no · open-world yes
9 inputs
- searchstring“Free-text search string.”
- sort_bystring
- sort_dirstring“Sort direction.”
- created_fromstring“Only jobs created at or after this time (yyyy-mm-dd or ISO 8601 with a timezone).”
- created_tostring“Only jobs created at or before this time.”
- status_idsarray“Only jobs in these custom status ids (see fieldpulse_list_job_workflow_statuses).”
- with_custom_fieldsboolean“Include each job's custom field values (customfields_with_related_data).”
- pageinteger“Page number, from 1 (default 1).”
- limitinteger“Records per page, 1-100 (default 25).”
fieldpulse_get_job
“One job by id, optionally with its custom field values.”
Publisher declares: read-only yes · destructive no · open-world yes
2 inputs, 1 required
- job_idintegerrequired“FieldPulse job id.”
- with_custom_fieldsboolean“Include custom field values.”
fieldpulse_list_job_status_workflows
“The job status workflows (use their ids with fieldpulse_list_job_workflow_statuses and when setting a custom job status).”
Publisher declares: read-only yes · destructive no · open-world yes
1 input
- limitinteger“Records per page, 1-100 (default 25).”
fieldpulse_list_job_workflow_statuses
“The custom job statuses of all workflows, with their ids (for filtering jobs or setting a status).”
Publisher declares: read-only yes · destructive no · open-world yes
1 input
- limitinteger“Records per page, 1-100 (default 25).”
fieldpulse_list_estimates
“List or search estimates (customer, status, totals, line items).”
Publisher declares: read-only yes · destructive no · open-world yes
5 inputs
- searchstring“Free-text search string.”
- sort_bystring“An attribute of the record, e.g.”
- sort_dirstring“Sort direction.”
- pageinteger“Page number, from 1 (default 1).”
- limitinteger“Records per page, 1-100 (default 25).”
fieldpulse_get_estimate
“One estimate by id.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- estimate_idintegerrequired“FieldPulse estimate id.”
fieldpulse_list_invoices
“List or search invoices (customer, status, totals, due dates).”
Publisher declares: read-only yes · destructive no · open-world yes
5 inputs
- searchstring“Free-text search string.”
- sort_bystring“An attribute of the record, e.g.”
- sort_dirstring“Sort direction.”
- pageinteger“Page number, from 1 (default 1).”
- limitinteger“Records per page, 1-100 (default 25).”
fieldpulse_get_invoice
“One invoice by id.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- invoice_idintegerrequired“FieldPulse invoice id.”

Show 31 more tools

fieldpulse_list_payments
“List or search payments (amount, method, date, invoice).”
Publisher declares: read-only yes · destructive no · open-world yes
5 inputs
- searchstring“Free-text search string.”
- sort_bystring
- sort_dirstring“Sort direction.”
- pageinteger“Page number, from 1 (default 1).”
- limitinteger“Records per page, 1-100 (default 25).”
fieldpulse_get_payment
“One payment by id.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- payment_idintegerrequired“FieldPulse payment id.”
fieldpulse_list_assets
“List or search customer assets (equipment) by install status.”
Publisher declares: read-only yes · destructive no · open-world yes
4 inputs
- searchstring“Free-text search string.”
- statusstring
- pageinteger“Page number, from 1 (default 1).”
- limitinteger“Records per page, 1-100 (default 25).”
fieldpulse_get_asset
“One asset by id.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- asset_idintegerrequired“FieldPulse asset id.”
fieldpulse_list_asset_categories
“List asset categories.”
Publisher declares: read-only yes · destructive no · open-world yes
3 inputs
- searchstring“Free-text search string.”
- pageinteger“Page number, from 1 (default 1).”
- limitinteger“Records per page, 1-100 (default 25).”
fieldpulse_list_locations
“List locations (service addresses) of a customer or a job.”
Publisher declares: read-only yes · destructive no · open-world yes
4 inputs
- object_typestring
- object_idinteger“Id of the customer or job (needs object_type).”
- pageinteger“Page number, from 1 (default 1).”
- limitinteger“Records per page, 1-100 (default 25).”
fieldpulse_get_location
“One location by id.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- location_idintegerrequired“FieldPulse location id.”
fieldpulse_list_projects
“List or search projects (status, completion).”
Publisher declares: read-only yes · destructive no · open-world yes
5 inputs
- searchstring“Free-text search string.”
- sort_bystring
- sort_dirstring“Sort direction.”
- pageinteger“Page number, from 1 (default 1).”
- limitinteger“Records per page, 1-100 (default 25).”
fieldpulse_get_project
“One project by id.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- project_idintegerrequired“FieldPulse project id.”
fieldpulse_list_contracts
“List contracts (maintenance agreements).”
Publisher declares: read-only yes · destructive no · open-world yes
1 input
- limitinteger“Records per page, 1-100 (default 25).”
fieldpulse_get_contract
“One contract by id.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- contract_idintegerrequired“FieldPulse contract id.”
fieldpulse_list_items
“List the invoice item catalog (products and services with prices).”
Publisher declares: read-only yes · destructive no · open-world yes
2 inputs
- pageinteger“Page number, from 1 (default 1).”
- limitinteger“Records per page, 1-100 (default 25).”
fieldpulse_get_item
“One invoice item by id.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- item_idintegerrequired“FieldPulse item id.”
fieldpulse_list_purchase_orders
“List purchase orders.”
Publisher declares: read-only yes · destructive no · open-world yes
2 inputs
- pageinteger“Page number, from 1 (default 1).”
- limitinteger“Records per page, 1-100 (default 25).”
fieldpulse_get_purchase_order
“One purchase order by id.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- purchase_order_idintegerrequired“FieldPulse purchase order id.”
fieldpulse_list_vendors
“List vendors (suppliers).”
Publisher declares: read-only yes · destructive no · open-world yes
2 inputs
- searchstring“Free-text search string.”
- limitinteger“Records per page, 1-100 (default 25).”
fieldpulse_get_vendor
“One vendor by id.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- vendor_idintegerrequired“FieldPulse vendor id.”
fieldpulse_list_company_profiles
“The company profile(s) of this FieldPulse account (name, address, contact details, settings).”
Publisher declares: read-only yes · destructive no · open-world yes
3 inputs
- searchstring“Free-text search string.”
- pageinteger“Page number, from 1 (default 1).”
- limitinteger“Records per page, 1-100 (default 25).”
fieldpulse_list_users
“List the account's users (team members) with ids for assignments.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input
- limitinteger“Records per page, 1-100 (default 25).”
fieldpulse_list_teams
“List the account's teams.”
Publisher declares: read-only yes · destructive no · open-world yes
2 inputs
- pageinteger“Page number, from 1 (default 1).”
- limitinteger“Records per page, 1-100 (default 25).”
fieldpulse_list_tags
“List tags for customers or jobs.”
Publisher declares: read-only yes · destructive no · open-world yes
3 inputs
- object_typestring
- pageinteger“Page number, from 1 (default 1).”
- limitinteger“Records per page, 1-100 (default 25).”
fieldpulse_list_lead_sources
“List customer lead sources.”
Publisher declares: read-only yes · destructive no · open-world yes
2 inputs
- pageinteger“Page number, from 1 (default 1).”
- limitinteger“Records per page, 1-100 (default 25).”
fieldpulse_list_pipeline_statuses
“List customer pipeline statuses.”
Publisher declares: read-only yes · destructive no · open-world yes
2 inputs
- pageinteger“Page number, from 1 (default 1).”
- limitinteger“Records per page, 1-100 (default 25).”
fieldpulse_list_custom_fields
“List custom field definitions, optionally for one object type.”
Publisher declares: read-only yes · destructive no · open-world yes
3 inputs
- object_typestring
- pageinteger“Page number, from 1 (default 1).”
- limitinteger“Records per page, 1-100 (default 25).”
fieldpulse_list_comments
“List comments on a record (customer, job, project, subtasks, invoice).”
Publisher declares: read-only yes · destructive no · open-world yes
4 inputs
- object_typestring
- object_idinteger“Id of the record (needs object_type).”
- pageinteger“Page number, from 1 (default 1).”
- limitinteger“Records per page, 1-100 (default 25).”
fieldpulse_list_subtasks
“List subtasks (job checklist items) by status or assigned user.”
Publisher declares: read-only yes · destructive no · open-world yes
6 inputs
- statusstring
- assigned_user_idinteger“Only subtasks assigned to this user id.”
- sort_bystring
- sort_dirstring“Sort direction.”
- pageinteger“Page number, from 1 (default 1).”
- limitinteger“Records per page, 1-100 (default 25).”
fieldpulse_list_timesheets
“List timesheet entries (clock in/out), optionally for one user or a time window.”
Publisher declares: read-only yes · destructive no · open-world yes
5 inputs
- user_idinteger“Only this user's entries.”
- in_timestring“Clock-in time filter (yyyy-mm-dd or ISO 8601 with a timezone).”
- out_timestring“Clock-out time filter.”
- typestring“Entry type, e.g.”
- limitinteger“Records per page, 1-100 (default 25).”
fieldpulse_create_customer
“WRITE: create a customer (lead or account).”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
28 inputs
- first_namestring
- last_namestring
- display_namestring“Required by FieldPulse when first and last name are empty; must be unique.”
- company_namestring
- account_typestring
- emailstring
- alt_emailstring
- secondary_emailstring
- phonestring“A valid phone number.”
- secondary_phonestring“A valid phone number.”
- statusstring
- notesstring
- job_notesstring
- assigned_tointeger or null“User id the customer is assigned to (see fieldpulse_list_users); null clears it.”
- lead_source_idinteger“See fieldpulse_list_lead_sources.”
- pipeline_status_idinteger“See fieldpulse_list_pipeline_statuses.”
- tagsarray“Existing customer tag ids (see fieldpulse_list_tags).”
- has_different_billing_addressboolean
- billing_address_1string
- billing_address_2string
- billing_citystring
- billing_statestring
- billing_zip_codestring
- service_address_1string
- service_address_2string
and 3 more not listed here.
fieldpulse_update_customer
“WRITE: change fields of one customer (only the fields you pass).”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes
29 inputs, 1 required
- customer_idintegerrequired“FieldPulse customer id.”
- first_namestring
- last_namestring
- display_namestring“Required by FieldPulse when first and last name are empty; must be unique.”
- company_namestring
- account_typestring
- emailstring
- alt_emailstring
- secondary_emailstring
- phonestring“A valid phone number.”
- secondary_phonestring“A valid phone number.”
- statusstring
- notesstring
- job_notesstring
- assigned_tointeger or null“User id the customer is assigned to (see fieldpulse_list_users); null clears it.”
- lead_source_idinteger“See fieldpulse_list_lead_sources.”
- pipeline_status_idinteger“See fieldpulse_list_pipeline_statuses.”
- tagsarray“Existing customer tag ids (see fieldpulse_list_tags).”
- has_different_billing_addressboolean
- billing_address_1string
- billing_address_2string
- billing_citystring
- billing_statestring
- billing_zip_codestring
- service_address_1string
and 4 more not listed here.
fieldpulse_create_job
“WRITE: create a job for an existing customer.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
17 inputs, 3 required
- customer_idintegerrequired“Existing customer id.”
- job_typestringrequired“Job type label, e.g.”
- billingintegerrequired“The integer billing value FieldPulse requires for a job.”
- subtitlestring
- notesstring
- field_notesstring
- statusinteger“1 = new, 2 = in progress, 3 = pending, 4 = completed, 5 = canceled, 6 = on the way.”
- status_idinteger“A custom status id (see fieldpulse_list_job_workflow_statuses); needs status_workflow_id.”
- status_workflow_idinteger“The status workflow of status_id (see fieldpulse_list_job_status_workflows).”
- start_timestring or null“Start, yyyy-mm-dd or ISO 8601 with a timezone.”
- end_timestring or null“End, yyyy-mm-dd or ISO 8601 with a timezone.”
- due_datestring or null“Due date, yyyy-mm-dd or ISO 8601 with a timezone.”
- location_idinteger or null“A location of the customer (see fieldpulse_list_locations).”
- project_idinteger or null
- customer_contact_idinteger or null
- assignmentsarray“Who the job is assigned to.”
- tagsarray“Existing job tag ids (see fieldpulse_list_tags).”
fieldpulse_update_job
“WRITE: change a job: status, schedule, notes, assignments, location.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes
18 inputs, 1 required
- job_idintegerrequired“FieldPulse job id.”
- customer_idinteger
- job_typestring
- billinginteger
- subtitlestring
- notesstring
- field_notesstring
- statusinteger“1 = new, 2 = in progress, 3 = pending, 4 = completed, 5 = canceled, 6 = on the way.”
- status_idinteger“A custom status id (see fieldpulse_list_job_workflow_statuses); needs status_workflow_id.”
- status_workflow_idinteger“The status workflow of status_id (see fieldpulse_list_job_status_workflows).”
- start_timestring or null“Start, yyyy-mm-dd or ISO 8601 with a timezone.”
- end_timestring or null“End, yyyy-mm-dd or ISO 8601 with a timezone.”
- due_datestring or null“Due date, yyyy-mm-dd or ISO 8601 with a timezone.”
- location_idinteger or null“A location of the customer (see fieldpulse_list_locations).”
- project_idinteger or null
- customer_contact_idinteger or null
- assignmentsarray“Who the job is assigned to.”
- tagsarray“Existing job tag ids (see fieldpulse_list_tags).”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-24.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description: 66% of 195
Tools with a description: 100% of 43
Typical description length: 82 characters

The tool set

Counted from the listing

Tools: 43
Size of the list: about 9,632 tokens for an agent to load (characters ÷ 4)
Naming: 43 of 43 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 43 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none, comparing tools within groups of 40. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-24 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai

Settings → Connectors → Add custom connector, then paste:
https://fieldpulse.usefulapi.io/mcp

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

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

VS Code · .vscode/mcp.json

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

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

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

Claude Code

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

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 --server-url https://fieldpulse.usefulapi.io/mcp --transport http

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

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

Does the registry listing match what we found?

Feature #6

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

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

Who made it?

Feature #7 · lineage

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

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

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

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

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

Choosing

Record checks

Public records · not a safety rating

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

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

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

Common questions about io.usefulapi/fieldpulse

Answered from the data above

Is io.usefulapi/fieldpulse safe to install?

We do not rate servers as safe or unsafe. 4 of its 4 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does io.usefulapi/fieldpulse need an API key or sign-in?

It opened a session without any credential on 2026-10-24. The registry entry declares no required credential; no declaration is not a guarantee.

Has io.usefulapi/fieldpulse been security tested?

Partly. 3 of the 16 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security verdict is published before verification.

Where is the source code of io.usefulapi/fieldpulse?

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

Found this page useful?

Anonymous · no sign-in

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

Compare with another server

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

Security testing

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

18 checks · features #1, #2

Open without sign-in

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

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

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

3 exercised13 not run (reason given)2 not applicable

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

Exercised · 3

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

Not run, with the reason · 13

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

Does not apply to this server · 2

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

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

What happened during the test?

Feature #8

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

0 msStarted a read-only session with the server's remote endpoint
337 msConnected after 0 redirects. No credential was sent or needed.
Read the inventory: 43 tools, 0 resources, 1 prompt.
1,017 msFinished: 3 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

pending: added in the weekly update

listed 2026-10-24; not classified yet

Pricing modelAI-classified

pending: added in the weekly update

the website is not read yet

Programming language

JavaScript

api.github.com · 2026-10-24

Hosting type

remote (hosted by the publisher)

registry · 2026-10-24

MCP capability

prompts, tools

our test · 2026-10-24

Transport

streamable HTTP

registry · 2026-10-24

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

does not apply

remote-only server: no package is shipped, so there is no package registry

Freshness

0–30 days

registry updatedAt · 2026-10-24

Lifecycle status

active

registry · 2026-10-24

License class

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Integrity hash

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Signature / provenance

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Dependency advisories

does not apply

ships no package, so there are no dependencies to audit

Popularity

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Publisher signals

owner: a personal account · repository age: 91–180 days · stars: 0–9

api.github.com · 2026-10-24

Maintenance

active

api.github.com · 2026-10-24

Environment

the publisher's infrastructure

where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.usefulapi/fieldpulse: MCP server record.” Data checked 2026-10-24. https://protocolprobe.com/mcp/servers/io.usefulapi/fieldpulse

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.usefulapi/fieldpulse)](https://protocolprobe.com/mcp/servers/io.usefulapi/fieldpulse)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology