Read and submit one AI Form API form for a person, with a one-time fill code. No login.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh 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.
The fill code from the prompt, starting with fil_
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
claude mcp add --transport http aiformapi-fill https://aiformapi.com/mcp/fill
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.
| Argument | Type | Description |
|---|---|---|
| fill_token* | string | The fill code from the prompt, starting with fil_ |
{
"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_"
}
}
}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.
| Argument | Type | Description |
|---|---|---|
| answers* | object | Map of field id to value |
| fill_token* | string | The fill code from the prompt, starting with fil_ |
{
"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_"
}
}
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Oct 30, 2026.
No readOnlyHint / destructiveHint annotations, so clients can't tell a read from a write without asking.
Fix: Add annotations to each tool, e.g. { readOnlyHint: true } for tools that only read.