Home / MCP registry index / io.usefulapi/fieldedge

FieldEdge MCP by usefulapi

io.usefulapi/fieldedge in the official MCP registry. Endpoint https://fieldedge.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.

The registry describes it as: Read work orders, customers and invoices; create customers, notes and work orders in FieldEdge.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

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

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

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

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

fieldedge_list_work_orders fieldedge_get_work_order fieldedge_search_work_orders_by_address fieldedge_list_work_order_assignments fieldedge_search_customers fieldedge_get_customer fieldedge_get_customer_by_phone fieldedge_search_customers_by_address fieldedge_list_customer_notes fieldedge_list_customer_attachments fieldedge_list_tags fieldedge_list_invoices fieldedge_get_invoice fieldedge_list_quotes fieldedge_get_quote fieldedge_list_agreements fieldedge_get_agreement fieldedge_list_employees fieldedge_get_employee fieldedge_list_business_units fieldedge_get_business_unit fieldedge_list_lead_sources fieldedge_get_lead_source fieldedge_list_tasks fieldedge_get_task_bundle fieldedge_list_items fieldedge_get_item fieldedge_list_item_categories fieldedge_get_item_category fieldedge_list_sales_tax_codes fieldedge_list_warehouses fieldedge_get_warehouse fieldedge_get_lead fieldedge_get_company fieldedge_create_customer fieldedge_create_customer_note fieldedge_update_customer_note fieldedge_create_tag fieldedge_add_customer_tag fieldedge_remove_customer_tag fieldedge_create_work_order fieldedge_update_work_order fieldedge_assign_technician fieldedge_update_assignment_status fieldedge_remove_assignment

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-06): 4a96eeb1fa4ff551. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-usefulapi-fieldedge/badge.svg)](https://lazaretto.dev/mcp-registry/io-usefulapi-fieldedge)

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. How tool poisoning works. What we found across the registry. Check another server.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.