SmartAPIs Products Watch
net.smartapisPublished by smartapis.netOfficial publisherv0.1.1Updated Oct 24, 2026
Testing-phase Products Watch endpoint; public discovery remains while new onboarding is paused.
Overview
A remote SmartAPIs endpoint for Products Watch that lets an assistant explore product-watch data, with public discovery open while new onboarding is paused.
- What you can do
- Connect to a hosted SmartAPIs Products Watch endpoint for product-watch discovery work. Public discovery is available without a key, while keyed access uses an existing SmartAPIs testing key. The server is in a testing phase and new customer onboarding and purchases are currently paused. No tool list is published, so the exact operations an assistant can call are not documented here.
- When to use it
- Worth trying if you already hold a SmartAPIs testing key and want to explore Products Watch from an assistant during its testing phase. Not suitable if you need to sign up as a new customer or make purchases, since onboarding is paused.
- Requirements
- A remote streamable HTTP endpoint at smartapis.net; no local runtime or package is needed. Public discovery works without credentials. Keyed access requires an existing SmartAPIs testing key sent in the X-API-Key header. Network access to the endpoint is required.
Installation
In SourceWeft
- Open SmartAPIs Products Watch 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/net.smartapis%2Fproducts-watch/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": {
"smartapis-products-watch": {
"type": "http",
"url": "https://smartapis.net/mcp"
}
}
}Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
56% 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
Publish an icon in the registry entry.
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.