Inquira vs WebAsk
Inquira is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
Inquira is a plugin bundle for AI coding tools published by Inquira. No marketplace we read lists it any more. WebAsk is an MCP server published by WebAskio. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  WebAsk | |
|---|---|---|
| Community marketplace bayarbh/inquira-agent-plugin | Removed on 2026-10-15 Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Inquirano longer listed · | WebAsk |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (getinquira.com/api/mcp) | Remote server (mcp.webask.io/mcp/v1) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/bayarbh/inquira-agent-plugin | github.com/webaskio/webask-mcp |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 5 days ago, requires a key |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of Inquira
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Create, edit and publish surveys, then read results from your AI chat.
-
create-survey io.github.feedbk-ai/create-survey
Create AI surveys with dynamic follow-up probing directly from your AI assistant.
-
survey-light com.mobopinions/survey-light
Build, target, launch and analyse consumer surveys from your AI assistant (Survey Light, 71 tools).
-
survey-builder-ai-mcp io.github.CSOAI-ORG/survey-builder-ai-mcp
AI-powered survey builder ai MCP server for agents. Supports create survey, validate questions
-
Create and run surveys by chatting. Respondents just open a link — no AI, no account.
-
user-research
End-to-end user research skill for AI agents — plan qualitative studies (research plans, screening questionnaires, interview guides), synthesize interview transcripts into…
What each says it does
Inquira
Inquira plugin for AI-powered survey creation, response collection, and analysis reports from Codex and other MCP-compatible agents.
WebAsk
Build surveys, read answers and make reports in WebAsk from an AI assistant.
How to run each
Inquira
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
WebAsk As a remote MCP server
claude mcp add --transport http webask-mcp https://mcp.webask.io/mcp/v1 --header "Authorization: Bearer <YOUR_API_KEY>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only WebAsk has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Inquira · What it can do: WebAsk · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.