streamable-httpupdated 3mo ago
Two production-ready Apify Actors available as MCP servers via the Apify MCP Gateway. Free tier users can call them directly from any MCP client (Claude, Cursor, Windsurf, etc.); pay-per-event pricing means you only pay for what you use.
What can you do with US Building Permit Aggregator?
Apify MCP Servers — by dizzyvinci
Two production-ready Apify Actors available as MCP servers via the Apify MCP Gateway. Free tier users can call them directly from any MCP client (Claude, Cursor, Windsurf, etc.); pay-per-event pricing means you only pay for what you use.
Servers
1. Shopify Catalog Monitor
Track price drops, stock-outs, restocks, and new/removed products across any public Shopify store.
MCP endpoint:
https://mcp.apify.com?tools=dizzyvinci/shopify-catalog-monitor
Apify Store: https://apify.com/dizzyvinci/shopify-catalog-monitor
Tools exposed: shopify-catalog-monitor — polls stores and returns only the diffs (price changes, stock changes, product adds/removes). On first call per store, captures a baseline; subsequent calls return what changed.
Use cases: competitor price intelligence, dropship product research, brand MAP enforcement, restock alerts.
2. US Building Permit Aggregator
Pull recent building & construction permits from 9 major US cities in one unified schema.
MCP endpoint:
https://mcp.apify.com?tools=dizzyvinci/building-permit-aggregator
Apify Store: https://apify.com/dizzyvinci/building-permit-aggregator
Tools exposed: building-permit-aggregator — returns permits from Chicago, LA, Austin, SF, Seattle, DC, Nashville, Philadelphia, and Boston. All data from official government open-data APIs (Socrata, ArcGIS, Carto, CKAN).
Use cases: construction lead gen, market intelligence, real-estate research, contractor prospecting.
Usage with Claude / any MCP client
Add either server to your MCP client config. Example for Claude Desktop (claude_desktop_config.json):
{
"mcpServers": {
"shopify-monitor": {
"url": "https://mcp.apify.com?tools=dizzyvinci/shopify-catalog-monitor",
"headers": {
"Authorization": "Bearer <your-apify-token>"
}
},
"building-permits": {
"url": "https://mcp.apify.com?tools=dizzyvinci/building-permit-aggregator",
"headers": {
"Authorization": "Bearer <your-apify-token>"
}
}
}
}
Get a free Apify token at console.apify.com/settings/integrations. Free tier includes $5/month in compute credits.
Pricing
Pay-per-event — no subscription:
| Actor | Event | Price |
|---|---|---|
| shopify-catalog-monitor | store-checked (per store polled) |
$0.05 |
| shopify-catalog-monitor | change-detected (per change found) |
$0.002 |
| building-permit-aggregator | permit (per record returned) |
$0.005 |
80% of revenue goes to the developer (Apify takes 20%).
License
MIT
Install
Add US Building Permit Aggregator to your client. Pick the one you use.
claude mcp add --transport http us-building-permit-aggregator https://mcp.apify.com?tools=dizzyvinci/building-permit-aggregatorcodex mcp add us-building-permit-aggregator --url https://mcp.apify.com?tools=dizzyvinci/building-permit-aggregator{
"mcpServers": {
"us-building-permit-aggregator": {
"url": "https://mcp.apify.com?tools=dizzyvinci/building-permit-aggregator"
}
}
}Add to `~/.cursor/mcp.json`, or `.cursor/mcp.json` for a single project.
{
"servers": {
"us-building-permit-aggregator": {
"type": "http",
"url": "https://mcp.apify.com?tools=dizzyvinci/building-permit-aggregator"
}
}
}Add to `.vscode/mcp.json` in your workspace.
{
"mcpServers": {
"us-building-permit-aggregator": {
"url": "https://mcp.apify.com?tools=dizzyvinci/building-permit-aggregator"
}
}
}Add to `claude_desktop_config.json`, then restart Claude Desktop.
{
"mcpServers": {
"us-building-permit-aggregator": {
"serverUrl": "https://mcp.apify.com?tools=dizzyvinci/building-permit-aggregator"
}
}
}Add to `~/.codeium/windsurf/mcp_config.json`.
Score
39 / 100
Incomplete
- Documentation22/25
- Maintenance16/25
- Trust6/20
- Capability0/15
- Install experience12/15
- Documents what it does and how to connect
- Has a resolvable package or endpoint
- Exposes at least one tool, prompt or resource
- README has substantive content
- Includes a code example
- Documents its configuration
- Mentions credentials or security posture
- Last commit 88 days ago
- Has a release history
- Repository is not archived
- No licence detected
- Namespace verified in the official MCP registry
- Claimed by its owner
- Published under an organisation
- 0 tool(s) documented
- Provides prompt templates
- Provides resources
- 6 documented install method(s)
- Published to a package registry
- Offers a hosted endpoint — no local install
Version history
| Versions | Published |
|---|---|
| 0.1.1Latest | Jun 5, 2026 |