Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Forms On Fire / Appenate MCP by usefulapi

REMOTE · FORMS-ON-FIRE.USEFULAPI.IO

Read mobile forms, entries, users and tasks; create confirmed draft or sent tasks for field workers.

−46 this week 18 Trust /100

Last scanned (5 hours ago)

Scores higher than 4% of remote servers

Reachable. Last reached 7 Nov 2026.

Category Project Management

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security46
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (4)

  • TLS certificate
  • HSTS header
  • DNSSEC
  • Transport

Checks we could not complete (7)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 1 Nov 26 −46
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: pass → unverified ▼ security
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 31 Oct 26 64

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 7 Nov 2026 · Probed https://forms-on-fire.usefulapi.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=usefulapi.io CN=WE1,O=Google Trust Services,C=US 13 Sept 2026 12 Dec 2026 ECDSA 256 ECDSA-SHA256 d9be3287b0fde9630e825ba1f79bff3f
SANs: usefulapi.io, *.usefulapi.io
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of forms-on-fire.usefulapi.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
usefulapi.io. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 302

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://forms-on-fire.usefulapi.io/mcp Redirected 302 https://usefulapi.io/forms-on-fire/
http (plaintext) http://forms-on-fire.usefulapi.io/mcp Inconclusive 302 http://forms-on-fire.usefulapi.io/mcp
MCP tools · 11 exposed · ~1,921 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
formsonfire_create_task ~355

WRITE: create a task for a field worker with one form to fill out, optionally with prefilled answers. By default it remains a draft; send_immediate=true sends it and notifies the worker. Identify the worker by email, user id or external id (list_users). The form is identified by its external id (formsonfire_get_form shows field names for the prefilled answers). Requires confirm=true and a due time. Not idempotent: calling twice creates two tasks. POST /task.

NameTypeReqDescription
additional_infostring–Free-text instructions shown with the task.
answersarray–Prefilled answers: field data name and value.
complete_bystringyesDue time (ISO 8601 UTC).
confirmbooleanyesSet true only after the user approved creating the task and any requested notification.
form_external_idstringyesExternal id of the form the worker has to fill out.
iconstring–Task icon name (vendor icon list), e.g. Clock.
instructionstring–Instruction shown for this form activity.
namestring–Task name shown on the device, e.g. 'Site inspection - Acme'.
send_immediateboolean–Notify the worker right away (vendor default applies when omitted).
start_bystring–When the task should be started (ISO 8601 UTC).
user_emailstring–Email of the worker (user) the task is assigned to.
user_external_idstring–External id of the worker the task is assigned to.
user_idstring–Id (GUID) of the worker the task is assigned to.

No output schema declared.

No examples provided.

formsonfire_get_data_source ~156

One data source by id (GUID) or external id: its column headers, TotalRows and (with return_rows) a page of rows. Rows are only returned when return_rows is true; page through them with page_no. GET /datasource.

NameTypeReqDescription
external_idstring–Data source external id.
idstring–Data source id (GUID).
page_nointeger–Page number, starting at 0 (default 0). Pass the previous reply's next_page_no.
page_sizeinteger–Rows per page, 1-1250 (default 50).
return_rowsboolean–Also return the rows (default false: headers and total only).

No output schema declared.

No examples provided.

formsonfire_get_form ~108

One form's definition: name, version, status and its fields (names and types, which are the names to use for prefilled answers). Give the form's id (GUID) or its external id. GET /screen/form.

NameTypeReqDescription
external_idstring–Form external id.
idstring–Form id (GUID).
statusstring–Form status (default: Published).
versioninteger–Form version (default: the latest published).

No output schema declared.

No examples provided.

formsonfire_get_task ~100

One task by its id (GUID), with activities and history. GET /task.

NameTypeReqDescription
answer_formatstring–How form answers are shaped: Flat (one value per field, easiest to read), Rich (typed values) or Raw (as stored). Default: the vendor's default.
idstringyesTask id (GUID).
retrieve_entriesboolean–Also return the form entries completed by the task's activities.

No output schema declared.

No examples provided.

formsonfire_get_user ~46

One user by id (GUID): name, status, groups, folders, role and registered devices. GET /user.

NameTypeReqDescription
idstringyesUser id (GUID).

No output schema declared.

No examples provided.

formsonfire_list_data_sources ~122

List the data sources (lookup tables that feed dropdowns and prefill in forms, such as customers, sites or products): id, external id, name and row count. Use formsonfire_get_data_source for the rows. GET /datasource/search.

NameTypeReqDescription
namestring–Data source name.
page_nointeger–Page number, starting at 0 (default 0). Pass the previous reply's next_page_no.
page_sizeinteger–Results per page, 1-250 (default 50).

No output schema declared.

No examples provided.

formsonfire_list_forms ~100

List the forms (screens) in the organization with id, name, version and status. Use a form id with formsonfire_get_form or formsonfire_search_entries. GET /screen/form/search.

NameTypeReqDescription
page_nointeger–Page number, starting at 0 (default 0). Pass the previous reply's next_page_no.
page_sizeinteger–Results per page, 1-250 (default 50).

No output schema declared.

No examples provided.

formsonfire_list_groups ~112

List user groups with their id, name and member user ids. Filter by name or external id. Returns UserGroups with TotalRows. GET /usergroup/search.

NameTypeReqDescription
external_idstring–Group external id.
namestring–Group name.
page_nointeger–Page number, starting at 0 (default 0). Pass the previous reply's next_page_no.
page_sizeinteger–Results per page, 1-250 (default 50).

No output schema declared.

No examples provided.

formsonfire_list_users ~96

List the organization's users (field workers and admins): name, email, status, groups, website role and last activity. Passwords and keys are never returned. GET /user/search.

NameTypeReqDescription
page_nointeger–Page number, starting at 0 (default 0). Pass the previous reply's next_page_no.
page_sizeinteger–Results per page, 1-250 (default 50).

No output schema declared.

No examples provided.

formsonfire_search_entries ~394

Search submitted form entries (the completed forms your team sent in): who filled them, when, where (GPS) and every answer. Filter by form id or external id, version and a date range (by received time, or complete time via order_by). Returns the page of Entries with TotalRows. GET /formentry/search.

NameTypeReqDescription
answer_formatstring–How form answers are shaped: Flat (one value per field, easiest to read), Rich (typed values) or Raw (as stored). Default: the vendor's default.
date_orderstring–Sort direction (default Ascending, oldest first).
fieldsstring–Comma-separated field names to return (works with answer_format Flat).
form_external_idstring–Only entries of the form with this external id.
form_idstring–Only entries of this form (id, GUID).
form_versioninteger–Form version; 0 or omitted = the latest published version, -1 = all versions.
from_datestring–ISO 8601 UTC date (2026-10-01) or date-time (2026-10-01T08:00:00Z).
media_as_urlboolean–Return photos/signatures as URLs instead of embedded data.
order_bystring–Sort and date-filter by ReceivedTime (default) or CompleteTime (when the form was completed on the device).
page_nointeger–Page number, starting at 0 (default 0). Pass the previous reply's next_page_no.
page_sizeinteger–Results per page, 1-250 (default 50).
to_datestring–ISO 8601 UTC date (2026-10-01) or date-time (2026-10-01T08:00:00Z).

No output schema declared.

No examples provided.

formsonfire_search_tasks ~332

Search tasks (jobs assigned to field workers, each with one or more activities such as filling out a form): status, assignee, due time, activities and history. Filter by assignee, status, name, task template and date range. Returns the page of Tasks with TotalRows. GET /task/search.

NameTypeReqDescription
answer_formatstring–How form answers are shaped: Flat (one value per field, easiest to read), Rich (typed values) or Raw (as stored). Default: the vendor's default.
from_datestring–ISO 8601 UTC date (2026-10-01) or date-time (2026-10-01T08:00:00Z).
namestring–Task name.
page_nointeger–Page number, starting at 0 (default 0). Pass the previous reply's next_page_no.
page_sizeinteger–Results per page, 1-250 (default 50).
retrieve_entriesboolean–Also return the form entries completed by the task's activities.
statusstring–Only tasks in this status.
template_idstring–Only tasks created from this task template id.
to_datestring–ISO 8601 UTC date (2026-10-01) or date-time (2026-10-01T08:00:00Z).
user_emailstring–Only tasks of the user with this email.
user_external_idstring–Only tasks of the user with this external id.

No output schema declared.

No examples provided.

Install

How do I install the Forms On Fire / Appenate MCP by usefulapi server?

Forms On Fire / Appenate MCP by usefulapi is a hosted endpoint at https://forms-on-fire.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.

remote · forms-on-fire.usefulapi.io

# add to Claude Code
claude mcp add --transport http io-usefulapi-forms-on-fire 'https://forms-on-fire.usefulapi.io/mcp'
Common questions

What is the Forms On Fire / Appenate MCP by usefulapi server?

Forms On Fire / Appenate MCP by usefulapi is listed in the public MCP registry as io.usefulapi/forms-on-fire. Read mobile forms, entries, users and tasks; create confirmed draft or sent tasks for field workers. This page covers its hosted endpoint (https://forms-on-fire.usefulapi.io/mcp).

Is the Forms On Fire / Appenate MCP by usefulapi server safe to use?

Forms On Fire / Appenate MCP by usefulapi scores 18 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 Forms On Fire / Appenate MCP by usefulapi server expose?

Forms On Fire / Appenate MCP by usefulapi exposes 11 tools: formsonfire_list_forms, formsonfire_get_form, formsonfire_search_entries, formsonfire_search_tasks, formsonfire_get_task, and 6 more. Their descriptions and schemas cost roughly 1,921 tokens of context every time the server is loaded.

Does the Forms On Fire / Appenate MCP by usefulapi server require authentication?

Its publisher declares no required credentials for Forms On Fire / Appenate MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the Forms On Fire / Appenate MCP by usefulapi server still maintained?

Forms On Fire / Appenate MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 7 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Forms On Fire / Appenate MCP by usefulapi server?

VerifyMCP ran 4 checks on Forms On Fire / Appenate MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about Forms On Fire / Appenate MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.