fal.ai MCP by usefulapi
REMOTE · FALAI.USEFULAPI.IO
Run fal.ai models, poll the inference queue and read model schemas.
Available components
Last scanned (9 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 22 Oct 2026.
Category AI and Machine Learning
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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1040 tokens (~148/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 22 Oct 26 0
- Server version: 1.16.3 → 1.16.4 functional
- 21 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.14.0 → 1.16.3 functional
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: unverified → 100 ▲ functional
- The server now declares the “prompts” capability functional
- New prompt “getting_started” functional
- Server version: 1.13.0 → 1.14.0 functional
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 −13
- HTTPS: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.9.0 → 1.13.0 functional
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 22 Oct 2026 · Probed https://falai.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 falai.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://falai.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://falai.usefulapi.io/.well-known/oauth-protected-resource/mcp" Protected resource metadata
| Document | https://falai.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://falai.usefulapi.io/mcp |
| Authorisation server | https://falai.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://falai.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/falai/ |
| http (plaintext) | http://falai.usefulapi.io/mcp | Inconclusive | 302 | http://falai.usefulapi.io/mcp |
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 →
falai_cancel_request Cancel request ~107
Request cancellation of a queued (not-yet-started) request. Returns 202 { status: 'CANCELLATION_REQUESTED' }. fal.ai queue: PUT {queue}/{model_id}/requests/{request_id}/cancel.
| Name | Type | Req | Description |
|---|---|---|---|
| model_id | string | yes | The fal.ai model id, used raw as a path segment, e.g. 'fal-ai/flux/schnell'. |
| request_id | string | yes | The queue request id returned when the request was submitted. |
No output schema declared.
No examples provided.
falai_get_model_schema Get model schema ~94
Get the OpenAPI 3 schema for a model — its input/output fields (components.schemas). Use this to learn what inputs a model accepts before submitting. fal.ai API: GET /openapi/queue/openapi.json?endpoint_id={model_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| model_id | string | yes | The fal.ai model id, used raw as a path segment, e.g. 'fal-ai/flux/schnell'. |
No output schema declared.
No examples provided.
falai_get_request_result Get request result ~88
Get the final output of a COMPLETED queued request. fal.ai queue: GET {queue}/{model_id}/requests/{request_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| model_id | string | yes | The fal.ai model id, used raw as a path segment, e.g. 'fal-ai/flux/schnell'. |
| request_id | string | yes | The queue request id returned when the request was submitted. |
No output schema declared.
No examples provided.
falai_get_request_status Get request status ~118
Get the status of a queued request (IN_QUEUE | IN_PROGRESS | COMPLETED). fal.ai queue: GET {queue}/{model_id}/requests/{request_id}/status (optional logs=1).
| Name | Type | Req | Description |
|---|---|---|---|
| logs | boolean | – | Include queue logs in the response (?logs=1). |
| model_id | string | yes | The fal.ai model id, used raw as a path segment, e.g. 'fal-ai/flux/schnell'. |
| request_id | string | yes | The queue request id returned when the request was submitted. |
No output schema declared.
No examples provided.
falai_list_models List models ~84
List or search fal.ai models in the registry (paginated). fal.ai API: GET /models (query: keywords, page, total).
| Name | Type | Req | Description |
|---|---|---|---|
| keywords | string | – | Optional search string to filter models by. |
| page | integer | – | 1-based page number (default 1). |
| total | integer | – | Page size (number of models per page). |
No output schema declared.
No examples provided.
falai_run_model Run model (subscribe) ~200
Convenience 'subscribe': submit a request, poll its status until COMPLETED, then return the result. Consumes fal credits. If it does not complete within the wait budget, returns a { status, request_id, status_url, note } object (NOT an error) so you can keep polling with falai_get_request_status / falai_get_request_result.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | The model's input object — arbitrary params for that model, e.g. { "prompt": "a cat" }. Use falai_get_model_schema to learn the fields. |
| max_wait_seconds | integer | – | Max seconds to wait for completion (default 60, capped at 300). |
| model_id | string | yes | The fal.ai model id, used raw as a path segment, e.g. 'fal-ai/flux/schnell'. |
| poll_interval_seconds | integer | – | Seconds between status polls (default 3, min 1). |
No output schema declared.
No examples provided.
falai_submit_request Submit request ~146
Submit an inference request to the queue and return immediately (async — does NOT wait for completion). Returns { request_id, response_url, status_url, cancel_url, queue_position }. Consumes fal credits when the model runs. fal.ai queue: POST {queue}/{model_id} with body = the model input.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | The model's input object — arbitrary params for that model, e.g. { "prompt": "a cat" }. Use falai_get_model_schema to learn the fields. |
| model_id | string | yes | The fal.ai model id, used raw as a path segment, e.g. 'fal-ai/flux/schnell'. |
No output schema declared.
No examples provided.
How do I install the fal.ai MCP by usefulapi server?
fal.ai MCP by usefulapi is a hosted endpoint at https://falai.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 · falai.usefulapi.io
claude mcp add --transport http io-usefulapi-falai 'https://falai.usefulapi.io/mcp'
What is the fal.ai MCP by usefulapi server?
fal.ai MCP by usefulapi is listed in the public MCP registry as io.usefulapi/falai. Run fal.ai models, poll the inference queue and read model schemas. This page covers its hosted endpoint (https://falai.usefulapi.io/mcp).
Is the fal.ai MCP by usefulapi server safe to use?
fal.ai MCP by usefulapi scores 73 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 fal.ai MCP by usefulapi server expose?
fal.ai MCP by usefulapi exposes 7 tools: falai_list_models, falai_get_model_schema, falai_get_request_status, falai_get_request_result, falai_submit_request, and 2 more. Their descriptions and schemas cost roughly 837 tokens of context every time the server is loaded.
Does the fal.ai MCP by usefulapi server require authentication?
Yes. fal.ai 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 fal.ai MCP by usefulapi server still maintained?
fal.ai MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.