Home / MCP registry index / io.usefulapi/fieldpulse
FieldPulse MCP by usefulapi
io.usefulapi/fieldpulse in the official MCP registry.
Endpoint https://fieldpulse.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Read FieldPulse customers, jobs, estimates, invoices, assets and projects; create and update jobs.
We read its 43 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
fieldpulse_list_customers fieldpulse_get_customer fieldpulse_list_customer_contacts fieldpulse_get_customer_contact fieldpulse_list_jobs fieldpulse_get_job fieldpulse_list_job_status_workflows fieldpulse_list_job_workflow_statuses fieldpulse_list_estimates fieldpulse_get_estimate fieldpulse_list_invoices fieldpulse_get_invoice fieldpulse_list_payments fieldpulse_get_payment fieldpulse_list_assets fieldpulse_get_asset fieldpulse_list_asset_categories fieldpulse_list_locations fieldpulse_get_location fieldpulse_list_projects fieldpulse_get_project fieldpulse_list_contracts fieldpulse_get_contract fieldpulse_list_items fieldpulse_get_item fieldpulse_list_purchase_orders fieldpulse_get_purchase_order fieldpulse_list_vendors fieldpulse_get_vendor fieldpulse_list_company_profiles fieldpulse_list_users fieldpulse_list_teams fieldpulse_list_tags fieldpulse_list_lead_sources fieldpulse_list_pipeline_statuses fieldpulse_list_custom_fields fieldpulse_list_comments fieldpulse_list_subtasks fieldpulse_list_timesheets fieldpulse_create_customer fieldpulse_update_customer fieldpulse_create_job fieldpulse_update_job
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-fieldpulse)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.