SSTIM MCP: Senses, Stimuli and Perception
NPM · @SSTIM/MCP
SSTIM reference for senses, stimuli, perception and scientific contributions.
Available components
Last scanned (21 hours ago)
Scores higher than 39% of npm servers
Category Health and Science
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
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 (Apache-2.0).Pass
- Actively maintained (last published 4 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 817 tokens (~102/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 79% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 14 Oct 26 +29
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 79 functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- 12 Oct 26 0
- Package version: 0.2.0 → 0.3.0 functional
- 11 Oct 26 40
First indexed and scored.
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 16 Oct 2026 · Analysed npm/@sstim/mcp@0.3.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 →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
sstim_draft_contribution ~179
Draft a source-conscious proposal about stimuli, sensory perception, music/sound-based interventions, technology or the SSTIM reference. Never submits or validates claims.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | What is wrong, needed, or proposed (max 4000 characters) |
| evidence | string | – | Source URLs, citations, counterexamples or supporting details (not automatically verified) |
| kind | string | yes | Kind of proposed improvement or research need |
| release | string | – | Optional frozen SSTIM ontology release x.y.z |
| reproduction | string | – | Reproduction steps, observed behavior or specific use case |
| stance | string | yes | Epistemic status of the proposed assertion |
| targetIri | string | – | Optional affected public HTTPS term/resource IRI |
| title | string | yes | Concise proposal title (max 140 characters) |
No output schema declared.
No examples provided.
sstim_get_concept ~84
Return a complete, exact released SSTIM term record with multilingual definitions, related IRIs, mappings and source provenance. Identifier must be IRI or CURIE from SSTIM catalog.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | Exact term IRI or CURIE, e.g. sstim:Stimulation |
| release | string | – | Optional frozen release; defaults to latest |
No output schema declared.
No examples provided.
sstim_get_contribution ~39
Read one public SSTIM MCP contribution issue, including its unverified text and current GitHub issue state.
| Name | Type | Req | Description |
|---|---|---|---|
| number | integer | yes | – |
No output schema declared.
No examples provided.
sstim_list_contributions ~46
Read recent public SSTIM MCP contribution issues; open/closed status does not mean accepted/rejected science.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| state | string | – | – |
No output schema declared.
No examples provided.
sstim_list_releases ~27
List supported frozen SSTIM ontology releases and the latest published release. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sstim_prepare_feedback ~79
Create an SSTIM Contribution Bridge link for a user to review and voluntarily submit feedback. Does NOT submit, save or change anything. Never insert private chat text.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | – | Optional exact term IRI or CURIE; leave empty for a missing-concept idea |
| release | string | – | Optional frozen release for term identity |
No output schema declared.
No examples provided.
sstim_search_concepts ~106
Search the versioned SSTIM reference catalog by CURIE, IRI, label, alternate label, or definition. Returns exact canonical IRIs with source release; not scientific evidence.
| Name | Type | Req | Description |
|---|---|---|---|
| includeDeprecated | boolean | – | – |
| kind | string | – | – |
| limit | integer | – | – |
| query | string | yes | Search phrase, at least 2 characters |
| release | string | – | Frozen release, for example 0.19.0; defaults to latest |
No output schema declared.
No examples provided.
sstim_submit_contribution ~209
WRITE: create a PUBLIC GitHub issue containing the exact reviewed proposal. Requires explicit operator authorization for this submission and SSTIM_GITHUB_TOKEN. Does NOT modify canonical SSTIM knowledge.
| Name | Type | Req | Description |
|---|---|---|---|
| approvedForPublicSubmission | boolean | yes | Must be true only after operator reviews and authorizes publishing this exact proposal publicly |
| description | string | yes | What is wrong, needed, or proposed (max 4000 characters) |
| evidence | string | – | Source URLs, citations, counterexamples or supporting details (not automatically verified) |
| kind | string | yes | Kind of proposed improvement or research need |
| release | string | – | Optional frozen SSTIM ontology release x.y.z |
| reproduction | string | – | Reproduction steps, observed behavior or specific use case |
| stance | string | yes | Epistemic status of the proposed assertion |
| targetIri | string | – | Optional affected public HTTPS term/resource IRI |
| title | string | yes | Concise proposal title (max 140 characters) |
No output schema declared.
No examples provided.
How do I install the SSTIM MCP: Senses, Stimuli and Perception server?
SSTIM MCP: Senses, Stimuli and Perception runs locally as an npm package, launched with npx -y @sstim/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 · @sstim/mcp
claude mcp add w3c-cg-sstim -- npx -y @sstim/mcp
What is the SSTIM MCP: Senses, Stimuli and Perception server?
SSTIM MCP: Senses, Stimuli and Perception is listed in the public MCP registry as io.github.w3c-cg/sstim. SSTIM reference for senses, stimuli, perception and scientific contributions. This page covers its npm package (@sstim/mcp).
Is the SSTIM MCP: Senses, Stimuli and Perception server safe to use?
SSTIM MCP: Senses, Stimuli and Perception scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 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 SSTIM MCP: Senses, Stimuli and Perception server expose?
SSTIM MCP: Senses, Stimuli and Perception exposes 8 tools: sstim_list_releases, sstim_search_concepts, sstim_get_concept, sstim_prepare_feedback, sstim_draft_contribution, and 3 more. Their descriptions and schemas cost roughly 769 tokens of context every time the server is loaded.
Is the SSTIM MCP: Senses, Stimuli and Perception server still maintained?
SSTIM MCP: Senses, Stimuli and Perception is still listed as active in the MCP registry. We last reached this channel on 16 October 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 SSTIM MCP: Senses, Stimuli and Perception server under?
SSTIM MCP: Senses, Stimuli and Perception declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.