# map [Health: Active]

**Category:** 🛒 E-Commerce  
**Repository:** https://github.com/maraventano/map  
**GitHub Stars:** 0  
**npm Downloads (last month):** 189  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/map

## Description
One MCP for agent commerce: read · pay · publish. Teacher, not butler.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "map": {
    "command": "npx",
    "args": ["-y","@maraventano/map"]
  }
}
```

## Documentation

## What the map MCP server does

The map MCP server combines three related capabilities for agent commerce: reading merchant pages, explaining payment procedures, and publishing product data. It is distributed as `@maraventano/map` and runs as one MCP process with 23 tools.

Merchant Key handles the read path. Given a product URL, `decode-merchant` attempts to produce one CleanRead structure containing the source URL, product description, seller, price, currency, availability, payment information, outcome, and any actionable gaps. The result uses explicit null or unknown values instead of dropping fields when a page does not provide enough information.

Provisions provides instructional payment content. Its lessons cover wallet concepts, x402 challenges, USDC payment signing, receipt verification, delegation and mandate topics, and troubleshooting. The lessons describe actions for an agent to take with its own wallet; they do not perform the payment.

Atlas supports the publishing path. A merchant can decode its own product URLs, write a catalog and discovery manifest, then expose catalog or product data through `get-catalog` and `get-product`.

## How it works

`decode-merchant` uses read-only HTTP requests. It checks JSON-LD product and offer data, OpenGraph product metadata, and an x402 payment challenge. Version 1 reliably detects x402; other payment values exist in the output schema but are not detected by the current implementation. The decoder follows one same-origin redirect and refuses cross-origin redirects and redirect chains.

The returned outcome distinguishes three cases. `autonomous` means a known price, available product, and detected x402 rail are present. `human_checkout` means the product can be read but no verified agent-payment rail was found. `unreadable` means the decoder could not obtain a usable product or price description.

Atlas reuses the same decoder for merchant-owned URLs rather than requiring platform-specific adapters. `publish-catalog` creates `catalog.json` and a `.well-known/map.json` manifest for discovery. The resulting data can then be served through the catalog tools.

## Setup and configuration

Run the server with Node.js 18 or newer:

```bash
npx @maraventano/map
```

The process communicates over stdio. The package has one runtime dependency, `@modelcontextprotocol/sdk`, and the supplied smoke commands exercise the decoder and publishing flow:

```bash
npm run smoke
npm run smoke:publish
```

No environment variables or wallet credentials are specified as required configuration. The server does not hold private keys, store cards, deploy merchant infrastructure, sign transactions, or submit payments.

## Limitations and notes

Pages that depend on JavaScript and do not expose JSON-LD or OpenGraph product data may be unreadable because there is no headless-browser step. Stock information is often unavailable, in which case the result remains `unknown`. The decoder does not probe secondary endpoints.

Detection is deliberately conservative: branding, checkout buttons, scripts, marketing text, and platform names do not establish an agent-payment rail. A normal Shopify or Stripe page therefore remains `human_checkout` unless a verifiable supported signal is present. AP2, ACP, and UCP detectors are described as future work rather than current functionality.

Atlas currently trusts the merchant's own decoder output. Independent rereads, signed manifests, and periodic audits are not implemented. The payment rail still determines the actual settlement price, so a faulty manifest can misstate fields such as stock but cannot change the settlement amount.

The project is dual-licensed: individuals and agents may use it freely, while companies require a commercial license. It is not MIT-licensed.

_Full upstream README: https://allmcps.com/mcp/map/readme_