# FCC Geo MCP > FCC Geo converts geographic coordinates into official US government zones. This MCP instantly maps any latitude and longitude pair to precise State, County, Census Block FIPS codes, plus all overlapping FCC telecommunication boundaries like CMAs and PEAs. Zero authentication means you just feed it the coordinates and get structured data—no keys, no fuss. ## Overview - **Category:** telecommunications - **Price:** Free - **Tags:** geospatial-analysis, census-data, telecom-mapping, coordinate-conversion, spatial-intelligence ## Description Need to know exactly what jurisdiction a point on Earth falls into? This connector links your agent directly to the US Federal Communications Commission's geographic intelligence sources. It’s designed for analysts who need instant spatial intersection analysis without wrestling with API keys or complex setup. You input coordinates, and it spits out structured data showing everything that overlaps: from the census block code down to which major cellular market area covers that spot. Think real estate, logistics planning, or spectrum licensing research—if your job depends on knowing *where* something is in official terms, this MCP works. It’s hosted on Vinkius, making it simple for any of your AI clients to connect and use the data immediately. ## Tools ### get_census_block_by_lat_lon Converts precise geographic coordinates into official US Census Blocks, County codes, and FIPS identifiers. ### get_fcc_areas_by_lat_lon Retrieves specific FCC telecommunication boundaries (CMA, PEA, EAG) that intersect the provided coordinates. ## Prompt Examples **Prompt:** ``` Find the Census Block for coordinates 40.0 latitude and -85.0 longitude. ``` **Response:** ``` I've checked the FCC geodatabase. Those coordinates correspond to Wayne County in Indiana (State FIPS 18, County FIPS 18177). The exact Census Block FIPS code is 181770103002008. ``` **Prompt:** ``` Which telecommunication economic areas overlap with coordinates 40, -85? ``` **Response:** ``` According to the FCC Area boundaries, coordinates 40.0, -85.0 fall under Cellular Market Area (CMA) 408, Major Economic Area (MEA) 019, and Economic Area Grouping (EAG) 704. ``` **Prompt:** ``` Convert the coordinate pair 34.05, -118.24 into proper Census details. ``` **Response:** ``` Checking the FCC Geo repository... Coordinates map directly to California (State FIPS 06), Los Angeles County (County FIPS 06037). The block FIPS evaluates firmly to 060372074001004 natively effortlessly. ``` ## Capabilities ### Identify Census Block Codes Converts exact coordinates into precise State, County, and official US Census Block FIPS codes. ### Map Telecom Overlaps Retrieves all FCC broadcast zones, including Cellular Market Areas (CMA) and Economic Area Groupings (EAG), that cover the coordinates. ### Determine County Jurisdiction Pinpoints the specific county boundary a location falls within using standard FIPS identifiers. ### Check Zoning Boundaries Provides critical government zoning data, moving beyond simple GPS points to regulatory regions. ## Use Cases ### Market Entry Planning A telecom consultant needs to know if a new city is within a viable Cellular Market Area (CMA). They ask their agent to run the coordinates through `get_fcc_areas_by_lat_lon` to confirm coverage before submitting a proposal. ### Zoning Dispute Resolution A developer needs to verify if a proposed site falls under specific county zoning laws. They use the coordinates with `get_census_block_by_lat_lon` to pull the definitive County and FIPS codes for legal review. ### Logistics Route Optimization A logistics AI needs to ensure a delivery point is serviced by adequate infrastructure. It checks both `get_census_block_by_lat_lon` (for county boundaries) and `get_fcc_areas_by_lat_lon` (for communication coverage). ## Benefits - You instantly get Census Block details. Instead of manually cross-referencing massive government datasets, the `get_census_block_by_lat_lon` tool pulls the exact State and County FIPS codes you need for data warehousing. - Map full broadcast coverage automatically. The `get_fcc_areas_by_lat_lon` tool tells you instantly if a location is covered by specific Cellular Market Areas (CMA) or Economic Area Groupings (EAG). - No API keys required. Since the service is fully open and unmetered, your agent doesn't stall waiting for credentials or hitting usage limits. - Analyze overlaps effortlessly. You can feed a single location and get both its Census Block details *and* its FCC zone coverage in one go. - Speed up due diligence. Instead of spending days on manual GIS research, you run the coordinates through your agent and get regulatory data in seconds. ## How It Works The bottom line is: it gives you a complete picture of official jurisdiction just by knowing the coordinates. 1. Your agent sends the MCP the specific latitude and longitude coordinates you care about. 2. The MCP queries the FCC geodatabases for both census data and telecom boundaries simultaneously. 3. You get back a single, structured response containing all relevant official government codes (FIPS, CMA, etc.). ## Frequently Asked Questions **Do I need to pay or provide an API Key?** Neither! The FCC Geo API operates completely publicly. There are zero auth steps, meaning you can plug it into any AI agent securely and immediately. **How accurate is the coordinate conversion?** It draws directly from US federal census files. When you submit raw geographic decimal degrees, the system instantly identifies the overlapping demographic and telecommunication limits with absolute national accuracy. **Can I query locations outside of the United States?** No. The FCC Geo API specifically maps United States territories and census blocks. International coordinates will not return valid census or telecommunication zone data. **If I combine calls to `get_census_block_by_lat_lon` and `get_fcc_areas_by_lat_lon`, how do I handle overlapping data?** You pass the same coordinates to both tools, which returns two distinct datasets. Your agent then needs a simple logic step to correlate the resulting FIPS codes with the CMA/EAG zones for complete context. **Does `get_census_block_by_lat_lon` return just readable names or the full numeric Census Block FIPS code?** It provides the precise, multi-part FIPS codes for State, County, and the specific Census Block. This raw coding is essential for accurate data engineering. **What should I do if I input coordinates that fall in an unmapped or non-existent area using `get_fcc_areas_by_lat_lon`?** The tool handles invalid inputs by returning a clear error message detailing the coordinate failure. Always check for null returns before attempting to process telecom zones. **Are there any rate limits or volume restrictions when using this MCP, even though it's listed as unmetered?** While endpoints are open and unmetered, your AI client must still respect standard API request rates. High-volume batch processing should be managed by your agent's execution workflow. **How can I ensure the latitude and longitude inputs for `get_census_block_by_lat_lon` are correctly formatted?** The tool expects standard decimal format coordinates (e.g., 34.05, -118.24). Ensure your agent passes these as floating-point numbers.