Asset Notation
NPM · ASSET-NOTATION
Read and maintain an Asset Notation file on disk: net worth, holdings, valuations, CSV import.
Available components
Last scanned (17 hours ago)
Scores higher than 26% of npm servers
Category Finance and Payments
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 Security98
- 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
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to assetnotation/js). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
- Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.Unverified
Stability & Change Management0
- Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.Unverified
Tool Coverage0
- Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.Unverified
Tool Safety0
- Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.Unverified
Capabilities0
- Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
Checks we ran (9)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
Checks we could not complete (5)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.
- Capabilities in Capabilities (scores 0 for this)Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 0
- Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
- Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Package version: 0.1.10 → 0.1.11 functional
- 3 Nov 26 0
- Package version: 0.1.9 → 0.1.10 functional
- 2 Nov 26 0
- Stability: Stability not yet verified: our sandbox could not run this package, so we have no schema to compare. security
- Tool safety: Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan. security
- Schema quality: Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess. functional
- Capabilities: Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake. functional
- Tool coverage: Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess. functional
- 1 Nov 26 0
- Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
- Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Package version: 0.1.8 → 0.1.9 functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- Package version: 0.1.7 → 0.1.8 functional
- 29 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 25 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- Security disclosure: unverified → fail ▼ functional
- 24 Oct 26 34
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 5 Nov 2026 · Analysed npm/asset-notation@0.1.11
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | assetnotation/js |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/assetnotation/js/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3692274474 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:1e57537c0b68652c5f2e56ab035ce322b8bad161eb5c756023126a08764f33f33974aa5bc04859a94bd4952ef5b2cec9b0c79db2d750f4ffb9747f167 |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| 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 →
Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.
How do I install the Asset Notation MCP server?
Asset Notation runs locally as an npm package, launched with npx -y asset-notation mcp, plus the required file.json, which you supply. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · asset-notation
claude mcp add assetnotation-asset-notation -- npx -y asset-notation mcp
Incomplete: the registry marks file.json as required and gives no value we can show, so it is not in this command. Add it before you run it.
What is the Asset Notation MCP server?
Asset Notation is an MCP server listed in the public MCP registry as io.github.assetnotation/asset-notation. Read and maintain an Asset Notation file on disk: net worth, holdings, valuations, CSV import. This page covers its npm package (asset-notation).
Is the Asset Notation MCP server safe to use?
Asset Notation scores 49 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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.
Is the Asset Notation MCP server still maintained?
Asset Notation 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 Asset Notation MCP server under?
Asset Notation 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.
What did VerifyMCP test on the Asset Notation MCP server?
VerifyMCP ran 9 checks on Asset Notation, covering Malware scan, Known CVEs, Install scripts, Dependency health and 5 more. 5 items could not be completed, a gap on our side rather than a finding about Asset Notation: Schema quality, Stability, Tool coverage, Tool safety and 1 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.