Data Collection

citysignalai.com

CitySignal is an MCP server that aggregates and deduplicates official local alerts—such as roads, transit, weather, power, water, and construction—into city-level live, ongoing, upcoming, and recap views with nearby and weekly analysis.

1 endpoint23 known toolsFirst detected October 21, 2026Last detected October 21, 2026

ENDPOINT 1

https://citysignalai.com/mcp

No auth detected

MCP server metadata

Name: citysignal
Version: 1.0.0

Capabilities

resources.listChangedtools.listChanged

Server instructions

CitySignal is a live city layer: official road, transit, weather, power and water signals fused, deduplicated and kept current, with a week of memory. City tools need no sign-in. Personal tools (my_*) read the signed-in person's own saved spots, routes, errands, priced list and daily brief; Circle tools (circle_*) read only what people in their Circle chose to share with their assistant; if a personal tool answers 401, the person needs to connect their CitySignal account. Every tool reads, except two that write on the person's explicit ask: add_errand adds one item to their own errand list in their words (optionally with a day), and save_spot saves a spot at an address they typed, only when the address resolves to one confident match; otherwise it returns suggestions and saves nothing until they confirm one. Neither changes or deletes anything that exists. my_detours and get_detour read Scout's detour offers for today and what a DETOUR-XXX code opens. Always pass the city slug from list_cities; the default is atlanta. Live, with public trackers: Atlanta, Nashville, Charlotte, Dallas, Austin, Seattle, Chicago, San Francisco, Raleigh, Houston, Greensboro, Birmingham, Pensacola. In preview: Louisville, San Jose, Memphis, Knoxville, Wilmington, Asheville, Salt Lake City, Ogden, Provo-Orem, Las Vegas, Phoenix, Madison, Milwaukee, Los Angeles, Riverside, San Diego, Sacramento, Columbus, Cincinnati, Cleveland, Toledo, Akron, Charleston, Greenville, Columbia, Myrtle Beach, Denver, Colorado Springs, Savannah, Augusta, Columbus, Macon, Portland, Chattanooga, El Paso, New York, Minneapolis, Stockton, Fresno, Bakersfield, Oxnard-Ventura, Spokane, Orlando, Tampa, Jacksonville, Sarasota, Lakeland, Daytona Beach, Melbourne, Miami. A city list_cities marks preview is still being checked against what residents see (anyone may choose one at sign-up, its public tracker is not out yet): answer about it, and say it is in preview. Pictures: city_now and get_signal attach CitySignal picture cards (picture_url, label and a ready markdown link, plus a few inline images) for incidents a road camera captured; city_pictures returns up to six for 'show me what's happening', with a gallery_url that opens all cards. Inline images are visible to you only, not to the person: give the person the markdown links (or the gallery_url first) and never say an image is shown or above. Always say the time on the card: a card tagged Cleared or Earlier today is a past moment, not a live view. An item with no picture may carry placeholder_url, a summary card and not a picture. In apps that show CitySignal cards natively, the cards appear on their own; still add one line per card (what it shows and when). Show only CitySignal pictures for an incident: never add images from the web or any other source, not even as illustrations. Describe where information comes from only with the general labels the tools return (road reports, the weather service, the power utility, local news); do not name agencies, departments or feeds, even ones you know.

Known tools 23

list_cities

The cities CitySignal covers, with their slug, timezone, center point, the official sources it reads, and status: live, or preview (still being checked, open to sign-ups, trackers not yet public).

Inferred read-only

city_now

Live alerts in a city, deduplicated from official feeds (roads, transit, weather, power, water, construction) and placed by the app's own rule into four buckets: now (live and current), ongoing (live for more than two days, or unconfirmed), ahead (starts later, within 7 days, grouped by day) and recap (ended in the last 12 hours).

Inferred read-only

city_near

Alerts within a radius of a latitude and longitude in a city, nearest first, each with its distance in miles: live ones (bucket now, ongoing or ahead) and ones that ended in the last 12 hours (bucket recap, so 'was there anything here this afternoon' can be answered).

Inferred read-only

city_week

Week-over-week memory for a city: counts by category for the last 7 days and the 7 before, a plain-language read of the week, measured insights, where it concentrated (areas and corridors), why an unusual week was unusual, and what a newsroom published about it.

Inferred read-only

city_incidents

Four weeks of what happened in a city, sorted by kind, for one category.

Inferred read-only

cities_report

Report mode: how every live CitySignal city is doing, in one call.

Inferred read-only

city_events

Events, concerts and home games coming up in a city within the next N days (default 7, max 14), with venue area, ticket price range and a ticket link when listed, and expected local traffic impact when known.

Inferred read-only

get_signal

Full detail for one signal by its signal_id (from any other tool): summary, place, area, corridor, timing, source link, confidence and whether a live camera check confirmed or contradicted it.

Inferred read-only

city_cameras

Road cameras within a radius of a latitude and longitude (default 1 mile, max 5), nearest first, each with a link to its current still and whether it has live video; plus the camera checks CitySignal ran on alerts there in the last N hours (default 24, max 72): what the camera showed and whether it matched the alert.

Inferred read-only

city_pictures

Up to six CitySignal picture cards for incidents in a city, including ones that already cleared: the frame a camera check kept, or a live view while the incident is still going.

Inferred read-only

get_profile

The connected CitySignal account: a stable opaque id and display name.

Inferred read-only

my_day

The connected person's own Now / Ongoing / Ahead / Recap: live signals that touch their saved spots and routes, in the same buckets the app shows, plus today's calendar line.

Inferred read-only

my_brief

Today's written brief for the connected person: top alerts, citywide items, what is near their spots with why it matters and a recommended action, events, what is ongoing, what came and went since the last brief.

Inferred read-only

my_routes_now

Each of the connected person's saved routes with its current state (Clear, Minor delay, Expect delays, Consider another route) and what changes how the road drives on its corridor now and ahead: crashes, lane closures, roadwork, weather over the route's counties, and event crowds around the trip time.

Inferred read-only

my_along_the_way

Errands on the connected person's list that fit a trip they already make today, with the store, the detour in minutes, why that store, and a price line when one is known.

Inferred read-only

my_list

The connected person's shopping list as Scout priced it at their home Kroger: each item with product, size, price and whether it is on sale, plus the running total.

Inferred read-only

my_spots_and_routes

The connected person's saved spots (name, kind, part of town, alert radius) and routes (name, from, to, schedule).

Inferred read-only

add_errand

Adds one errand to the connected person's own list, in their words ('milk and eggs', 'pick up lotion at the pharmacy'), the way the app, Siri and a text to Scout do: Scout reads the store kind from the words and fits the errand into a drive they already make.

Inferred read-only

save_spot

Saves a spot (a place that matters to the connected person, where Scout looks out for them) at an address they typed, with a kind: home, work, school, church, gym or other, and an optional name.

Inferred read-only

my_detours

Scout's detour offers on the connected person's drives today, as the Scout page shows them: the streak line (how many drives or weeks straight home), the offer (worth it: an event they marked interest in, near a drive, as a stop; dodge it: a big crowd a drive passes, with the way around), the DETOUR-XXX code and what the code opens.

Inferred read-only

get_detour

Resolves a DETOUR-XXX code for the connected person: which drive it is on, the event, whether it is worth it (a stop) or dodge it (a way around), the streak and offer lines, and the link that opens it.

Inferred read-only

circle_needs

Open errands and list items of people in the connected person's Circle, for people who turned on assistant access for them, with how long each has waited and whether it was already asked of or accepted by the connected person.

Inferred read-only

circle_along_the_way

Trips people in the connected person's Circle already plan today or tomorrow that fit an errand: a store run someone's item could ride along on, a return or post office stop, a trip they both make.

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.citysignal]
url = "https://citysignalai.com/mcp"
enabled = true

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: citysignal
Remote MCP URL: https://citysignalai.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": {
    "citysignal": {
      "url": "https://citysignalai.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "citysignal",
  "transport": "streamable-http",
  "url": "https://citysignalai.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.