io.github.CloudCorpRecords/formfurrow
formfurrow
Is the io.github.CloudCorpRecords/formfurrow MCP server down? No. It answered initialize and tools/list in the probe of 2026-11-07.
Run a form backend end to end: teams, clients, projects, forms, submissions, snippets, webhooks.
alive probed 2026-11-14 · unchanged since 2026-11-07
- Run it
- npx -y @reneturcios/formfurrow@0.1.0 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- formfurrow 0.1.0
- Capabilities
- tools
- Instructions
- none
- Of a 1M window
- 2.6 % of a 1M context window
- Count
- 26k tokens in Claude Opus 5.5, exact, measured 2026-11-07. With the Claude Code prefix mcp__…__ on each tool name: 26k. The o200k_base estimate is 15k. Counted again when the tool definitions change. Method.
- Repository
- https://github.com/CloudCorpRecords/formfurrow
- Registry
- active, updated 2026-11-04 · registry entry
- Changes
- 2 recorded, reachable in 2 of them. A row is added when the result, the tool count or the cost changes.
Most expensive tools
The Claude column scales the o200k estimate of each tool by this server's ratio of exact to estimate, 1.67×.
| Tool | ≈ Claude tokens | o200k estimate | Share of this server |
|---|---|---|---|
| bootstrap_site | 4 602 | 2 749 | 18 % |
| update_project | 2 868 | 1 713 | 11 % |
| create_project | 2 752 | 1 644 | 11 % |
| create_form | 1 867 | 1 115 | 7 % |
| update_form | 1 815 | 1 084 | 7 % |
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- io.github.CloudCorpRecords/flightdata · alive
- io.github.CloudCorpRecords/flowcheck · alive
- io.github.CloudCorpRecords/formchime · alive
- io.github.CloudCorpRecords/formfill · alive
- io.github.CloudCorpRecords/formwire · alive
- io.github.CloudCorpRecords/forumport · alive
- io.github.CloudCorpRecords/freightlane · alive
- io.github.CloudCorpRecords/freshcheck · alive
Servers that mention submissions or projects.
- Dubai Data — Dubai real estate statistics ae.datadubai/dubai-real-estate · alive
- Alpic ai.alpic.mcp/alpic-mcp · needs auth
- Atako ai.atako/mcp · needs auth
- Project Desk ai.atlier/project-desk · needs auth
- AutoRFP.ai ai.autorfp/mcp · needs auth
- BeatBandit MCP ai.beatbandit/beatbandit · needs auth
- ai.bridgeapp/bridgeapp · needs auth
- Data Center Index ai.datacenterindex/datacenterindex · needs auth
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-11-07 07:50 | alive | 164 ms | 26 | 26k | 15k |
| 2026-11-05 08:34 | alive | 217 ms | 26 | 26k | 15k |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- This server is in the heaviest 10 % of the registry. Its 5 most expensive tools are 54 % of the cost. Shorter descriptions, fewer optional parameters and fewer tools cut the cost. The command npx mcpcost --url <endpoint> --tools 50 lists every tool with its cost.