Data Collection

gwinnettpulse.com

Accesses and searches Gwinnett County building and development permit data, including weekly summaries and city statistics.

1 endpoint7 known toolsFirst detected August 29, 2026Last detected August 29, 2026

ENDPOINT 1

https://gwinnettpulse.com/mcp

No auth detected

MCP server metadata

Name: gwinnettpulse
Version: 1.0.0

Capabilities

tools

Server instructions

Hank's weekly letter on what's getting built in Gwinnett County, Georgia, backed by every permit the county issues. search_permits finds permits by city, week, type, keyword or cost; get_permit gives one in full; read_letter returns Hank's column for a week (newest by default); list_weeks and list_cities are the indexes; get_stats has the totals; subscribe signs an email up for the Friday letter. Weeks are keyed by their Monday (YYYY-MM-DD).

Known tools 7

search_permits

Search Gwinnett County building and development permits.

Inferred read-only

get_permit

One permit in full — every field the county filed (address, parcel, contractor, developer, zoning, estimated cost, square footage, lots, units, dates…).

Inferred read-only

read_letter

Read Hank's weekly letter for a week in markdown — the column itself plus that week's numbers.

Inferred read-only

list_weeks

Every week the paper covers, newest first: letter number, date range, permit count, total estimated value, and the week key to use with read_letter and search_permits.

Inferred read-only

list_cities

Every city that appears in the permits, with permit counts and total estimated value, busiest first; the eleven curated cities include a link to their hub page.

Inferred read-only

get_stats

Totals for the whole paper or one week: permit count, estimated value, split by type, top ten cities, weeks covered.

Inferred read-only

subscribe

Subscribe an email address to Hank's letter — one email every Friday, free, unsubscribe link in every send.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.gwinnettpulse]
url = "https://gwinnettpulse.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "gwinnettpulse": {
      "type": "http",
      "url": "https://gwinnettpulse.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: gwinnettpulse
Remote MCP URL: https://gwinnettpulse.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "gwinnettpulse": {
      "url": "https://gwinnettpulse.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "gwinnettpulse": {
      "type": "http",
      "url": "https://gwinnettpulse.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "gwinnettpulse",
  "transport": "streamable-http",
  "url": "https://gwinnettpulse.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.