Backstory: search your data exports locally
NUGET · BACKSTORY · SCANNED SEP 20
Search your Google, Telegram, Spotify and Instagram exports locally. Fully offline.
Available components
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 Security88
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Install-script risk not yet assessed.Unverified
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- 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 83 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 288 tokens (~57/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
How do I install the Backstory: search your data exports locally MCP server?
Backstory: search your data exports locally runs locally as a NuGet package, launched with dnx Backstory@1.1.0 --yes. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
nuget · Backstory
claude mcp add magna-nz-backstory -- dnx Backstory@1.1.0 --yes
{
"mcpServers": {
"magna-nz-backstory": {
"command": "dnx",
"args": [
"Backstory@1.1.0",
"--yes"
]
}
}
} {
"servers": {
"magna-nz-backstory": {
"command": "dnx",
"args": [
"Backstory@1.1.0",
"--yes"
]
}
}
} codex mcp add magna-nz-backstory -- dnx Backstory@1.1.0 --yes
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"magna-nz-backstory": {
"type": "local",
"command": [
"dnx",
"Backstory@1.1.0",
"--yes"
],
"enabled": true
}
}
} mcp_servers:
magna-nz-backstory:
command: "dnx"
args: ["Backstory@1.1.0", "--yes"] {
"McpServers": {
"magna-nz-backstory": {
"Transport": "stdio",
"Command": "dnx",
"Arguments": [
"Backstory@1.1.0",
"--yes"
]
}
}
} {
"mcpServers": {
"magna-nz-backstory": {
"command": "dnx",
"args": [
"Backstory@1.1.0",
"--yes"
]
}
}
} 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.
- 19 Sept 26 −2
- Stability: pass → 0.80 functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 17 Sept 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.
- 14 Sept 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.
- 12 Sept 26 −2
- Stability: pass → 0.80 functional
- 11 Sept 26 0
- Stability: 0.97 → pass security
- 10 Sept 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.
- 7 Sept 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.
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 20 Sept 2026 · Analysed nuget/Backstory@1.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | nuget |
| Reason | Package not fetched |
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 →
get_events ~36
Fetch full event records by id, including the pointer to the original source record.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | string | yes | Comma-separated event ids. |
No output schema declared.
No examples provided.
list_sources ~23
List the sources ingested into this vault and how many events each contributed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lookup_entity ~35
Look up a person or place by name and return the matching entity.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Name or alias to look up. |
No output schema declared.
No examples provided.
search_timeline ~119
Search the user's life timeline with a natural-language query. Returns ranked events with timestamp, source and text.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string|null | – | Optional ISO-8601 lower bound on event time. |
| limit | integer | – | Max results (default 10). |
| query | string | yes | Natural-language query, e.g. 'dinner plans with Sarah'. |
| source | string|null | – | Optional source filter: 'telegram' or 'google_takeout'. |
| to | string|null | – | Optional ISO-8601 upper bound on event time. |
No output schema declared.
No examples provided.
summarize_period ~75
Return all events in a time range so the agent can summarize what happened.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | ISO-8601 start of range. |
| limit | integer | – | Max events (default 100). |
| source | string|null | – | Optional source filter. |
| to | string | yes | ISO-8601 end of range. |
No output schema declared.
No examples provided.
What is the Backstory: search your data exports locally MCP server?
Backstory: search your data exports locally is an MCP server listed in the public MCP registry as io.github.magna-nz/backstory. Search your Google, Telegram, Spotify and Instagram exports locally. Fully offline. This page covers its NuGet package (Backstory).
Is the Backstory: search your data exports locally MCP server safe to use?
Backstory: search your data exports locally scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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 Backstory: search your data exports locally MCP server expose?
Backstory: search your data exports locally exposes 5 tools: lookup_entity, search_timeline, list_sources, get_events, summarize_period. Their descriptions and schemas cost roughly 288 tokens of context every time the server is loaded.
Is the Backstory: search your data exports locally MCP server still maintained?
Backstory: search your data exports locally is still listed as active in the MCP registry. We last reached this channel on 20 September 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 Backstory: search your data exports locally MCP server under?
Backstory: search your data exports locally declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.