
Agent Signal
io.github.dan24ou-cpuPublished by GitHub account dan24ou-cpuv1.0.0Updated Oct 24, 2026
Collective intelligence for AI shopping agents — product intel, deals, and more
Overview
Agent Signal is a shared shopping-intelligence service that lets an AI shopping agent log sessions and pull pooled product, deal, merchant and seller analytics.
- What you can do
- Start and log shopping sessions, product evaluations, comparisons and outcomes
- Look up product intelligence, category recommendations, constraint matches and similar session outcomes
- Check merchant reliability, deal verdicts, warnings and budget or trending products
- Create and check price alerts
- Review seller-side competitive landscape, rejection analysis, category demand and merchant scorecards
- When to use it
- Useful when an assistant helps users shop and you want cross-agent signals such as selection rates, rejection reasons, price history and merchant reliability, or when a seller wants to see how agents treat their products. Not needed for general product search without shared intelligence.
- Requirements
- Either the hosted remote endpoint or a local process run via npx with Node.js. Self-hosting needs a PostgreSQL database configured through DATABASE_URL. No accounts, API keys or headers are declared.
Installation
In SourceWeft
- Open Agent Signal in the dashboard and add it to a workspace.
- 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/io.github.dan24ou-cpu%2Fagent-signal/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.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"agent-signal": {
"type": "http",
"url": "https://agent-signal-production.up.railway.app/mcp"
}
}
}README
AgentSignal
[npm version] [GitHub stars] [License: MIT] [MCP Tools]
The collective intelligence layer for AI shopping agents.
Every agent that connects makes every other agent smarter. 1,200+ shopping sessions, 95 products, 50 merchants, 10 categories — and growing.
Why this exists: When AI agents shop for users, each agent starts from zero. AgentSignal pools decision signals across all agents so every session benefits from what every other agent has already learned — selection rates, rejection patterns, price intelligence, merchant reliability, and proven constraint matches.
Quick Start (30 seconds)
Remote — zero install, instant intelligence:
Local via npx:
Claude Desktop / Claude Code:
One Call to Start Shopping Smarter
The smart_shopping_session tool logs your session AND returns all available intelligence in a single call:
Returns:
- Your session ID for subsequent logging
- Top picks from other agents in that category
- What constraints and factors mattered most
- How similar sessions ended (purchased vs abandoned)
- Network-wide stats
23 MCP Tools
Smart Combo Tools (recommended)
Buyer Intelligence — Shop Smarter
Seller Intelligence — Understand Your Market
Discovery & Monitoring
Write Tools — Contribute Back
Example: Full Agent Workflow
Every step feeds the network. The next agent shopping for headphones benefits from your data.
Example: Seller Intelligence Workflow
Categories with Active Intelligence
Agent Framework Examples
Ready-to-run examples in /examples:
All examples connect to the hosted MCP endpoint — no setup beyond pip install required.
REST API
Merchant-facing analytics at https://agent-signal-production.up.railway.app/api:
Self-Hosting
Architecture
- MCP Server — Stdio transport (local) + Streamable HTTP (remote)
- REST API — Express on the same port
- Database — PostgreSQL (Neon-compatible)
- 23 MCP tools — 17 read (buyer + seller + discovery) + 6 write
License
MIT
Source: README.md at commit bf41045
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
75% 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
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.