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.

shyn

MCPB · SHYN.MCPB

Local-first ambient memory for your Mac — pages, meetings, notes, encrypted on-device.

Available components

0 this week 50 Trust /100

Last scanned (2 hours ago)

Scores higher than 81% of MCPB servers

Category Memory and Knowledge

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 Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
Provenance & Transparency32
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 688 tokens (~114/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 Coverage79
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 38% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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

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.

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.

  • 2 Nov 26 0
    • Stability: 0.97 → pass security
  • 1 Nov 26 0
    • Stability: pass → 0.97 functional
  • 26 Oct 26 0
    • Stability: 0.97 → pass security
  • 25 Oct 26 +1

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

  • 23 Oct 26 +1

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

  • 21 Oct 26 +1

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

  • 19 Oct 26 +1

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

  • 17 Oct 26 +1

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

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 mcpb/https://github.com/shyn-labs/homebrew-tap/releases/download/v0.6.3-alpha/shyn.mcpb

Provenance No attestation

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

Result No attestation
Ecosystem mcpb
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 6 exposed · ~688 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
forget ~110

Permanently delete documents from memory (purged from disk, not soft-deleted). Requires confirm: true — always ask the user before confirming. time_from/time_to accept ISO 8601 date or datetime, offsets allowed.

NameTypeReqDescription
confirmbooleanyes–
doc_idinteger––
sourcestring––
time_fromstring–ISO 8601 date or datetime, offsets allowed
time_tostring–ISO 8601 date or datetime, offsets allowed

No output schema declared.

No examples provided.

get_document ~134

Read a whole document from memory by uri or doc_id — search_memory returns only matching excerpts, so use this when you need the complete text (a full meeting transcript, a whole note). Both uri and doc_id come from search_memory and recent_activity results. Long documents are truncated with an offset footer; call again with that offset to page through the rest.

NameTypeReqDescription
doc_idinteger––
max_charsinteger––
offsetinteger–character offset into the document
sourcestring–disambiguates a uri that exists under more than one source
uristring––

No output schema declared.

No examples provided.

memory_status ~44

Daemon health: document/vector counts, pending embeddings, model download progress. modelLoaded=false with modelDownloaded=true just means the model is idle-unloaded; it loads on demand.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

recent_activity ~227

Enumerate documents in a time window, in timestamp order. Call this FIRST for vague or broad questions ('what was I working on') to orient, then drill in with search_memory. Unlike search_memory this is NOT ranked by relevance — it returns everything in the window, so it is the right tool for reconstructing a specific period ('what did I do between 13:00 and 16:00 yesterday'). Use time_from/time_to for an explicit past window (ISO 8601, offsets allowed) and order:'asc' to replay a day forwards; `hours` is a lookback-from-now shorthand. Page with limit/offset — the reply says so when more rows remain.

NameTypeReqDescription
hoursinteger––
limitinteger––
offsetinteger––
orderstring–asc replays a window forwards; default desc
sourcesarray––
time_fromstring–ISO 8601 date or datetime, offsets allowed
time_tostring–ISO 8601 date or datetime, offsets allowed

No output schema declared.

No examples provided.

remember ~36

Save an explicit fact or note to the user's local memory for future recall.

NameTypeReqDescription
contentstringyes–
tagsarray––

No output schema declared.

No examples provided.

search_memory ~137

Search the user's local memory (files, notes, saved facts) with hybrid keyword+semantic retrieval. The workhorse tool. For vague questions, call recent_activity first to orient, then search with a sharpened query. Resolve relative dates ('last Tuesday') into ISO timestamps yourself via time_from/time_to (ISO 8601 date or datetime, offsets allowed).

NameTypeReqDescription
limitinteger––
querystringyes–
sourcesarray––
time_fromstring–ISO 8601 date or datetime, offsets allowed
time_tostring–ISO 8601 date or datetime, offsets allowed

No output schema declared.

No examples provided.

Install

How do I install the shyn MCP server?

shyn ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 6b8ae67921ed1e5f5a159381d66bf43abd6bbbd692a9764b2b052cf9c926fbfb; the commands to do that are on this page. If it does not match, do not open it.

mcpb · shyn.mcpb

Download bundle

Check the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.

SHA-256

6b8ae67921ed1e5f5a159381d66bf43abd6bbbd692a9764b2b052cf9c926fbfb

macOS / Linux

echo "6b8ae67921ed1e5f5a159381d66bf43abd6bbbd692a9764b2b052cf9c926fbfb  shyn.mcpb" | shasum -a 256 -c

Windows (PowerShell)

(Get-FileHash -Algorithm SHA256 .\shyn.mcpb).Hash -eq "6b8ae67921ed1e5f5a159381d66bf43abd6bbbd692a9764b2b052cf9c926fbfb"

Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.

Common questions

What is the shyn MCP server?

shyn is an MCP server listed in the public MCP registry as day.shyn/shyn. Local-first ambient memory for your Mac, pages, meetings, notes, encrypted on-device. This page covers its MCPB bundle (https://github.com/shyn-labs/homebrew-tap/releases/download/v0.6.3-alpha/shyn.mcpb).

Is the shyn MCP server safe to use?

shyn scores 50 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 shyn MCP server expose?

shyn exposes 6 tools: search_memory, recent_activity, get_document, remember, forget, memory_status. Their descriptions and schemas cost roughly 688 tokens of context every time the server is loaded.