IFORM Web3 Forms MCP Server
REMOTE · IFORM.FUN · SCANNED SEP 20
Create, deploy, and manage decentralized Web3 forms on EVM chains via MCP.
Available components
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 544 tokens (~90/item across 6 items; 4 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the IFORM Web3 Forms MCP Server server?
IFORM Web3 Forms MCP Server is a hosted endpoint at https://iform.fun/api/ai/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 · iform.fun
claude mcp add --transport http robdomain-iform-mcp 'https://iform.fun/api/ai/mcp'
{
"mcpServers": {
"robdomain-iform-mcp": {
"url": "https://iform.fun/api/ai/mcp"
}
}
} {
"servers": {
"robdomain-iform-mcp": {
"type": "http",
"url": "https://iform.fun/api/ai/mcp"
}
}
} [mcp_servers.robdomain-iform-mcp] url = "https://iform.fun/api/ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"robdomain-iform-mcp": {
"type": "remote",
"url": "https://iform.fun/api/ai/mcp",
"enabled": true
}
}
} openclaw mcp add robdomain-iform-mcp --url 'https://iform.fun/api/ai/mcp' --transport streamable-http
mcp_servers:
robdomain-iform-mcp:
url: "https://iform.fun/api/ai/mcp" {
"McpServers": {
"robdomain-iform-mcp": {
"Transport": "http",
"Url": "https://iform.fun/api/ai/mcp"
}
}
} assistant mcp add robdomain-iform-mcp -t streamable-http -u 'https://iform.fun/api/ai/mcp'
{
"mcpServers": {
"robdomain-iform-mcp": {
"type": "http",
"url": "https://iform.fun/api/ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 15 Sept 26 59
First indexed and scored.
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 20 Sept 2026 · Probed https://iform.fun/api/ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.iform.fun | CN=YR1,O=Let's Encrypt,C=US | 8 Sept 2026 | 7 Dec 2026 | RSA 2048 | SHA256-RSA | 529518df2e0752687cc4b040630fef71841 |
| SANs: *.iform.fun, iform.fun | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of iform.fun. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| fun. | present | 47728 | 13 | Verified |
| iform.fun. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| sse | https://iform.fun/api/ai/mcp | Verified | 200 | |
| http (plaintext) | http://iform.fun/api/ai/mcp | HTTPS enforced | 308 | https://iform.fun/api/ai/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 →
confirm_form ~145
Registers and indexes an on-chain created form in the IFORM registry with its questions schema and transaction hash, generating the 6-character short slug (e.g. /e3qa69) and live URL.
| Name | Type | Req | Description |
|---|---|---|---|
| chainId | number | – | EVM Chain ID (4663, 42161, 10, 1). |
| formId | number | yes | On-chain Form ID emitted in the FormCreated event. |
| ownerAddress | string | – | Creator EVM wallet address. |
| schema | object | – | Form JSON schema with fields and settings. |
| title | string | – | Form title. |
| txHash | string | – | Transaction hash of the creation on the blockchain. |
No output schema declared.
No examples provided.
generate_form_transaction ~213
Constructs a ready-to-sign on-chain EVM transaction (to, data, value, chainId) for the FormFactory smart contract (createForm, closeForm, activateForm, archiveForm, updateSchemaHash) with exact 0.00005 ETH protocol fee (0x2d79883d2000).
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | The smart contract action to execute. |
| chainId | number | – | Target EVM chain ID: 4663 (Robinhood Chain), 42161 (Arbitrum One), 10 (Optimism), 1 (Ethereum). Defaults to 4663. |
| formId | number | – | The on-chain form ID (required for closeForm, activateForm, archiveForm, updateSchemaHash). |
| newSchemaHash | string | – | New schema hash (required for updateSchemaHash). |
| schema | object | – | Form schema containing fields, questions, and access gating settings. |
| title | string | – | Title of the form (required for createForm). |
No output schema declared.
No examples provided.
get_form_responses ~56
Fetches submitted responses for a specific decentralized form by form ID or slug.
| Name | Type | Req | Description |
|---|---|---|---|
| chainId | number | – | Chain ID (defaults to 4663). |
| formId | string | yes | Form ID or 6-character slug. |
No output schema declared.
No examples provided.
query_forms ~76
Queries decentralized forms by chain ID, creator wallet address, or status (active, closed, archived).
| Name | Type | Req | Description |
|---|---|---|---|
| chainId | number | – | Filter by chain ID (4663, 42161, 10, 1). |
| owner | string | – | Filter by creator wallet address. |
| status | string | – | Filter by form status. |
No output schema declared.
No examples provided.
What is the IFORM Web3 Forms MCP Server server?
IFORM Web3 Forms MCP Server is listed in the public MCP registry as io.github.robdomain/iform-mcp. Create, deploy, and manage decentralized Web3 forms on EVM chains via MCP. This page covers its hosted endpoint (https://iform.fun/api/ai/mcp).
Is the IFORM Web3 Forms MCP Server server safe to use?
IFORM Web3 Forms MCP Server scores 62 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 IFORM Web3 Forms MCP Server server expose?
IFORM Web3 Forms MCP Server exposes 4 tools: generate_form_transaction, confirm_form, query_forms, get_form_responses. Their descriptions and schemas cost roughly 490 tokens of context every time the server is loaded.
Does the IFORM Web3 Forms MCP Server server require authentication?
No. We connected to IFORM Web3 Forms MCP Server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the IFORM Web3 Forms MCP Server server still maintained?
IFORM Web3 Forms MCP Server is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.