com.mnemopay/gridstamp
NPM · GRIDSTAMP
Tamper-evident spatial receipts: cryptographic proof-of-presence for AV fleets, logistics and AR.
Available components
Last scanned (18 hours ago)
Scores higher than 63% of npm servers
Category Maps and Location
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
- 80 of 247 dependencies flagged as unhealthy (2 deprecated). View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- 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 2 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 745 tokens (~62/item across 12 items; 12 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 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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
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.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
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.
- 21 Nov 26 0
- Stability: 0.97 → pass security
- 20 Nov 26 0
- Stability: pass → 0.97 functional
- 14 Nov 26 0
- Stability: 0.97 → pass security
- 13 Nov 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.
- 11 Nov 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.
- 9 Nov 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.
- 7 Nov 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.
- 4 Nov 26 −4
- Stability: pass → 0.67 functional
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 21 Nov 2026 · Analysed npm/gridstamp@1.4.2
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 247 packages
| Packages resolved | 247 |
|---|---|
| Deprecated | 2 |
| Stale | 79 |
| 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 →
distance_between ~75
Calculate distance in km between two GPS coordinates using the Haversine formula.
| Name | Type | Req | Description |
|---|---|---|---|
| lat1 | number | yes | Latitude of point 1 |
| lat2 | number | yes | Latitude of point 2 |
| lng1 | number | yes | Longitude of point 1 |
| lng2 | number | yes | Longitude of point 2 |
No output schema declared.
No examples provided.
list_settlements ~32
List all spatial settlements for this robot.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results (default: 20) |
No output schema declared.
No examples provided.
list_stamps ~35
List all spatial stamps for this robot, most recent first.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results (default: 20) |
No output schema declared.
No examples provided.
proof_chain ~106
Build an IETF COSE Merkle inclusion proof (draft-ietf-cose-merkle-tree-proofs-18) over an ordered sequence of spatial stamps. Each stamp's leaf hash is combined into a tree head (tree_size + root_hash + timestamp); the returned chain carries the audit path segments needed to re-derive the root. Use for delivery audit trails and regulator-facing evidence.
| Name | Type | Req | Description |
|---|---|---|---|
| stampIds | array | yes | Ordered list of stamp IDs whose leaf hashes form the tree leaves. |
No output schema declared.
No examples provided.
robot_status ~25
Get robot status: ID, total stamps, memories, settlements, last known location.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
spatial_memory_recall ~83
Recall spatial memories near a location or matching tags.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | – | Latitude to search near |
| limit | number | – | Max results (default: 10) |
| lng | number | – | Longitude to search near |
| radiusKm | number | – | Search radius in km (default: 1) |
| tags | array | – | Filter by tags |
No output schema declared.
No examples provided.
spatial_memory_store ~65
Store spatial context to persistent memory. Tags a location with metadata for later recall.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | What to remember about this location |
| lat | number | yes | Latitude |
| lng | number | yes | Longitude |
| tags | array | – | Tags for categorization |
No output schema declared.
No examples provided.
spatial_settle ~85
Create a spatial settlement — payment that requires proof-of-presence at a location. Used for delivery confirmation, service completion, and location-based contracts.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Amount in USD |
| payeeId | string | yes | Payee identifier |
| reason | string | yes | Reason for settlement |
| stampId | string | yes | Stamp ID proving presence at settlement location |
No output schema declared.
No examples provided.
spoof_check ~47
Run anti-spoofing analysis on a stamp. Checks for GPS spoofing signals: impossible speed, duplicate timestamps, coordinate anomalies.
| Name | Type | Req | Description |
|---|---|---|---|
| stampId | string | yes | Stamp ID to check |
No output schema declared.
No examples provided.
stamp_location ~75
Create a tamper-evident spatial stamp at a GPS coordinate. Returns a cryptographically signed proof-of-presence receipt.
| Name | Type | Req | Description |
|---|---|---|---|
| alt | number | – | Altitude in meters (optional) |
| label | string | – | Human-readable location label (optional) |
| lat | number | yes | Latitude |
| lng | number | yes | Longitude |
No output schema declared.
No examples provided.
verify_proof_chain ~79
Verify an IETF COSE Merkle inclusion proof produced by proof_chain. Recomputes each leaf hash, walks the audit path up to the expected root_hash, and checks the tree head signature. Reports per-leaf validity plus the overall tree-head status.
| Name | Type | Req | Description |
|---|---|---|---|
| chainId | string | yes | Tree-head / chain ID returned by proof_chain. |
No output schema declared.
No examples provided.
verify_stamp ~38
Verify a spatial stamp's integrity. Checks HMAC signature and timestamp to detect tampering.
| Name | Type | Req | Description |
|---|---|---|---|
| stampId | string | yes | Stamp ID to verify |
No output schema declared.
No examples provided.
How do I install the com.mnemopay/gridstamp MCP server?
com.mnemopay/gridstamp runs locally as an npm package, launched with npx -y gridstamp. The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · gridstamp
claude mcp add com-mnemopay-gridstamp -- npx -y gridstamp
The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it.
What is the com.mnemopay/gridstamp MCP server?
com.mnemopay/gridstamp is an MCP server listed in the public MCP registry as com.mnemopay/gridstamp. Tamper-evident spatial receipts: cryptographic proof-of-presence for AV fleets, logistics and AR. This page covers its npm package (gridstamp).
Is the com.mnemopay/gridstamp MCP server safe to use?
com.mnemopay/gridstamp scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 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 com.mnemopay/gridstamp MCP server expose?
com.mnemopay/gridstamp exposes 12 tools: stamp_location, verify_stamp, spatial_memory_store, spatial_memory_recall, proof_chain, and 7 more. Their descriptions and schemas cost roughly 745 tokens of context every time the server is loaded.
Is the com.mnemopay/gridstamp MCP server still maintained?
com.mnemopay/gridstamp is still listed as active in the MCP registry. We last reached this channel on 21 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 com.mnemopay/gridstamp MCP server under?
com.mnemopay/gridstamp 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 com.mnemopay/gridstamp MCP server?
VerifyMCP ran 15 checks on com.mnemopay/gridstamp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about com.mnemopay/gridstamp: Security disclosure. 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.