Waitlist-stage pricing-page monitor: plans and early pricing, plus a PriceMovedBot robots.txt check.
Scored across 2 tools
The two tools have completely non-overlapping purposes: product_info returns static metadata about the service with no network calls, while robots_check performs a live RFC 9309 fetch for a given URL. An agent can trivially select the right one based on whether it needs service facts or a robots.txt verdict.
Both names use a consistent snake_case noun_verb/noun-topic style (product_info, robots_check) that is readable and predictable. No convention mixing is present.
Two tools is thin for a server whose stated domain is pricing-page change monitoring, though it plausibly reflects a waitlist-only product surface. It sits at the borderline of under-scoped rather than being badly matched.
The core domain — monitoring pricing pages and surfacing changes — has no tools at all; the surface exposes only service metadata and a robots.txt pre-check. There is no way to create, list, or retrieve monitoring targets or detected changes, leaving significant gaps for any real workflow.
Facts about PriceMoved, a pricing-page change monitor that is waitlist-only today: what is available now, the planned Free/Starter/Pro plans (pages, check intervals, Slack, history) with early USD prices that are subject to change, the crawler user agent, and links to the waitlist, privacy policy and terms. No network calls. Same data as GET /api/product.
Inputs: no named parameters. Returns: name, links, status, contact, +5 more
Fetch the robots.txt of the given public http(s) URL's site (at most 500 KiB, 5 s timeout, redirects followed) and report whether PriceMovedBot is allowed to fetch that URL under RFC 9309 rules: verdict allowed, disallowed, or skipped (robots.txt unreachable, 5xx/429, or too complex: PriceMoved would not fetch). Does not fetch the page itself. Domain names only (no IP addresses or ports). About 10 checks per minute and 30 per hour per network; results cached 10 minutes. Same engine as GET /api/robots-check.
Inputs: url (required). Returns: url, note, cached, allowed, +5 more
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Page change monitoring, sitemap discovery, prompt-injection screening, clean markdown. Free preview.
Monitor web pages for price, stock or text changes; low-noise alerts via MCP, API and webhooks.
Check AI crawler robots.txt policy and monitor public-site policy, sitemap, and llms.txt changes.
Check AI crawler robots.txt policy and monitor public-site policy, sitemap, and llms.txt changes.
Add one secure layer between your agents and this server.