Server data from the Official MCP Registry
MCP endpoint for 100 buyer intents, intent search and dispatchable quote requests.
About
MCP endpoint for 100 buyer intents, intent search and dispatchable quote requests.
Remote endpoints: streamable-http: https://agentshopping.org/mcp
Security Report
Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.
6 tools verified · Open access · No issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Permissions Found in Source Code
Found by scanning the linked source code. This listing connects to a hosted endpoint, so none of this runs on your machine: it describes what the server software does where it is hosted.
How to Connect
Remote Plugin
No local installation needed. Your AI client connects to the remote endpoint directly.
Add this to your MCP configuration to connect:
{
"mcpServers": {
"org-agentshopping-intent-catalog": {
"url": "https://agentshopping.org/mcp"
}
}
}Documentation
View on GitHubFrom the project's GitHub 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:
{
"mcpServers": {
"agentshopping": {
"url": "https://agentshopping.org/mcp"
}
}
}
This endpoint is listed in the official MCP Registry:
| Field | Value |
|---|---|
| Name | org.agentshopping/intent-catalog |
| Version | 0.2.0 |
| Namespace | domain reverse-DNS of agentshopping.org (HTTP authentication) |
| Status | active |
| Published | 2026-11-08T13:47:55Z |
| Source | https://github.com/wken2238-byte/agentshopping-mcp |
Verify it yourself:
curl 'https://registry.modelcontextprotocol.io/v0.1/servers?search=agentshopping'
2. Local stdio server (runs on your machine)
node src/index.js
{
"mcpServers": {
"agentshopping": {
"command": "node",
"args": ["/absolute/path/to/agentshopping-mcp/src/index.js"]
}
}
}
Not on npm yet. The
agentshopping-mcppackage name is reserved but the package has not been published to the registry, sonpm install -g agentshopping-mcpdoes 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:
{
"mcpServers": {
"agentshopping": {
"command": "node",
"args": ["/path/to/agentshopping-mcp/src/index.js"],
"env": { "AGENTSHOPPING_API_BASE": "https://your-mirror.example" }
}
}
}
The tools
| Tool | Returns |
|---|---|
list_intents | 100 buyer transaction intents with supply status |
get_intent | One intent's required context, decision factors, honest supply status |
list_offers | Supply catalog with dated verified facts and explicit unverified fields |
match_workload | Deterministic, explainable match or rejection for a workload |
search_intents | Filter the 100 intents by keyword / category without downloading the catalog |
build_request | Fill a quote request with buyer context and return dispatchable text |
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.
From reading to doing
Most intents have no verified supplier, so the useful output is not a recommendation —
it is a request an agent can actually dispatch. build_request takes an intent id
plus buyer context and returns a filled quote request, the list of any still-missing
required fields, and ready-to-send text. Pure computation: nothing is transmitted by
the server, and no price, vendor, specification or availability is asserted.
The same 100 templates are available over plain HTTP at
https://agentshopping.org/api/v1/requests/{id}.json
(index: /api/v1/requests/index.json).
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_fieldsrather 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:
MCP_PORT=8787 MCP_DATA_ROOT=/path/to/site python3 src/http-server.py
Design constraints it holds to:
- Binds to
127.0.0.1only. 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=64MandCPUQuota=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.GETreturns405— 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
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
npm i -g mcp-publisher
cd 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.
Reviews
No reviews yet
Be the first to review this server!
More Developer Tools MCP Servers
Rea
Freeby Morluto · Developer Tools
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Paperclip
Freeby Paperclipai · Developer Tools
Trending hip-hop artist momentum scores across four cultural dimensions.
Scrapling
Freeby D4Vinci · Developer Tools
Web scraping with stealth HTTP, real browsers, and Cloudflare bypass. CSS selectors supported.
Git
Freeby Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
MCP Marketplace
Freeby mcp-marketplace · Developer Tools
Search and install MCP servers from inside your AI client.
