Marden Yard Permits
Server Details
Daily US building permits, cleaned: search by area, trade and value, with coverage and freshness.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 4 tools
Each tool occupies a distinct layer: coverage reports corpus metadata, search_permits queries by criteria, permit_detail drills into a single permit, and watch_area sets up a recurring feed. There is no realistic scenario where an agent would confuse these four purposes.
Two tools follow a verb_noun pattern (search_permits, watch_area) while the other two are bare noun phrases (coverage, permit_detail). The names are readable and internally sensible, but the set mixes conventions rather than settling on one predictable scheme.
Four tools cover the core read-and-monitor workflow for a permit data service, and each earns its place. The surface is on the lean side—no reference lookups or watch management—but it is not arbitrarily bloated or trivially thin.
Search, detail, coverage, and standing watches form a coherent core, but the surface has dead ends: a created watch cannot be listed, paused, or deleted, and there is no lookup for valid trades or jurisdictions beyond the coverage summary. Agents would need workarounds for watch lifecycle and filter vocabulary.
Available Tools
4 toolscoverageBInspect
Which jurisdictions are covered, how fresh each is, and approximate weekly permit volume.
Inputs: jurisdiction.
permit_detailBInspect
Scope, permit-declared value, status, dates, contractor and the raw source fields for one permit.
Inputs: id (required).
search_permitsCInspect
Permits by area (jurisdiction, ZIP, community area), trade, minimum permit-declared value, date range and confidence floor, with a short brief.
Inputs: to, zip, days, from, +6 more.
watch_areaCInspect
A standing watch on the same criteria that delivers each day's new permits.
Inputs: to, zip, days, from, +9 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Daily US building permits for 30 cities and counties. Free counts; records paid per call via x402.
Newly issued building permits in 10 US cities, with trade tags and job values, daily.
Source-linked building-permit search across 34 US states and DC, with county-level coverage.
Fresh US building permits with contacts from official city APIs. Construction lead generation.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to search permit coverage, count matching building permits, and retrieve clean permit rows with property and contractor details, including free initial results and paid per-row access.38 PyPIMIT
- AlicenseAqualityCmaintenanceFrench building permits MCP server: 1.2M Sitadel permits (2014-2026, daily refresh), DVF transactions, cadastre DGFiP, PLU zoning, BRGM risks, and property-dealer opportunity scoring through 11 MCP tools. Free tier 500 req/month, no credit card.11303 PyPI3MIT
- AlicenseAqualityDmaintenanceSearch official US government data from any MCP client: building permits from 10 city open-data portals, federal contract opportunities from SAM.gov with contracting-officer contacts, and the CMS NPI healthcare-provider registry. Open-source TypeScript server; data delivered via Apify's pay-per-result actors using your own Apify token.3MIT
- AlicenseAqualityDmaintenanceRegulatory intelligence API — look up permits, licenses, and fees for food service businesses in Austin, SF, and NYC.338 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.