# io.github.sunsiyuan/human-survey (npm · humansurvey-mcp)

Self-reported attribution: which channel and which creator your users first heard you from.

- Trust score: 62/100 (medium)
- Change this week: +19
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-04

## Components

- npm · `humansurvey-mcp`: 62/100 (this document), [markdown](https://verifymcp.io/servers/sunsiyuan-human-survey/humansurvey-mcp.md), [page](https://verifymcp.io/servers/sunsiyuan-human-survey/humansurvey-mcp)

## Channel facts

- Registry: `npm`
- Package: `humansurvey-mcp`
- Version: `1.2.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-04.

- **Supply Chain Security**: 83/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known medium-severity CVE affects hono 4.12.33, reached via @modelcontextprotocol/sdk > hono. A fixed version is available.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1548 tokens (~154/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability check failed: the tool surface changed between 0.6.0 and 1.2.0: 5 tool removals, 0 breaking changes, 10 additions.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 92% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add sunsiyuan-human-survey -- npx -y humansurvey-mcp
```

### Codex

```bash
codex mcp add sunsiyuan-human-survey -- npx -y humansurvey-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "sunsiyuan-human-survey": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "humansurvey-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add sunsiyuan-human-survey --command npx --arg -y --arg humansurvey-mcp
```

### Hermes

```yaml
mcp_servers:
  sunsiyuan-human-survey:
    command: "npx"
    args: ["-y", "humansurvey-mcp"]
```

### Other

```json
{
  "mcpServers": {
    "sunsiyuan-human-survey": {
      "command": "npx",
      "args": [
        "-y",
        "humansurvey-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-04 (score 62, −1)

- [security regression] CVE-2026-69207 affects this package: medium
- [security regression] Known CVEs: partial → fail

### 2026-08-03 (score 63, +29)

- [security regression] Stability: unverified → fail
- [security regression] Provenance: unverified → fail
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Install scripts: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] License: unverified → pass
- [functional improvement] Schema quality: unverified → excellent
- [functional] Licence: MIT

### 2026-08-02 (score 34, +29)

- [security improvement] Malware scan: unverified → pass
- [functional regression] Schema quality: excellent → unverified
- [functional improvement] Tool coverage: unverified → 100

### 2026-08-01 (score 5, −36)

- [security regression] Provenance: fail → unverified
- [security regression] Stability: fail → unverified
- [security regression] Install scripts: pass → unverified
- [functional regression] Maintenance: pass → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] License: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified
- [functional] Licence: MIT
- [functional] Package version: 1.1.1 → 1.2.0

### 2026-07-31 (score 41, +16)

- [security regression] Provenance: unverified → fail
- [security improvement] Install scripts: unverified → pass
- [security] First check of Stability: fail
- [functional regression] Tool coverage: 100% → 92%
- [functional improvement] Schema quality: 224 → 152
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] License: unverified → pass
- [functional improvement] Schema quality: unverified → excellent
- [functional] First check of MCP protocol: pass
- [functional] Licence: MIT
- [functional] Package version: 0.6.0 → 1.1.1
- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 25, −18)

- [security regression] Malware scan: pass → unverified

### 2026-07-27 (score 43)

First indexed and scored.

## MCP tools (10)

### `login` (~182 tokens)

Sign in

Sign in with an email address and store an API key on this machine. Called with only an email, it mails a six-digit code and returns nothing usable — the code has to come from the person, out of their inbox. Called with the email and that code, it stores a key at ~/.humansurvey/credentials and reports where it was written. The key itself is never printed. Signing in and signing up are the same act: an address that has never been used gets an account.

Input parameters:

- `code` (string): The six digits from the email. Omit on the first call — you cannot know this value; ask the person for it.
- `email` (string, required): The person’s email address. They will read the code out of this inbox.
- `name` (string): A label for the key, e.g. the project it is for.

### `get_catalog` (~85 tokens)

Platform catalog

List the platforms HumanSurvey knows: the slug to use as catalog_slug, the display label, and which class of channel it is. These are the named channels a respondent can be shown — TikTok, ChatGPT, LinkedIn, Reddit and so on — plus the descriptive options that have no brand behind them, like "a friend or colleague told me". No API key needed.

### `list_forms` (~46 tokens)

List forms

List the forms on this account: id, name, respondent URL, whether it is active or paused, whether it has been configured with questions yet, and how many responses it has collected.

### `get_form` (~70 tokens)

Read a form

Read one form: its settings, and the question configuration currently shown to respondents — every question, every candidate, and the order mode. Returns the configuration as JSON, because that is the exact shape a configuration write takes.

Input parameters:

- `form_id` (string, required): The form id, as reported by the forms listing.

### `create_form` (~156 tokens)

Create a form

Create a form and return its id, its respondent URL, and the iframe and postMessage listener to embed that URL in a host page. The form has no questions yet and shows nothing to respondents until it is configured. allowed_origins restricts which sites may embed it; leaving it empty allows any site, which means any site can spend this account’s response quota.

Input parameters:

- `allowed_origins` (array): Origins permitted to embed the form, e.g. ["https://app.example.com"]. Scheme and host only — a path is rejected rather than trimmed.
- `name` (string, required): An internal label. Respondents never see it.
- `theme` (object): Exactly these four tokens. Any other key is rejected rather than ignored.

### `configure_form` (~233 tokens)

Configure the questions

Set the questions and candidates a form shows. Replaces the whole configuration and stores it as a new immutable version, so responses already collected keep describing the list they were actually shown. Re-sending an identical configuration reuses the existing version rather than making another.

A form is one single-select question, optionally expanding into a second. Give a candidate an `expands` naming another question to reveal it when that candidate is picked — that is how "TikTok" becomes "which account".

Candidate ids must be stable keys that survive a rename. Using a handle as an id splits that creator’s history in two the day they change it.

Set catalog_slug to take a candidate’s label and logo from the platform catalog. Order defaults to "rotate", which randomizes per respondent and is what makes the reported shares unbiased; "fixed" keeps your order and accepts that earlier options get picked more often for being earlier.

Input parameters:

- `form_id` (string, required): The form to configure.
- `nodes` (array, required): One to twelve questions. Exactly one must not be reachable by any `expands` — that one is asked first.

### `get_attribution` (~236 tokens)

Attribution rollup

What respondents said, aggregated. Reports, per question, how many completed responses named each candidate out of how many answered that question, the unresolved answers in the same list, how often a follow-up question failed to find an answer, and revenue where conversion events have been recorded.

Computed fresh on every call, including any mappings made since — so a rollup of a past window can legitimately change between two reads.

Input parameters:

- `by` (string): "candidate" (default) is one row per option; "node" collapses to one row per question.
- `form_id` (string, required): The form to report on. Required: combining forms would mix two respondent populations into one denominator.
- `from` (string): Start of the window, inclusive. ISO 8601; a value with no timezone is read as UTC.
- `metric` (string): Sort order only; counts and revenue are both reported either way. Revenue appears on the rows of the first question and nowhere else, because a respondent’s money belongs to the respondent rather tha…
- `to` (string): End of the window, exclusive.

### `list_unresolved` (~154 tokens)

Free-text answers

The answers respondents typed instead of picking from the list, grouped by the exact text and ordered by how often it was typed. Reports the spelling variants seen, when each was first and last typed, and whether a mapping already covers it.

These are verbatim words. Two texts that read alike may be different people, and a text may name somebody who is not on the candidate list at all.

Input parameters:

- `form_id` (string, required): The form to read.
- `from` (string): Start of the window, inclusive.
- `include_mapped` (boolean): Include texts that a live mapping already resolves. Off by default.
- `limit` (integer)
- `to` (string): End of the window, exclusive.

### `remap` (~206 tokens)

Map a typed answer to a candidate

Record that a specific typed answer means a specific candidate. It applies to every response already carrying that text as well as every future one, so numbers reported for past windows change.

The original text is never altered and a mapping can be revoked, but a report may already have been read. Only map a text whose meaning is established — a text that merely resembles a candidate’s name is not evidence that it is that candidate.

One live mapping per text per question.

Input parameters:

- `candidate_id` (string, required): The candidate it means. Not validated against the current configuration, because a candidate may have been removed while its history still needs the mapping.
- `form_id` (string, required)
- `node_id` (string, required): The question the text was typed into. The same words can mean different things in different questions.
- `note` (string): Why. Kept with the mapping.
- `raw` (string, required): The typed text, exactly as reported. It is normalized the same way on both sides.

### `revoke_remap` (~180 tokens)

Undo a mapping

Stop a mapping from applying. The typed answers it covered return to the unresolved list — in past windows as well as future ones, because rollups join mappings when they are read rather than when they are made. Numbers already reported for those windows will therefore change.

Nothing is deleted: the mapping is marked revoked and kept, so a report produced while it was live can still be explained. Revoking an already-revoked mapping is not an error and does not move the time it stopped applying.

Mapping ids appear beside any text that is already mapped in the free-text listing, and in the confirmation given when a mapping is created.

Input parameters:

- `form_id` (string, required): The form the mapping belongs to.
- `remap_id` (string, required): The mapping to revoke. A mapping id alone is never enough — it is checked against this form and this account.

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/sunsiyuan-human-survey/humansurvey-mcp#diagnostics

## Score history

- 2026-08-04: 62
- 2026-08-03: 63
- 2026-08-02: 34
- 2026-08-01: 5
- 2026-07-31: 41
- 2026-07-30: 25
- 2026-07-28: 43
- 2026-07-27: 43

## Links

- npm package: https://www.npmjs.com/package/humansurvey-mcp
- Socket report: https://socket.dev/npm/package/humansurvey-mcp
- Repository: https://github.com/sunsiyuan/human-survey
- Changelog RSS feed: https://verifymcp.io/servers/sunsiyuan-human-survey/humansurvey-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/sunsiyuan-human-survey/humansurvey-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/sunsiyuan-human-survey/humansurvey-mcp