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.

Likerts

NPM · @LIKERTS/MCP · 2 COMPONENTS

Manage open-source in-product surveys, collections, responses and exports with scoped access.

0 this week 76 Trust /100

Last scanned (4 hours ago)

Scores higher than 53% of npm servers

Category Data and Analytics

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.30.0, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 53 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1572 tokens (~47/item across 33 items; 33 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 Coverage74
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 10% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 7 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 33 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

  • 28 Oct 26 0
    • GHSA-f897-62hf-6gxq affects this package: high ▼ security
  • 26 Oct 26 0
    • Stability: 0.97 → pass security
  • 25 Oct 26 0
    • Stability: pass → 0.97 functional
  • 24 Oct 26 0
    • CVE-2023-54404 affects this package: high ▼ security
  • 21 Oct 26 0
    • CVE-2026-111767 affects this package: high ▼ security
    • CVE-2026-111771 affects this package: high ▼ security
    • CVE-2026-111768 affects this package: high ▼ security
    • CVE-2026-111769 affects this package: high ▼ security
  • 17 Oct 26 +1
    • Stability: 0.90 → pass security
  • 15 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Oct 26 −2
    • Stability: pass → 0.83 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 5 Nov 2026 · Analysed npm/@likerts/mcp@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 7 findings
ID CVE Severity Vector Fix available
GHSA-22jm-h49p-29qw CVE-2026-111767 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L yes
GHSA-46jr-4wx8-v453 CVE-2026-111768 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-6prh-2h8m-c8cw CVE-2026-111769 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N yes
GHSA-6qxp-vccf-f47h CVE-2026-104850 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N yes
GHSA-f897-62hf-6gxq high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-rvq5-wwqv-78pq CVE-2026-111771 medium CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N yes
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 93 packages
Packages resolved 93
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 33 exposed · ~1,572 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
collections_create ~135

Create an immutable embedded collection only when every declared SDK installation supports the bound schema version. Identical retries return the original submission credential; handle it as a secret.

NameTypeReqDescription
expiresAtstring–Optional future expiry, at most 90 days from creation.
idempotencyKeystringyes–
placementstringyes–
responseCapinteger––
sdkCapabilitiesobjectyesCustomer-declared installed SDK groups. Every group must include the published/bound survey schema version. This is a compatibility guard, not attestation.
surveyIdstringyes–
versionintegeryes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

collections_get ~25

Fetch the immutable respondent configuration using a collection credential.

NameTypeReqDescription
idstringyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

collections_security_update ~53

Configure exact browser origins and a per-collection request rate. Origins are browser policy, not authentication.

NameTypeReqDescription
allowedOriginsarrayyes–
idstringyes–
requestsPerMinuteintegeryes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

collections_update ~41

Open or close collection acceptance, or irreversibly revoke its credential.

NameTypeReqDescription
acceptingboolean––
idstringyes–
revoke–––
NameTypeReqDescription
resultobjectyes–

No examples provided.

exports_create ~64

Create or idempotently retry a bounded asynchronous CSV or JSON response export.

NameTypeReqDescription
acceptedFromstring––
acceptedTostring––
collectionIdstring––
formatstringyes–
idempotencyKeystringyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

exports_download ~31

Download a ready export as authenticated base64 content before its 24-hour expiry.

NameTypeReqDescription
idstringyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

exports_get ~26

Read an export job's status and stable schema manifest.

NameTypeReqDescription
idstringyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

exports_revoke ~29

Irreversibly revoke export access and remove its stored object.

NameTypeReqDescription
idstringyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

memberships_list ~18

List current workspace memberships. Owner access is required.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes–

No examples provided.

memberships_put ~35

Grant or replace a workspace membership role. Owner access is required.

NameTypeReqDescription
rolestringyes–
subjectstringyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

memberships_revoke ~28

Revoke a workspace membership immediately. Owner access is required.

NameTypeReqDescription
subjectstringyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

oauth_grants_create ~57

Persist consent as a tenant, subject, client, audience and scope-bound OAuth grant.

NameTypeReqDescription
clientIdstringyes–
expiresAtstringyes–
scopesarrayyes–
subjectstringyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

oauth_grants_revoke ~30

Irreversibly revoke an OAuth grant for subsequent requests.

NameTypeReqDescription
idstringyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

responses_delete ~34

Erase one response's raw answers and metadata while preserving its minimal retry receipt and usage entry.

NameTypeReqDescription
idstringyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

responses_list ~68

Retrieve one stable snapshot page of workspace responses, optionally filtered by collection and acceptance time. Continue with nextCursor.

NameTypeReqDescription
acceptedFromstring––
acceptedTostring––
collectionIdstring––
cursorstring––
limitinteger––
NameTypeReqDescription
resultobjectyes–

No examples provided.

responses_submit ~162

Submit a completed response. Accepted responses are counted for observability and are never metered or charged. Reuse the same idempotency key only for identical retries.

NameTypeReqDescription
answersobjectyesQuestion-ID keyed answers. Legacy and schema-v3 choice answers retain their documented wire types. Ranking is a complete option-ID permutation; matrix is a row-ID map to a column ID or nonempty colum…
idstringyes–
idempotencyKeystringyes–
metadataobject–Untrusted caller metadata; compact serialized JSON must be at most 4096 bytes.
NameTypeReqDescription
resultobjectyesImmutable acknowledgement of one accepted response. Likerts does not meter or charge responses.

No examples provided.

retention_run ~22

Run one bounded raw-response and expired-export retention batch for the workspace.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultobjectyes–

No examples provided.

service_credentials_create ~44

Issue a scoped service credential. Its token is returned exactly once.

NameTypeReqDescription
expiresAtstringyes–
namestringyes–
scopesarrayyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

service_credentials_list ~22

List service credential metadata without secret values. Owner access is required.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes–

No examples provided.

service_credentials_revoke ~26

Irreversibly revoke a service credential.

NameTypeReqDescription
idstringyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

surveys_create ~65

Create a survey draft idempotently; identical retries return the original draft.

NameTypeReqDescription
idempotencyKeystringyesRequired by survey creation; omitted from draft update payloads.
pagesarray––
questionsarrayyes–
titlestringyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

surveys_list ~12

List workspace surveys.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes–

No examples provided.

surveys_publish ~75

Publish an immutable version only when every customer-declared SDK installation supports its schema version.

NameTypeReqDescription
idstringyes–
revisionintegeryes–
sdkCapabilitiesobjectyesCustomer-declared installed SDK groups. Every group must include the published/bound survey schema version. This is a compatibility guard, not attestation.
NameTypeReqDescription
resultobjectyes–

No examples provided.

surveys_update ~51

Update a draft using its current revision.

NameTypeReqDescription
idstringyes–
pagesarray––
questionsarrayyes–
revisionintegeryes–
titlestringyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

usage_get ~13

Retrieve accepted-response usage.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultobjectyesResponse counts for observability. These values never gate acceptance or create a charge.

No examples provided.

webhook_deliveries_get ~40

Read attempts, retry time and fixed failure code. Receiver bodies and survey answers are never exposed through delivery status.

NameTypeReqDescription
idstringyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

webhook_deliveries_list ~63

Inspect delivery status. Continue with after equal to the last returned UUID for a stable ordering of existing rows; this operational list is not a response snapshot.

NameTypeReqDescription
afterstring––
endpointIdstring––
limitinteger––
NameTypeReqDescription
resultarrayyes–

No examples provided.

webhook_deliveries_replay ~61

Requeue a completed or failed delivery before seven-day expiry, up to three times. The event ID remains unchanged; receivers deduplicate business processing by that ID.

NameTypeReqDescription
idstringyes–
idempotencyKeystringyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

webhook_endpoints_create ~73

Creates disabled. Install the returned signing secret on your receiver, then explicitly enable. An identical idempotency retry reconstructs the original generation.

NameTypeReqDescription
eventTypesarray–Immutable event subscriptions. Community Edition supports response.accepted.
idempotencyKeystringyes–
urlstringyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

webhook_endpoints_list ~28

Lists up to 100 workspace endpoints, including revoked entries. Signing secrets are never listed.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes–

No examples provided.

webhook_endpoints_rotate ~57

Install the new generation and retain the old receiver secret for five minutes. New claims use the new generation; identical rotation retries return the original protected result.

NameTypeReqDescription
idstringyes–
idempotencyKeystringyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

webhook_endpoints_update ~59

Enable only after configuring verification. Use enabled:false to pause, or revoke:true to permanently cancel queued deliveries; an in-flight HTTP request cannot be recalled.

NameTypeReqDescription
enabledboolean––
idstringyes–
revoke–––
NameTypeReqDescription
resultobjectyes–

No examples provided.

workspace_delete ~25

Erase and tombstone the current workspace account, revoke capabilities and remove export objects.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultobjectyes–

No examples provided.

Install

How do I install the Likerts MCP server?

Likerts runs locally as an npm package, launched with npx -y @likerts/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @likerts/mcp

# add to Claude Code
claude mcp add crosstabs-likerts -- npx -y @likerts/mcp
Common questions

What is the Likerts MCP server?

Likerts is an MCP server listed in the public MCP registry as io.github.crosstabs/likerts. Manage open-source in-product surveys, collections, responses and exports with scoped access. This page covers its npm package (@likerts/mcp).

Is the Likerts MCP server safe to use?

Likerts scores 76 out of 100 on VerifyMCP. We recorded 7 known advisories against it as of 5 November 2026. It declares no install or post-install scripts. 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 Likerts MCP server expose?

Likerts exposes 33 tools: surveys_create, surveys_list, surveys_update, surveys_publish, collections_create, and 28 more. Their descriptions and schemas cost roughly 1,572 tokens of context every time the server is loaded.

Is the Likerts MCP server still maintained?

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

What licence is the Likerts MCP server under?

Likerts declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.