Skip to content
Permit Scouter logo

Permit Scouter MCP server

Which MCP servers are Permit Scouter's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-28

← Back to Permit Scouter

Whose server it is
  • Registry namecom.permitscouter/permitsverified in the MCP registry

The registry name sits under permitscouter.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-28
  • Stateanswerschecked 2026-10-28
  • Tools6
  • Server calls itselfPermit Scouter
  • Server version1.30.0
  • Protocol version2025-06-18

On 2026-10-28 the server answered initialize and tools/list without a sign-in. First answer in 247 ms.

Should an agent connect itConnect it
  • Its tools do every use case we checked: Find new roofing, HVAC and solar permits by area and date; Look up every permit filed at one address; Check a contractor's permit history and totals by trade.

Once connected

  • For "Find new roofing, HVAC and solar permits by area and date", the likely first call is search_permits.
  • For "Look up every permit filed at one address", the likely first call is property_history.
  • For "Check a contractor's permit history and totals by trade", the likely first call is contractor_history.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 7, the first on 2026-10-28
  • INITE MCP score100 of 100answers 100 · does the job 100 · definitions 100 · context 100 · connects 100
  • What an agent can do with it3 of 3 use cases
  • Answered100% of days7 of 7 daily checks
  • Median first answer251 ms
  • Space in an agent's context≈ 870 tokensthe definitions of all its tools (6), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results2 of 6 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • can do · Find new roofing, HVAC and solar permits by area and date
  • can do · Look up every permit filed at one address
  • can do · Check a contractor's permit history and totals by trade

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers6 tools · read 2026-10-28
  • coverage

    Free. Cities covered today, permit counts, date range and last update time.

  • sample_permits

    Free. Three recent permits, to see the record format before paying.

  • search_permits

    Search new building permits by trade, job value, date, zip or city. Newest first, up to 25 per call. Price: $0.02 per call (x402, USDC on Base).

  • get_permit

    One permit and every change recorded to its status, value or issue date. Price: $0.01 per call (x402, USDC on Base).

  • property_history

    Every permit recorded at one street address, newest first. Price: $0.05 per call (x402, USDC on Base).

  • contractor_history

    Every permit a contractor has pulled, with total job value and counts by trade. Price: $0.10 per call (x402, USDC on Base).

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "permits": {
      "type": "http",
      "url": "https://api.permitscouter.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http permitscouter https://api.permitscouter.com/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://api.permitscouter.com/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.