AI Form API (fill) is an MCP server published by io.github.sum-eet, hosted at aiformapi.com. When last checked on 2026-11-21 it was working: it answers and lists its tools. It declares 2 tools, including get_fill_form, submit_fill.
Read and submit one AI Form API form for a person, with a one-time fill code. No login.
789 connections through 5 shared values. Tap any node.
Inferred from the host name and headers: what a server runs on, not who runs it.
Read the form behind a fill code: questions, types, limits and what to do next. Does not use up the code. Ask the person for missing answers, show them everything, and submit only after they say yes.
| Parameter | Type | Description |
|---|---|---|
| fill_token * | string | The fill code from the prompt, starting with fil_ |
{
"name": "get_fill_form",
"title": "Get the form to fill",
"description": "Read the form behind a fill code: questions, types, limits and what to do next. Does not use up the code. Ask the person for missing answers, show them everything, and submit only after they say yes.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"fill_token"
],
"properties": {
"fill_token": {
"type": "string",
"description": "The fill code from the prompt, starting with fil_"
}
}
}
}None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Submit answers with a fill code. One successful use per code, at most 5 attempts. 201-equivalent result has response_id and receipt: tell the person the receipt. On invalid_answers fix the listed fields and call again.
| Parameter | Type | Description |
|---|---|---|
| answers * | object | Map of field id to value |
| fill_token * | string | The fill code from the prompt, starting with fil_ |
{
"name": "submit_fill",
"title": "Submit the answers",
"description": "Submit answers with a fill code. One successful use per code, at most 5 attempts. 201-equivalent result has response_id and receipt: tell the person the receipt. On invalid_answers fix the listed fields and call again.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"fill_token",
"answers"
],
"properties": {
"answers": {
"type": "object",
"description": "Map of field id to value",
"propertyNames": {
"type": "string"
},
"additionalProperties": {}
},
"fill_token": {
"type": "string",
"description": "The fill code from the prompt, starting with fil_"
}
}
}
}Names, descriptions and schemas were written by the server and are shown as data.
Shared addresses on big platforms (Cloudflare, Vercel and the like) put unrelated servers together; those are marked shared_infrastructure. A match is a pivot, not a link between operators.