MCP servers › tw.cityatlas › cityatlas

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

tw.cityatlas/cityatlas

Greater Hsinchu, Taiwan open data on a 125 m grid: crashes, buses, schools, flood. Read-only. — the publisher's description

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

Summary

tw.cityatlas/cityatlas is a remote MCP server listed in the official MCP registry at version 0.3.1. On 2026-10-23 ProtocolProbe connected to it in read-only mode and read its inventory: 10 tools, 1 resource 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

Key facts

Runs: remote (hosted by the publisher)
Transport: streamable HTTP
Sign-in: none needed to open a session
Tools: 10
Described as changing data: 0 of 10 toolsAI-classified
Mainly works on: nothing outside itself: it only answers questionsAI-classified
Topic: data-and-databasesAI-classified
Last tested: 2026-10-23

Add to your client

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: 0.3.1, published 2026-10-14 (registry, as of the 2026-10-23 snapshot)
First listed version: 2026-10-14 (earliest version still in the registry; older removed versions would be earlier)
Registry data: snapshot 2026-10-23
Package and repository: checked 2026-10-23
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 0.3.1 (published 2026-10-14).

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

10tools

1resources

0prompts

What it mainly works on, as our AI model read its tool descriptions: nothing outside itself: it only answers questions.

None of its 10 tools are described as changing anything.

search_catalogon 88 other serversreads or searches
“用關鍵字找城市圖譜的資料:11 大類 82 項資料,細到 161 條指標(141 條格網:事故、公車、人行道、淹水、樹…;20 條里 / 鄉鎮 / 縣市:里人口、長者與兒童、里所得…),加上 47 屆選舉與公投(投票率、得票率);公開版少 Google 街景判讀的 2 項 4 條,實際查得到 80 項、157 條:回代號、名稱、單位、年份、出處機關、是不是推估、涵蓋幾區。Search the i…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
- querystringrequired“關鍵字,例:「事故行人」「公車」「淹水」;空白分開的字要全部對上”
- limitinteger“最多幾條,預設 12”
describe_metricon 1 other serverreads or searches
“一條資料的完整出處(機關、資料集、網址、取得日、檔案、對帳)、涵蓋哪些鄉鎮、統計、以及「可能在講別的事」的但書。Full provenance and caveats of one indicator.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
- metricstringrequired“資料代號或名稱,例:crash_ped4 或「行人事故」”
rankon 4 other serversreads or searches
“某條資料在里或鄉鎮排前幾名(跟網站 07 同一套算法:先加總再除、人少的地方往平均拉)。可換算每千居民 / 每公里道路 / 路 + 人 + 店(只有事故)/ 任何能當分母的代號;可只看某個鄉鎮、可加篩條件。只回前 N 名。里層資料(長者占比、里所得、選舉投票率…)一個里一個數,不能換算、單位只能是里(人數可加到鄉鎮)。沒編里的範圍不進排名。Rank neighbourhoods or distr…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
8 inputs, 1 required
- metricstringrequired“資料代號或名稱,例:crash_ped4 或「行人事故」”
- unitstring“單位:里(預設,neighbourhood)或鄉鎮(district)”
- perstring“換算:不除(預設)/ 每千居民 / 每公里道路 / 路 + 人 + 店 / 分母的資料代號”
- townstring“只看一個鄉鎮,例:竹北、東區”
- filtersarray“篩條件:里 / 鄉鎮的值要符合,例:[{metric:'residents',op:'>',value:100}]”
- descendingboolean“由高到低,預設 true”
- topinteger“前幾名,預設 10”
- shrinkboolean“有換算時,人少的地方往平均拉;預設 true(同網站),false = 看原始的率”
lookup_placeon 1 other serverreads or searches
“給地址(例:竹北市光明六路 10 號)、里名(例:竹北市東平里)或鄉鎮名 → 那裡各項數字,以及在大新竹排第幾;查里名時另附里人口、所得、65 歲以上與 14 歲以下。地址只定位到 125 公尺的格(用我們自己的門牌檔比對,不送外部服務、不記錄)。Numbers for an address, neighbourhood or district.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
- placestringrequired“地址、里名或鄉鎮名”
- metricsarray“要看哪幾條(代號或名稱);不給就看常用的 10 條”
need_rankingreads or searches
“哪裡最多人被公車耽誤(被耽誤的人·分鐘、工作地、學校、公設的百分位加權);權重可帶,不帶用預設 60/20/10/10。Where the most people lose time on public transport compared with driving.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
4 inputs
- unitstring“單位:里(預設,neighbourhood)或鄉鎮(district)”
- weightsobject“權重;不帶 = 60 / 20 / 10 / 10”
- townstring“只看一個鄉鎮,例:竹北、東區”
- topinteger“前幾名,預設 10”
overlay_metricsreads or searches
“兩條資料疊起來看:A(可換算)與 B 各切三等分成九宮格,回各格有幾個里 / 鄉鎮,並列出「兩樣都高」的。例:事故(每千居民)高、人行道少的里。Which places are high on two indicators at once.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
7 inputs, 2 required
- metric_astringrequired“資料 A(代號或名稱)”
- metric_bstringrequired“資料 B(代號或名稱)”
- perstring“A 的換算:不除(預設)/ 每千居民 / 每公里道路 / 路 + 人 + 店”
- unitstring“單位:里(預設,neighbourhood)或鄉鎮(district)”
- townstring“只看一個鄉鎮,例:竹北、東區”
- topinteger“前幾名,預設 10”
- shrinkboolean“有換算時,人少的地方往平均拉;預設 true(同網站),false = 看原始的率”
compare_groupson 1 other serverreads or searches
“有 B 的格 vs 沒有 B 的格,A 差多少 —— 在居民 × 道路長度切成的 25 層裡各比一次(避免被市中心拉著走)。只描述,不做因果。Compare cells with vs without B, within strata of residents and road length.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 2 required
- metric_astringrequired“要比的東西 A(件數 / 長度這類能加總的),例:行人事故”
- has_bstringrequired“分組的依據 B:格裡有沒有,例:人行道、公車站”
- perstring“A 的換算:不除(預設)/ 每千居民 / 每公里道路”
filter_cellsreads or searches
“找出同時符合最多四個條件的 125 公尺格,回符合幾格、住了多少人,並照里 / 鄉鎮加總。例:離公車站超過 500 公尺、又住超過 100 人。Find grid cells that meet up to four conditions.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
4 inputs, 1 required
- conditionsarrayrequired“每一格都要同時符合,例:[{metric:'stop_dist_m',op:'>',value:500}]”
- unitstring“單位:里(預設,neighbourhood)或鄉鎮(district)”
- townstring“只看一個鄉鎮,例:竹北、東區”
- topinteger“前幾名,預設 10”
compare_changereads or searches
“兩個年份比,哪些里增加最多、減少最多(跟網站 07「看變化」同一套):里人口(97–114 年底,戶籍;97–106 只有新竹縣市、竹南、頭份,新設里設立前是估計、不拿來比)、事故場數(111–114)、里所得中位數(111→112)、投票率(總統 / 立委不分區政黨票 / 立委區域 / 縣市長,年份照選舉目錄)。門檻自己填(增加幾人 / 件 / 萬元 / 個百分點以上才算增加很多);里界調整過…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
6 inputs, 1 required
- topicstringrequired“題目:population 里人口 / crash 事故 / income 里所得中位數 / turnout_president 總統投票率 / turnout_party_list 不分區政黨票投票率 / turnout_legislator 立委(區域)投票率 / turnout_mayor 縣市長投票率”
- fromstring“起始年份,例:97 或 107(人口)、111(事故)、2020(投票率,選舉年);不給 = 預設(投票率是最近兩屆)”
- tostring“結束年份;不給 = 預設最後一年”
- thresholdnumber“門檻:增加(或減少)幾人 / 件 / 萬元 / 個百分點以上才算「很多」;不給或給 0 = 預設(人口 500、事故里 5 鄉鎮 20、所得 5、投票率 3)”
- unitstring“單位:里(預設)或鄉鎮;只有事故兩種都可以,其他只比里”
- topinteger“前幾名,預設 10”
show_mapon 2 other serversreads or searches
“把一條資料(或「需要度」)畫成里 / 鄉鎮的五級地圖,在對話裡直接顯示,可拖曳縮放、滑過看數字;換算同「排名」。畫不出來的 AI 會拿到一個能點開的網址(請轉給使用者)。Draw an indicator as an interactive choropleth map of neighbourhoods; chats that cannot render it get a link that …”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
5 inputs, 1 required
- metricstringrequired“資料代號、名稱,或「需要度」”
- perstring“換算:不除(預設)/ 每千居民 / 每公里道路 / 路 + 人 + 店 / 分母的資料代號”
- townstring“地圖先對準這個鄉鎮(其他鄉鎮照樣畫)”
- unitstring“單位:里(預設,neighbourhood)或鄉鎮(district)”
- shrinkboolean“有換算時,人少的地方往平均拉;預設 true(同網站),false = 看原始的率”

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 10 tools
Says what it returns: 100% of 10 tools
States limits, defaults or errors: 20% of 5 tools
Says when to use it: 0% of 9 tools
Items covered per tool: 2.7 of 4 on average

Counted from the listing

Parameters with a description: 100% of 42
Tools with a description: 100% of 10
Typical description length: 204 characters

The tool set

Counted from the listing

Tools: 10
Size of the list: about 2,354 tokens for an agent to load (characters ÷ 4)
Naming: 9 of 10 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 10 of 10 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://mcp.cityatlas.tw/mcp

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "cityatlas": {
      "url": "https://mcp.cityatlas.tw/mcp"
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "cityatlas": {
      "type": "http",
      "url": "https://mcp.cityatlas.tw/mcp"
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"cityatlas","type":"http","url":"https://mcp.cityatlas.tw/mcp"}'

Claude Code

claude mcp add --transport http cityatlas https://mcp.cityatlas.tw/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://mcp.cityatlas.tw/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 says	We found	Result	Source · date
Remote endpoint mcp.cityatlas.tw/mcp	Session opened	matches	our test · 2026-10-23
No credential declared as required	Opened a session without any credential	matches	our 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-23. 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 tw.cityatlas/cityatlas

Answered from the data above

Does tw.cityatlas/cityatlas 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 tw.cityatlas/cityatlas been security tested?

Partly. 3 of the 14 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security verdict is published before verification.

What can tw.cityatlas/cityatlas do?

It lists 10 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. We did not call any tool, so this describes the text, not the behaviour.

Can tw.cityatlas/cityatlas change or delete data?

None of its 10 tools is described as changing anything (our AI model's reading of the descriptions; nobody checked it by hand). We did not call any tool.

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

io.github.t8y2/dbxalso has tools that reads or searchescompare with this one
agency.ottobot/contractor-license-changesContractor Licence Changesalso has tools that reads or searchescompare with this one
agency.ottobot/licensed-house-paintersLicensed House Paintersalso has tools that reads or searchescompare with this one
io.github.revolist/revogrid-mcpRevoGrid DataGrid MCPalso has tools that reads or searchescompare with this one
io.github.chrisryugj/korean-law-mcpKorean Law MCPalso has tools that reads or searchescompare with this one
io.github.timescale/pg-aiguidealso has tools that reads or searchescompare with this one

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

Not probed (we call no server's tools)

We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. 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

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: exercised
Fake assistant turns: not applicable
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not run · our policy
Consent handling: not testable from outside
Sign-in metadata: not applicable

3 exercised11 not run (reason given)4 not applicable

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

Exercised · 3

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
12Hidden content
audience-hidingChecks resources that hide content from the user.exercised

Not run, with the reason · 11

3Real execution
real-executionCalls 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-leakPlants 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
ssrfChecks 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-confirmationChecks 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-handlingSends 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
samplingChecks 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-dataChecks 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-boundaryChecks 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-channelChecks 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-redirectChecks 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-deputyChecks 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 · 4

13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
14Token passthrough
token-passthroughChecks 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-validationChecks 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
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses 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.

0 msStarted a read-only session with the server's remote endpoint
550 msConnected after 0 redirects. No credential was sent or needed.
Read the inventory: 10 tools, 1 resource, 0 prompts.
1,483 msFinished: 3 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

data-and-databases

AI-classified · 2026-10-23

Pricing modelAI-classified

no value

No value: the AI answer was held back because the quoted text did not clearly support it.

Programming language

does not apply

no existing GitHub repository (server declares no repository link, so there is nothing to fetch)

Hosting type

remote (hosted by the publisher)

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

active

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. “tw.cityatlas/cityatlas: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/tw.cityatlas/cityatlas

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](https://protocolprobe.com/api/v1/badge/tw.cityatlas/cityatlas)](https://protocolprobe.com/mcp/servers/tw.cityatlas/cityatlas)

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