FIPS County Code Lookup — 3,231 US Counties

Created By
easysolutions9063 months ago
Look up US county FIPS codes. Search by code, county name, or state. 3,231 counties. Used by mortgage, title, GIS, and government platforms.
Overview

MCP FIPS Server

A Model Context Protocol (MCP) server for looking up US counties by FIPS code, name, or state. Covers all 50 states, DC, and territories.

Tools (4 total)

ToolDescription
fips_lookupLook up a county by its 5-digit FIPS code
fips_searchSearch counties by name, optionally filtered by state
fips_stateList all counties in a state by FIPS code or abbreviation
fips_statsGet database statistics: total counties, states, and counts by state

Install

npx @easysolutions906/mcp-fips

Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "fips": {
      "command": "npx",
      "args": ["-y", "@easysolutions906/mcp-fips"]
    }
  }
}

Cursor

Add to .cursor/mcp.json:

{
  "mcpServers": {
    "fips": {
      "command": "npx",
      "args": ["-y", "@easysolutions906/mcp-fips"]
    }
  }
}

REST API

Set PORT env var to run as an HTTP server.

  • GET /lookup?fips=06037 -- look up county by FIPS code
  • GET /search?name=los+angeles&state=CA -- search counties by name
  • GET /state/:code -- list all counties in a state (e.g., /state/CA)
  • POST /lookup/batch -- batch lookup multiple FIPS codes
  • GET /stats -- county counts by state

Data Source

US Census Bureau FIPS county codes. Run npm run build-data to regenerate from the latest Census data.

Transport

  • stdio (default) -- for local use with Claude Desktop and Cursor
  • HTTP -- set PORT env var to start in Streamable HTTP mode on /mcp

Server Config

{
  "mcpServers": {
    "fips": {
      "command": "npx",
      "args": [
        "-y",
        "@easysolutions906/mcp-fips"
      ]
    }
  }
}
Project Info
Created At
3 months ago
Updated At
3 months ago
Author Name
easysolutions906
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago