Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
PH civic data as MCP tools: the full PSA OpenSTAT catalog, hazards, procurement. 41 tools.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
PAGASA_API_TOKEN标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"ph-civic-data": {
"command": "uvx",
"args": [
"ph-civic-data-mcp"
],
"env": {
"PAGASA_API_TOKEN": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add ph-civic-data --env PAGASA_API_TOKEN=your-value -- uvx ph-civic-data-mcp运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"ph-civic-data": {
"command": "uvx",
"args": [
"ph-civic-data-mcp"
],
"env": {
"PAGASA_API_TOKEN": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"ph-civic-data": {
"type": "stdio",
"command": "uvx",
"args": [
"ph-civic-data-mcp"
],
"env": {
"PAGASA_API_TOKEN": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日
注册名称已通过 GitHub 账户 xmpuspus 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:PAGASA_API_TOKEN
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.8.0)于2个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Tethered Trust
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Fit, compatibility and recall checks for AI agents before they buy: verdicts, evidence, receipts.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Philippine civic data as agent-callable tools. The full PSA OpenSTAT
statistical catalog, PSGC location codes, infra-spending accountability,
earthquakes, weather, typhoons, procurement, poverty, solar radiation, air
quality, satellite vegetation, and macro indicators. Population figures
reach barangay level. 41 tools, no API keys.
Philippine civic-data portals publish open data in different shapes: scraped HTML tables, PXWeb JSON, and undocumented APIs. Nothing ties them together for an agent to use. This server does, over stdio, with zero hosting cost and no API key needed. It answers questions such as how many people live in a barangay, whether a place sits near an active fault or volcano, what a city spent on flood control, and how one place compares against another.
All data comes from public records. Heuristic indicators are statistical only. A specific allegation needs independent investigation and a second source.
Every client below runs the same package, uvx ph-civic-data-mcp, over stdio.
Claude Desktop. Add this to claude_desktop_config.json, which sits at ~/Library/Application Support/Claude/claude_desktop_config.json on macOS:
{
"mcpServers": { "ph-civic-data": { "command": "uvx", "args": ["ph-civic-data-mcp"] } } }
Claude Code.
claude mcp add ph-civic-data -- uvx ph-civic-data-mcp
Codex. Confirmed live on 2026-09-03.
codex mcp add ph-civic-data -- uvx ph-civic-data-mcp
Cursor. Add this to mcp.json:
{
"mcpServers": { "ph-civic-data": { "command": "uvx", "args": ["ph-civic-data-mcp"] } } }
VS Code. Add this to .vscode/mcp.json:
{
"servers": { "ph-civic-data": { "type": "stdio", "command": "uvx", "args": ["ph-civic-data-mcp"] } } }
Docker. Build once, then run with -i for stdio:
docker build -t ph-civic-data-mcp .
The image runs as a non-root user and ships a healthcheck.
That recording is vhs docs/demo_setup.tape. It spawns Claude Code with --mcp-config pointed at this server, and Claude fans out to get_weather_forecast and get_population_stats, then correlates them. The temperatures and the population are what the live sources returned while it recorded. The population turn answers from the 2024 Census of Population (NCR: 14,001,751 as of 1 July 2024).
ph-civic-data-mcp exposes 41 tools across 19 public sources. Start with get_area_profile for any place-based question. It resolves the name to a PSGC code once, then composes demographics, economy, procurement, hazards, and the 3-day outlook in a single turn, with infra notices already normalized per 100,000 residents.
get_area_profileresolve_ph_locationget_population_statsget_poverty_statsassess_area_risklist_admin_unitsget_location_hierarchycompare_areascompare_areascompare_areasget_latest_earthquakesget_earthquake_bulletinget_volcano_statusget_active_typhoonsget_usgs_earthquakes_phget_flood_forecastget_historical_typhoons_phsearch_procurementsearch_infra_projectssummarize_infra_spendingget_procurement_summaryflag_infra_anomaliesget_infra_projectsearch_psa_catalogbrowse_psa_catalogdescribe_psa_datasetquery_psa_datasetget_inflation_statsget_labor_statsget_health_indicatorssearch_psic_codesquery_psa_dataset needs an explicit value code for every dimension, refuses "all" and "*", and caps a query at 1000 cells. PSA answers a full-cube request with an HTTP 403, so describe_psa_dataset first is the only way in.
get_weather_forecastget_weather_alertsget_solar_and_climateget_air_qualityget_vegetation_indexlist_pagasa_advisory_filesget_world_bank_indicatorbrowse_election_resultsget_election_returnThe archive froze on 2025-05-16, so these two read a fixed public record. The tools retrieve and never interpret.
get_official_gazette_feedsearch_hdx_datasetsEvery HDX dataset carries its own license. Read license_id before reuse.
Three MCP prompts pre-write the multi-step work, so a client can offer them as slash commands or starting points.
area_briefing(location) composes a full place briefing.infra_accountability_scan(area) walks the procurement review path.psa_data_explorer(topic) drives the search, describe, query loop.One tool answers questions about the server itself. get_data_freshness reports the running version, the tool count, every source with its cache window and license, per-host health, and cache ages.
Two MCP resources carry context a client can read without a tool call.
data://ph-civic/source-catalog is the source, freshness, and license table.data://ph-civic/civic-framing is the language rule for accountability output.Full signatures, arguments, and limits for all 41 tools: [docs/tool-reference.md](docs/tool-reference.md).
get_area_profile("Tacloban") returns the resolved identity, then reports Tacloban's own population next to the national figure, not the region's.
{
"resolved": { "name": "City of Tacloban", "psgc_code": "083747000", "level": "city" }, "demographics": { "population": 259353, "population_year": 2024, "population_census": "2024 Census of Population", "population_reference": "PSA 2024 Census of Population, reference date 2024-07-01.", "population_geography_level": "highly_urbanized_city", "population_psgc_code": "0831600000", "poverty_incidence_pct": 20.6, "poverty_reference_year": 2023 }, "national_reference": { "population": 112729484, "population_year": 2024, "poverty_incidence_pct": 10.9, "poverty_year": 2023, "population_share_pct": 0.23, "poverty_gap_pct_points": 9.7 }, "blocks": { "resolve": "success", "population": "success", "poverty": "success", "hazard": "success", "weather": "success", "national_population": "success", "national_poverty": "success", "infra": "success" }, "upstream_error": false, "caveats": [] }
Captured live on 2026-09-03. Tacloban's own population, 259,353, replaces the Region VIII figure of about 4.6 million that an earlier version reported. Every demographic field names its own census, reference date, and geography level, so an agent never has to guess which population a number belongs to.
A list tool returns a real list on success. On upstream failure it returns an envelope instead:
{ "results": [], "upstream_error": true, "caveats": ["ConnectError: ..."] }
Read that as "the source was unreachable," never as "no earthquakes" or "no notices." Failures never enter a cache, so a retry is meaningful, and a caveats entry carries the real error rather than an exception class name.
Every single-value tool sets data_status to one of five values:
data_status | Meaning |
|---|---|
success | The source returned a value, with its provenance. |
empty | The source answered but has no row for this request. |
unavailable | The source failed to respond, or sent an unreadable body. |
indeterminate | The source answered, but the server cannot trust the result. |
invalid_request | The caller sent a bad argument. Fix the argument named in caveats. |
upstream_error and validation_error derive from data_status, so a caller can branch on either field. get_area_profile reports one status per block in blocks and folds every failed block into caveats, so a null figure never sits beside an empty caveats list.
Every response carries source and data_retrieved_at.
The table below comes straight from SOURCE_CATALOG in server.py, through scripts/render_source_matrix.py, so it cannot drift from what the server actually reports.
| Source | What it gives | Freshness |
只显示了开头部分;其余内容请在仓库中阅读