com.mnemopay/gridstamp
NPM · GRIDSTAMP · SCANNED SEP 22
Cryptographic spatial proof-of-presence for AV fleets, logistics, AR. 91% spoof detection.
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects sharp 0.33.5, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 79 of 266 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 100 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 645 tokens (~53/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 Management93
- Stability observed for 28 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 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
How do I install the com.mnemopay/gridstamp MCP server?
com.mnemopay/gridstamp runs locally as an npm package, launched with npx -y gridstamp. 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
{
"mcpServers": {
"com-mnemopay-gridstamp": {
"command": "npx",
"args": [
"-y",
"gridstamp"
]
}
}
} {
"servers": {
"com-mnemopay-gridstamp": {
"command": "npx",
"args": [
"-y",
"gridstamp"
]
}
}
} codex mcp add com-mnemopay-gridstamp -- npx -y gridstamp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mnemopay-gridstamp": {
"type": "local",
"command": [
"npx",
"-y",
"gridstamp"
],
"enabled": true
}
}
} openclaw mcp add com-mnemopay-gridstamp --command npx --arg -y --arg gridstamp
mcp_servers:
com-mnemopay-gridstamp:
command: "npx"
args: ["-y", "gridstamp"] {
"McpServers": {
"com-mnemopay-gridstamp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"gridstamp"
]
}
}
} assistant mcp add com-mnemopay-gridstamp -t stdio -c npx -a -y gridstamp
{
"mcpServers": {
"com-mnemopay-gridstamp": {
"command": "npx",
"args": [
"-y",
"gridstamp"
]
}
}
} 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.
- 20 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.
- 18 Sept 26 −2
- Stability: pass → 0.80 functional
- 17 Sept 26 0
- CVE-2026-39244 no longer affects this package ▲ security
- Stability: 0.97 → pass security
- 16 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.
- 15 Sept 26 0
- CVE-2026-82562 no longer affects this package ▲ security
- CVE-2026-82417 no longer affects this package ▲ security
- 13 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.
- 11 Sept 26 −2
- Stability: pass → 0.80 functional
- 10 Sept 26 0
- Stability: 0.97 → pass security
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 22 Sept 2026 · Analysed npm/gridstamp@1.2.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 →
Vulnerabilities 2 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-f88m-g3jw-g9cj | high | yes | ||
| GHSA-rgj7-g3m4-5g8c | high | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 266 packages
| Packages resolved | 266 |
|---|---|
| Deprecated | 2 |
| Stale | 78 |
| 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 ~44
Generate a proof chain showing the robot's path between locations. Useful for delivery verification and audit trails.
| Name | Type | Req | Description |
|---|---|---|---|
| stampIds | array | yes | Ordered list of stamp IDs in the chain |
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 ~41
Verify an entire proof chain for continuity and integrity. Checks each stamp and validates the sequence.
| Name | Type | Req | Description |
|---|---|---|---|
| chainId | string | yes | Proof chain ID to verify |
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.
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. Cryptographic spatial proof-of-presence for AV fleets, logistics, AR. 91% spoof detection. This page covers its npm package (gridstamp).
Is the com.mnemopay/gridstamp MCP server safe to use?
com.mnemopay/gridstamp scores 73 out of 100 on VerifyMCP. We recorded 2 known advisories against it as of 22 September 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 645 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 22 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 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.