Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Descripción del creador (original en inglés)
PH civic data as MCP tools: the full PSA OpenSTAT catalog, hazards, procurement. 41 tools.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
PAGASA_API_TOKENLos valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json
{
"mcpServers": {
"ph-civic-data": {
"command": "uvx",
"args": [
"ph-civic-data-mcp"
],
"env": {
"PAGASA_API_TOKEN": "your-value"
}
}
}
}Ejecuta esto en tu terminal
claude mcp add ph-civic-data --env PAGASA_API_TOKEN=your-value -- uvx ph-civic-data-mcpCompleta los valores vacíos antes de ejecutarlo.
Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"ph-civic-data": {
"command": "uvx",
"args": [
"ph-civic-data-mcp"
],
"env": {
"PAGASA_API_TOKEN": "your-value"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"ph-civic-data": {
"type": "stdio",
"command": "uvx",
"args": [
"ph-civic-data-mcp"
],
"env": {
"PAGASA_API_TOKEN": "your-value"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 7 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub xmpuspus, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
Debes completar: PAGASA_API_TOKEN
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (0.8.0) llegó al registro hace 2 meses.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Python (uv) en tu computadora.
En la misma categoría: Spec Driven Development, Remote Desktop Commander, Date Math
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
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.
Exact date/time math for agents: business days, holidays, time zones, cron, RRULE, SLA. x402 paid.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
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 |
Solo se muestra el principio; lee el resto en el repo