Ph Civic Data MCP Server

ph-civic-data-mcp PyPI v0.8.0

Published by xmpuspus — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for Philippine civic data: PSGC, infra spending accountability, PSA economy (inflation, labor, poverty, population), one-call area profiles, earthquakes, weather, typhoons, procurement, solar/climate, air quality, vegetation

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 41

Each tool and what it can reach — statically extracted from the published source.

  • browse_election_resultsingests untrusted input
  • browse_psa_catalogingests untrusted input
  • describe_psa_datasetingests untrusted input
  • get_air_qualityingests untrusted input
  • get_data_freshnessingests untrusted input
  • get_earthquake_bulletiningests untrusted input
  • get_election_returningests untrusted input
  • get_flood_forecastingests untrusted input
  • get_health_indicatorsingests untrusted input
  • get_infra_projectingests untrusted input
Show 31 more tools ↓
  • get_official_gazette_feedingests untrusted input
  • get_volcano_statusingests untrusted input
  • get_weather_forecastingests untrusted input
  • get_world_bank_indicatoringests untrusted input
  • list_pagasa_advisory_filesingests untrusted input
  • assess_area_riskno sensitive capability
  • compare_areasno sensitive capability
  • flag_infra_anomaliesno sensitive capability
  • get_active_typhoonsno sensitive capability
  • get_area_profileno sensitive capability
  • get_historical_typhoons_phno sensitive capability
  • get_inflation_statsno sensitive capability
  • get_labor_statsno sensitive capability
  • get_latest_earthquakesno sensitive capability
  • get_location_hierarchyno sensitive capability
  • get_population_statsno sensitive capability
  • get_poverty_statsno sensitive capability
  • get_procurement_summaryno sensitive capability
  • get_solar_and_climateno sensitive capability
  • get_usgs_earthquakes_phno sensitive capability
  • get_vegetation_indexno sensitive capability
  • get_weather_alertsno sensitive capability
  • list_admin_unitsno sensitive capability
  • query_psa_datasetno sensitive capability
  • resolve_ph_locationno sensitive capability
  • search_hdx_datasetsno sensitive capability
  • search_infra_projectsno sensitive capability
  • search_procurementno sensitive capability
  • search_psa_catalogno sensitive capability
  • search_psic_codesno sensitive capability
  • summarize_infra_spendingno sensitive capability

What this scan could not see

Versions 3

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.8.0 latest A 96/100 0 1.13.0 2026-09-04
v0.6.0 A 96/100 1 1.13.0 2026-08-25
v0.5.0 A 96/100 0 1.12.1 2026-07-27

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/ph-civic-data-mcp/badge.svg)](https://mcptrustchecker.com/registry/ph-civic-data-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/ph-civic-data-mcp"><img src="https://mcptrustchecker.com/registry/ph-civic-data-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/ph-civic-data-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan ph-civic-data-mcp --online --registry pypi

Use the free API → How scoring works

More in Data Science & ML