A remote MCP server for creating and managing decentralized Web3 forms on EVM chains, letting an assistant build on-chain form transactions and read form data.
What you can do
Build ready-to-sign on-chain transactions for creating, closing, activating, archiving or updating a form's schema, including the protocol fee value and chain ID. Register and index a newly created on-chain form with its questions schema and transaction hash, producing a short slug and live URL. Query decentralized forms by chain ID, creator wallet address or status. Fetch submitted responses for a specific form by form ID or slug.
When to use it
Useful when you want an assistant to help draft and manage decentralized forms on EVM chains, or to look up existing forms and their responses without leaving the chat.
Requirements
A remote MCP endpoint; no package or local runtime is needed. The assistant connects over SSE. An EVM-compatible wallet is needed to sign and submit the transactions the server constructs, and the target chain must be supported.
Before you install
The server constructs transactions that carry a protocol fee in ETH, so signing them spends funds; review the recipient, value and chain ID before signing. Registering a form writes data to a public registry, and form responses are fetched from on-chain or indexed data that may be publicly visible. No authentication is declared.
Enable the server for the chats that should use its tools.
Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.robdomain%2Fiform-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
Multi-chain Web3 Form Builder & AI Agent Hub allowing users and autonomous AI agents to build, deploy, and manage decentralized forms across EVM chains (Robinhood Chain, Arbitrum, Optimism, Ethereum).
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.
Queries decentralized forms by chain ID, creator wallet address, or status (active, closed, archived).
ParametersownerstatuschainId
get_form_responses
Fetches submitted responses for a specific decentralized form by form ID or slug.
ParametersformIdrequiredchainId
Version history
1
v1.0.0LatestSep 16, 2026
Score
90%
90% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts
Declare a license in the repository or the registry entry.