Servidor MCP de CitySignal

• Nome no registrocom.citysignalai/citysignalverificado no registro MCP

O nome no registro fica sob citysignalai.com. O registro só libera esse espaço de nomes para quem prova controle do domínio por DNS ou HTTP.

• Estadorespondeverificado em 2026-10-20
• Ferramentas23
• O servidor se chamacitysignal
• Versão do servidor1.0.0
• Versão do protocolo2025-06-18

Em 2026-10-20 o servidor respondeu a initialize e tools/list sem login. Primeira resposta em 141 ms.

• As ferramentas fazem check commute roads for closures before leaving, mas não find nearby gas with a recently checked price; fold errands and stops into a planned week.
• Verificado em 2 dos 7 dias necessários para julgar a confiabilidade.

Dito por regras a partir das medições acima. A primeira chamada provável é a escolha de um modelo na lista de ferramentas; leia a descrição antes de confiar nela.

• Nota INITE MCPdepois de uma semanaa nota precisa de 7 verificações diárias: 2 até agora
• O que um agente consegue fazer com ele1 de 3 casos de uso
• Respondeumedindo2 das 7 verificações diárias necessárias para mostrar a porcentagem
• Mediana da primeira resposta219 ms
• Espaço no contexto do agente≈ 7.759 tokensas definições de todas as ferramentas (23), que o agente carrega a cada turno
• Definições das ferramentasA · 96 de 100
• Resultados tipados23 de 23 ferramentasdeclaram outputSchema: o resultado chega tipado e é lido de uma vez

• Parâmetros sem descrição: em 5 de 23

Um programa verifica o servidor uma vez por dia: initialize e tools/list, sem modelo. Os tokens são o tamanho das definições, a cerca de quatro caracteres por token. A nota é a média de seis verificações do nome, da descrição, do esquema e das anotações de cada ferramenta; diz se as ferramentas estão bem descritas, não se funcionam. A nota pesa só o que foi medido: se responde (30%), se faz o trabalho do produto (25%), definições (20%), contexto (10%) e uso (15%). Uma parte não medida fica de fora, e uma instrução oculta limita a nota a 40. O estado dos servidores MCP dos fornecedores: método e números →

• 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). Call this when unsure which city slug to…

• 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…

• 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…

• 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…

• city_incidents

  Four weeks of what happened in a city, sorted by kind, for one category. roads (default): crashes, stalled vehicles, hazards and debris, closures, vehicle fires. power: outages by size (one home, small, neighborhood, large), planned…

• cities_report

  Report mode: how every live CitySignal city is doing, in one call. The CitySignal Index for the last complete week (Sunday to Saturday): each city scored against its own typical week (Quiet, Typical, Busy, Heavy, with how many times…

• 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. Each event carries…

• 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. When a real picture exists it carries…

• 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…

• 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. Each card has a headline, time, city, and a Cleared /…

• get_profile

  The connected CitySignal account: a stable opaque id and display name. Call this to confirm which account is linked before reading personal tools.

• 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. Use for 'anything I should know today', 'what's near my…

• 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. Use when they ask for…

• 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…

• 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. Use for 'what can I pick up on the way', 'any errands I can do…

• 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. Non-private lists include a revocable share link that expires after seven…

• my_spots_and_routes

  The connected person's saved spots (name, kind, part of town, alert radius) and routes (name, from, to, schedule). Use to understand what 'home', 'work' or 'my commute' refer to before answering about them. Addresses are not included…

• 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…

• 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. The address must resolve to one confident…

• 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…

• 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. Codes are per person and per day; a…

• 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. When an…

• 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. Returns the person's first name, the…