Remote PropertyLabs server that lets an assistant look up public building permits, address-level permit history and city-scoped company permit activity.
What you can do
Search public permit history for a specific civic address in a given city
Retrieve a single permit by its numeric PropertyLabs permit ID and city slug
Get aggregate, city-scoped permit activity samples matching a developer, applicant, builder or contractor name
Results follow the public PropertyLabs field boundary, so applicant and contractor identities stay gated
When to use it
Useful when you need public construction and development records for a property address, want details on a permit already referenced by a public PropertyLabs permit page, or want a rough aggregate view of how active a builder or developer is in a city.
Requirements
A remote streamable HTTP endpoint at propertylabs.org; no packages, environment variables or headers are declared. No authentication is declared, though the server may still apply its own access rules.
Before you install
Anonymous company-activity results are aggregate only and deliberately omit matched project addresses, permit numbers and coordinates, so they cannot be used to identify individual projects. Applicant and contractor identities are withheld by design; do not expect the assistant to surface them.
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.AlgoFalgo%2Fpropertylabs/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.
Look up the public PropertyLabs permit history for a specific civic address in a specific city. Use this for address-level construction history and activity. This follows the same public field boundary as PropertyLabs address pages and does not return applicant names, contractor names or permit numbers.
Parameterscityrequiredaddressrequired
get_public_permit
Get a public PropertyLabs permit record
Retrieve a permit using the numeric PropertyLabs canonical permit ID and city slug. Use this for a permit already referenced by a public PropertyLabs /permit/{city}/{id} URL. Returns only fields allowed on the public permit page; applicant and contractor identities remain gated.
Parameterscityrequiredcanonical_idrequired
search_company_activity
Get a public company activity snapshot
Get an aggregate, city-scoped sample of permit activity matching a developer, applicant, builder or contractor name. Only applicant/developer/contractor party-field matches are counted. Anonymous results are aggregate only and never return company-matched project addresses, permit numbers, coordinates or raw records.
Parameterscityrequiredcompanyrequired
Version history
1
v0.2.0LatestSep 16, 2026
Score
83%
83% 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
DescriptionRequired15 pts
Logo10 pts
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.