Gridstamp
Add cryptographic spatial proof-of-presence to agent or fleet workflows so GPS spoofing and fake location claims are caught before you trust logistics or AV telemetry.
Overview
com.mnemopay/gridstamp is a MCP server for the Ship phase that provides cryptographic spatial proof-of-presence with publisher-cited 91% spoof detection for fleet, logistics, and AR workflows.
What is this MCP server?
- Cryptographic spatial proof-of-presence for AV fleets, logistics, and AR use cases
- Documented 91% spoof detection in server metadata
- stdio MCP via npx gridstamp-mcp (npm package gridstamp, v1.2.0)
- GRIDSTAMP_API_KEY from getbizsuite.com/developers
- Publisher cites 91% spoof detection in description
- Package version 1.2.0
- stdio transport via npx gridstamp / gridstamp-mcp
What problem does it solve?
Agent and fleet apps that trust raw GPS are trivially fooled by spoofing, which blows up payouts, audits, and safety claims once you scale.
Who is it for?
Solo builders shipping location-attested logistics, AV-adjacent, or AR products who need an API-backed spoof check in the agent loop.
Skip if: Apps with no geolocation trust requirement, or teams unwilling to run an API key and evaluate detection limits on real data.
What do I get? / Deliverables
Your agent can call GridStamp verification through MCP so location-sensitive decisions use cryptographic proof-of-presence instead of naive coordinates.
- MCP-invokable spatial proof-of-presence checks against GridStamp API
- Local stdio MCP server process (gridstamp-mcp)
- Integration hook for AV, logistics, or AR location verification flows
Recommended MCP Servers
Journey fit
Location trust and spoof resistance belong on the Ship security shelf when you harden integrations that depend on where a device or agent claims to be. Security subphase covers verification and abuse resistance; GridStamp’s stated 91% spoof detection is a pre-production gate, not a marketing copy task.
How it compares
MCP geospatial attestation API, not a maps widget skill or generic reverse-geocoding integration.
Common Questions / FAQ
Who is com.mnemopay/gridstamp for?
Developers building AV, logistics, or AR systems who need agents to invoke GridStamp proof-of-presence checks via MCP and npm.
When should I use com.mnemopay/gridstamp?
Use it in Ship security when location spoofing would break fraud controls, compliance, or operational trust before launch.
How do I add com.mnemopay/gridstamp to my agent?
Set GRIDSTAMP_API_KEY, add an stdio MCP entry running npx with package gridstamp and command gridstamp-mcp per server.json, then restart your client.