AgentShopping Intent Catalog

org.agentshoppingPublished by agentshopping.orgOfficial publisherv0.1.1Updated Nov 8, 2026

Read-only MCP endpoint for 100 buyer-agent transaction intents and supply offers.

VerifiedStreamable HTTPWeb executableData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Read-only MCP endpoint exposing a catalog of 100 buyer-agent transaction intents and supply offers, with deterministic workload matching.

What you can do
  • List and read buyer transaction intents, including required context, decision factors and supply status
  • Browse the supply catalog with dated verified facts and explicitly listed unverified fields
  • Match a workload to offers, returning explainable matches or rejections with reasons
  • Report honest limitations, such as intents without a verified supply partner
When to use it
Useful when an assistant needs to look up buyer-intent or supply-side information from this catalog, or to check whether a given workload has a matching offer. It is a small protocol skeleton rather than a marketplace, so it fits exploratory or reference use.
Requirements
Remote Streamable HTTP endpoint, no install or credentials. The optional local stdio server needs Node.js 18 or later and runs from a source checkout, since the npm package is not published. The local server reads the AGENTSHOPPING_API_BASE environment variable to point at another catalog.
Before you install
Read-only: it holds no funds, places no orders and writes nothing. It asserts no prices, vendors or availability, and 99 of 100 intents have no verified supply partner, so results are sparse. Intent ordering is editorial, not measured demand. Outbound provider links require a human click.

Installation

In SourceWeft

  1. Open AgentShopping Intent Catalog in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/org.agentshopping%2Fintent-catalog/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "agentshopping-intent-catalog": {
      "type": "http",
      "url": "https://agentshopping.org/mcp"
    }
  }
}

README

agentshopping-mcp

An MCP server that exposes the AgentShopping buyer-intent catalog to any MCP-compatible agent.

It is read-only. It holds no funds, places no orders, and writes nothing. It returns dated, sourced facts — and states plainly what it does not know.

Two ways to use it

1. Remote endpoint (recommended, zero install)

https://agentshopping.org/mcp

MCP Streamable HTTP. Point any MCP client at the URL:

json
{  "mcpServers": {    "agentshopping": {      "url": "https://agentshopping.org/mcp"    }  }}

This endpoint is listed in the official MCP Registry:

FieldValue
Nameorg.agentshopping/intent-catalog
Version0.1.1
Namespacedomain reverse-DNS of agentshopping.org (HTTP authentication)
Statusactive
Published2026-11-08T13:47:55Z
Sourcehttps://github.com/wken2238-byte/agentshopping-mcp

Verify it yourself:

bash
curl 'https://registry.modelcontextprotocol.io/v0.1/servers?search=agentshopping'

2. Local stdio server (runs on your machine)

bash
node src/index.js
json
{  "mcpServers": {    "agentshopping": {      "command": "node",      "args": ["/absolute/path/to/agentshopping-mcp/src/index.js"]    }  }}

Not on npm yet. The agentshopping-mcp package name is reserved but the package has not been published to the registry, so npm install -g agentshopping-mcp does not work yet. Until it does, run it from a checkout as shown above.

Pointing it at a different catalog

The stdio server reads AGENTSHOPPING_API_BASE if set, and falls back to https://agentshopping.org. Use it to run against a self-hosted or mirrored catalog:

json
{  "mcpServers": {    "agentshopping": {      "command": "node",      "args": ["/path/to/agentshopping-mcp/src/index.js"],      "env": { "AGENTSHOPPING_API_BASE": "https://your-mirror.example" }    }  }}

The tools

ToolReturns
list_intents100 buyer transaction intents with supply status
get_intentOne intent's required context, decision factors, honest supply status
list_offersSupply catalog with dated verified facts and explicit unverified fields
match_workloadDeterministic, explainable match or rejection for a workload

match_workload returns matches and rejections with reasons. It does not rank, score, or declare a "best" option — a rejection is a first-class answer, not a failure.

Honest limitations

  • 99 of 100 intents have no verified supply partner. Every response says so explicitly.
  • No prices, specifications, vendors, or availability are asserted. Unknown fields are listed under unverified_fields rather than guessed.
  • Intent ordering is editorial, not measured demand.
  • One supply partner exists today. This is a protocol skeleton, not a marketplace.
  • Outbound provider links require an informed human click. No auto-redirect, no iframe.
  • The registry listing does not mean anyone is using it. It means it can be found.

Running the remote endpoint yourself

The deployed endpoint is src/http-server.py — Python 3 standard library only, no dependencies:

bash
MCP_PORT=8787 MCP_DATA_ROOT=/path/to/site python3 src/http-server.py

Design constraints it holds to:

  • Binds to 127.0.0.1 only. Publish it behind a TLS reverse proxy.
  • Reads static JSON from disk. No outbound network calls, no polling, no background work.
  • Request body capped at 64 KB; path allowlist with traversal protection.
  • Threaded with a concurrency cap and a per-connection timeout, so one slow client cannot block the others.
  • Runs under systemd with MemoryMax=64M and CPUQuota=10%.

src/http-server.cjs is the same server in Node, kept for reference. The deployed instance is the Python one.

Protocol details

  • Remote: MCP Streamable HTTP over POST /mcp. GET returns 405 — no SSE stream is held open.
  • Local: newline-delimited JSON-RPC over stdin/stdout (MCP stdio transport). Logs go to stderr only. Requires Node.js >= 18.
  • Supported methods: initialize, ping, tools/list, tools/call, resources/list (empty), prompts/list (empty). Notifications are ignored without a response.

Manual test

bash
printf '%s\n' \  '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18"}}' \  '{"jsonrpc":"2.0","id":2,"method":"tools/list"}' \  '{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"get_intent","arguments":{"id":"book-flight"}}}' \  | node src/index.js

Publishing a change to the registry

bash
npm i -g mcp-publishercd agentshopping-mcp./publish.sh 0.1.1     # bumps the version in server.json, then publishes

publish.sh authenticates with HTTP authentication — it signs a challenge with a local ECDSA P-384 key and the registry fetches the public key from https://agentshopping.org/.well-known/mcp-registry-auth. Nothing human needs to click anything.

Note the registry's own JWT lives for only 5 minutes, so the login and publish steps are chained with no gap between them. The script handles that, plus a retry for the occasional network stall.

The full walkthrough, including how the proof file and key pair are produced, is in 发布指引.md (Chinese).

License

MIT — see LICENSE.

Source: README.md at commit 34c8964

Tools

4

list_intents

List 100 buyer-agent transaction intents with supply status. 99 of 100 have no verified supply partner. Ranking is editorial, not measured demand.

Takes no parameters.

get_intent

Get one intent: required context, decision factors, honest supply status and policy. Never asserts prices or vendors.

Parametersidrequired

list_offers

Supply catalog with dated verified facts and an explicit list of unverified fields. Currently one partner.

Takes no parameters.

match_workload

Deterministic, explainable match or rejection for a workload. No scores, no invented numbers.

Parametersworkloadrequired

Version history

1
  1. v0.1.1LatestNov 8, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts