Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Inquira

REMOTE · GETINQUIRA.COM

AI survey platform: create and publish surveys, collect responses, generate AI analysis reports.

Available components

0 this week 76 Trust /100

Last scanned (23 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Data and Analytics

Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 282 tokens (~47/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "publish_survey" implies "publish" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 6 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
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

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 21 Nov 2026 · Probed https://getinquira.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.getinquira.com CN=YR1,O=Let's Encrypt,C=US 19 Nov 2026 17 Feb 2027 RSA 2048 SHA256-RSA 66874f62dd63d1ea20f7b8a64e567ce9e8e
SANs: *.getinquira.com, getinquira.com
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 getinquira.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
getinquira.com. No DS 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
streamable-http https://getinquira.com/api/mcp Verified 200
http (plaintext) http://getinquira.com/api/mcp HTTPS enforced 308 https://getinquira.com/api/mcp
MCP tools · 6 exposed · ~282 tokens

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 →

Tool Tokens
create_survey ~94

Generate a professional survey using AI based on a research goal. Returns the survey ID and shareable link.

NameTypeReqDescription
goalstringyesDescribe what you want to research. E.g. 'Customer satisfaction survey for our SaaS product after onboarding'
langstring–Language for the survey content. Defaults to 'en'.
publishboolean–Whether to immediately publish the survey after creation. Defaults to false.

No output schema declared.

No examples provided.

get_ai_report ~50

Generate an AI analysis report for a survey's responses. Returns executive summary, key metrics, per-question insights, and action recommendations.

NameTypeReqDescription
survey_idstringyesThe ID of the survey to analyze.

No output schema declared.

No examples provided.

get_responses ~35

Get all responses submitted to a specific survey.

NameTypeReqDescription
survey_idstringyesThe ID of the survey to get responses for.

No output schema declared.

No examples provided.

get_survey_link ~33

Get the shareable link for a published survey.

NameTypeReqDescription
survey_idstringyesThe ID of the survey.

No output schema declared.

No examples provided.

get_surveys ~34

List all surveys belonging to the authenticated user.

NameTypeReqDescription
statusstring–Filter by survey status. Defaults to 'all'.

No output schema declared.

No examples provided.

publish_survey ~36

Publish a survey to make it accessible via its share link.

NameTypeReqDescription
survey_idstringyesThe ID of the survey to publish.

No output schema declared.

No examples provided.

Install

How do I install the Inquira MCP server?

Inquira is a hosted endpoint at https://getinquira.com/api/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 · getinquira.com

# add to Claude Code
claude mcp add --transport http com-getinquira-inquira 'https://getinquira.com/api/mcp'
Common questions

What is the Inquira MCP server?

Inquira is an MCP server listed in the public MCP registry as com.getinquira/inquira. AI survey platform: create and publish surveys, collect responses, generate AI analysis reports. This page covers its hosted endpoint (https://getinquira.com/api/mcp).

Is the Inquira MCP server safe to use?

Inquira scores 76 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 Inquira MCP server expose?

Inquira exposes 6 tools: create_survey, get_surveys, get_responses, get_ai_report, publish_survey, get_survey_link. Their descriptions and schemas cost roughly 282 tokens of context every time the server is loaded.

Does the Inquira MCP server require authentication?

No. We connected to Inquira without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Inquira MCP server still maintained?

Inquira is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Inquira MCP server?

VerifyMCP ran 12 checks on Inquira, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Inquira: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.