com.mnemopay/gridstamp

MCPcommunity
v1.2.0com.mnemopayUnknownUpdated 5mo agonpmGitHub

Cryptographic spatial proof-of-presence for AV fleets, logistics, AR. 91% spoof detection.

[]( []( [](./LICENSE) Cryptographic dispute evidence for autonomous fleets. When a robot causes an incident — a delivery goes missing, an AMR damages inventory, an AV is involved in a collision — the question that decides who pays is always the same: where was it, exactly, and can you prove it? GridStamp is the evidence layer. Every operation produces a tamper-evident spatial receipt: HMAC-signed…

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
5mo agoLast update
Package
Authorcom.mnemopay
LicenseUnknown
Version1.2.0
Sourcemcp-registry
npmgridstamp
GitHubmnemopay/gridstamp
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface16 tools · 1 privileged
Security scan✓ Cleanv1.4.0 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

16 tools · 1 privileged
Statically extracted from the published packagev1.4.0 · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

stamp_locationNo description published

This tool published no description. Forge does not invent one.

verify_stampNo description published

This tool published no description. Forge does not invent one.

spatial_memory_storeNo description published

This tool published no description. Forge does not invent one.

spatial_memory_recallNo description published

This tool published no description. Forge does not invent one.

proof_chainNo description published

This tool published no description. Forge does not invent one.

verify_proof_chainNo description published

This tool published no description. Forge does not invent one.

spatial_settleNo description published

This tool published no description. Forge does not invent one.

spoof_checkNo description published

This tool published no description. Forge does not invent one.

list_stampsNo description published

This tool published no description. Forge does not invent one.

list_settlementsNo description published

This tool published no description. Forge does not invent one.

robot_statusNo description published

This tool published no description. Forge does not invent one.

distance_betweenNo description published

This tool published no description. Forge does not invent one.

read_sensorNo description published

This tool published no description. Forge does not invent one.

verify_spatial_proofNo description published

This tool published no description. Forge does not invent one.

check_antispoofingNo description published

This tool published no description. Forge does not invent one.

write_attestationprivilegedNo description published

This tool published no description. Forge does not invent one.

0 of 16 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

[]( []( [](./LICENSE) Cryptographic dispute evidence for autonomous fleets. When a robot causes an incident — a delivery goes missing, an AMR damages inventory, an AV is involved in a collision — the question that decides who pays is always the same: where was it, exactly, and can you prove it? GridStamp is the evidence layer. Every operation produces a tamper-evident spatial receipt: HMAC-signed camera frames, Merkle-rooted memory, cryptographic proof-of-location. The receipts hold up under…

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

16 tools · 1 privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.