Skip to content

MCP servers › com.citysignalai › citysignal

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

com.citysignalai/citysignal

Live road, transit, weather, power and water signals for US cities, plus your own spots and routes. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-10-23Topic: data-and-databases · AI-classifiedversion 1.0.0streamable HTTP23 tools

Summary

com.citysignalai/citysignal is a remote MCP server listed in the official MCP registry at version 1.0.0. On 2026-10-23 ProtocolProbe connected to it in read-only mode and read its inventory: 23 tools, 4 resources and 0 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

  • met: Registry entry is active and says how to run it
  • not met: Source repository link opens
  • not applicable: Repository is not archived
  • not applicable: Code pushed to the repository in the 90 days before our check
  • not applicable: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Sign-in
none needed to open a session
Tools
23
Described as changing data
2 of 23 toolsAI-classified
Topic
data-and-databasesAI-classified
Last tested
2026-10-23

Add to your client

Observed fact

This server accepted a session without any credential and lists 2 tools whose name or declaration suggests they change data (add_errand, save_spot). That is our reading of the names; we did not call them. Source: our connection, 2026-10-23.

Worth knowing before you connect it

  • 2 tools are described as changing something (add_errand, save_spot): our AI model's reading of the descriptions, not something we tested, and the server opened a session without any credential. We did not call them.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-10-23
Mode
read-only (no tool calls)
Latest version
1.0.0, published 2026-10-20 (registry, as of the 2026-10-23 snapshot)
First listed version
2026-10-20 (earliest version still in the registry; older removed versions would be earlier)
Registry data
snapshot 2026-10-23
Package and repository
checked 2026-10-22
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 1.0.0 (published 2026-10-20).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory
23tools
4resources
0prompts

2 of 23 tools are described as changing something (creating, editing, deleting, sending or running).

  • list_citieson 69 other serversreads or searches

    “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).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • city_nowreads or searches

    “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…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    3 inputs
    • citystring“City slug.”
    • categorystring“Only this category: road, transit, weather, power, water, construction, emergency, film, sanitation, government_notice.”
    • limitinteger“Max items per bucket (default 25).”
  • city_nearreads or searches

    “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…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    6 inputs, 2 required
    • citystring“City slug.”
    • latnumberrequired
    • lonnumberrequired
    • radius_minumber
    • categorystring“Only this category: road, transit, weather, power, water, construction, emergency, film, sanitation, government_notice.”
    • limitinteger“Max items per bucket (default 25).”
  • city_weekreads or searches

    “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 un…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input
    • citystring“City slug.”
  • city_incidentsreads or searches

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

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    3 inputs
    • citystring“City slug.”
    • categorystring“roads (default), power, transit, roadwork or water.”
    • hour_of_weekinteger“0 = Sunday midnight in the city's own time, 17 = Sunday 5 PM, 137 = Friday 5 PM.”
  • cities_reportreads or searches

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

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input
    • modestring“summary (default): the storylines and one line per city, for a quick read.”
  • city_eventson 1 other serverreads or searches

    “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 wh…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    3 inputs
    • citystring“City slug.”
    • daysinteger
    • limitinteger
  • get_signalon 16 other serversreads or searches

    “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.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 1 required
    • citystring“City slug.”
    • signal_idstringrequired
  • city_camerasreads or searches

    “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…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    6 inputs, 2 required
    • citystring“City slug.”
    • latnumberrequired
    • lonnumberrequired
    • radius_minumber
    • hoursinteger
    • limitinteger“Max cameras and max checks (default 10).”
  • city_picturesreads or searches

    “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.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs
    • citystring“City slug.”
    • hoursinteger“How far back, in hours (default 12).”
  • get_profileon 124 other serversreads or searches

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

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • my_dayon 1 other serverreads or searches

    “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.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

Show 11 more tools
  • my_briefreads or searches

    “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 th…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • my_routes_nowreads or searches

    “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: cras…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • my_along_the_wayreads or searches

    “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.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • my_listreads or searches

    “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.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • my_spots_and_routesreads or searches

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

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • add_errandcreates or changes datadescribed as changing data

    “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 t…”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    2 inputs, 1 required
    • textstringrequired“What they need, in their words.”
    • bystring“A day word (today, tomorrow, Friday, next Monday) or an ISO date.”
  • save_spotcreates or changes datadescribed as changing data

    “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.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    5 inputs, 2 required
    • addressstringrequired“The street address or place name they typed.”
    • kindstringrequired“home, work, school, church, gym or other.”
    • namestring“A nickname.”
    • latnumber“Only from a suggestion this tool returned, to confirm it.”
    • lonnumber“Only from a suggestion this tool returned, to confirm it.”
  • my_detoursreads or searches

    “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 interes…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • get_detourreads or searches

    “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 i…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • codestringrequired“The code, like DETOUR-KQM.”
  • circle_needsreads or searches

    “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 accept…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs
    • personstring“First name to narrow to one person.”
    • categorystring“A kind of errand or a word from it: grocery, pharmacy, returns, milk.”
  • circle_along_the_wayreads or searches

    “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.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs
    • categorystring“A store kind or word: pharmacy, grocery, Target, post office.”
    • daystring

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does
100% of 23 tools
Says what it returns
100% of 23 tools
States limits, defaults or errors
22% of 23 tools
Says when to use it
100% of 23 tools
Items covered per tool
3.2 of 4 on average

Counted from the listing

Parameters with a description
72% of 39
Tools with a description
100% of 23
Typical description length
554 characters

The tool set

Counted from the listing

Tools
23
Size of the list
about 10,871 tokens for an agent to load (characters ÷ 4)
Naming
23 of 23 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 23 of 23 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-23 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://citysignalai.com/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "citysignal": {
      "url": "https://citysignalai.com/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "citysignal": {
      "type": "http",
      "url": "https://citysignalai.com/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"citysignal","type":"http","url":"https://citysignalai.com/mcp"}'
Claude Code
claude mcp add --transport http citysignal https://citysignalai.com/mcp
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://citysignalai.com/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint citysignalai.com/mcpSession openedmatchesour test · 2026-10-23
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-10-23

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • Not metSource repository link opensThe registry entry gives no repository link.
  • Does not applyRepository is not archivedNo public GitHub repository to read.
  • Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
  • Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-22. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about com.citysignalai/citysignal

Answered from the data above

Is com.citysignalai/citysignal safe to install?

We do not rate servers as safe or unsafe. 1 of its 2 applicable record checks are met (facts from public records, each listed on this page). What the records show: 2 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does com.citysignalai/citysignal need an API key or sign-in?

It opened a session without any credential on 2026-10-23. The registry entry declares no required credential; no declaration is not a guarantee.

Has com.citysignalai/citysignal been security tested?

Partly. 4 of the 15 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security verdict is published before verification.

What can com.citysignalai/citysignal do?

It lists 23 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search and create or change data. We did not call any tool, so this describes the text, not the behaviour.

Can com.citysignalai/citysignal change or delete data?

2 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

Active servers whose topic is also “data-and-databases” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: exercised
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: exercised

4 exercised11 not run (reason given)3 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 4 of the 15 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 4
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.exercised
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.exercised
Not run, with the reason · 11
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 3
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 1,176 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 23 tools, 4 resources, 0 prompts.
  4. 6,488 msFinished: 4 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
AI-classified · 2026-10-23
Pricing modelAI-classified
no value
The pages we read do not state how the product is priced.
Programming language
does not apply
no existing GitHub repository (server declares no repository link, so there is nothing to fetch)
Hosting type
registry · 2026-10-23
MCP capability
resources, tools
our test · 2026-10-23
Transport
streamable HTTP
registry · 2026-10-23
Required credentials
none declared
registry · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-10-23
Lifecycle status
registry · 2026-10-23
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
not stated
no readable GitHub owner to describe
Maintenance
does not apply
server declares no repository link, so there is nothing to fetch
Environment
the publisher's infrastructure
where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “com.citysignalai/citysignal: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/com.citysignalai/citysignal

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 1 of 2 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/com.citysignalai/citysignal)](https://protocolprobe.com/mcp/servers/com.citysignalai/citysignal)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology