_ registry / mcp http-sse · checked 12h ago

PSGC

https://psgc.godmode.ph

Registry code: 4f2078f91382909e

api record

A server that provides Philippine Standard Geographic Code (PSGC) data to LLMs. Built on Cloudflare Workers with KV storage. Public, read-only, no authentication required.

from a public catalogue that lists it, not from the operator

endpoint
https://psgc.godmode.ph/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is PSGC live?
Yes — it answered the hub's last check (checked 12h ago). It answered 100% of checks over the last 30 days.
Is PSGC free to use?
Yes — the hub reached it with no key and no payment.
What tools does PSGC have?
7 tools: query_by_population, list_by_type, lookup, search, get_hierarchy, list_children, batch_lookup.
Is PSGC safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
1,008ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 7 tools
7 never probed 0 of 7 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • query_by_population unknown 12h ago

    Query PSGC entities by population range. Returns entities sorted by population. Useful for finding the largest/smallest cities, municipalities, or provinces. Barangay queries require a parent_code to narrow scope.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "level"
      ],
      "properties": {
        "sort": {
          "enum": [
            "asc",
            "desc"
          ],
          "type": "string",
          "description": "Sort order by population (default: desc)"
        },
        "level": {
          "enum": [
            "Reg",
            "Prov",
            "Dist",
            "City",
            "Mun",
            "SubMun",
            "SGU",
            "Bgy"
          ],
          "type": "string",
          "description": "Geographic level to query"
        },
        "limit": {
          "type": "integer",
          "maximum": 100,
          "minimum": 1,
          "description": "Max results to return (default 10, max 100)"
        },
        "offset": {
          "type": "integer",
          "maximum": 9007199254740991,
          "minimum": 0,
          "description": "Number of records to skip (default 0)"
        },
        "parent_code": {
          "type": "string",
          "pattern": "^\\d{10}$",
          "maxLength": 10,
          "minLength": 10,
          "description": "Filter to entities within this parent (required for Bgy). Uses code prefix matching."
        },
        "max_population": {
          "type": "integer",
          "maximum": 9007199254740991,
          "minimum": 0,
          "description": "Maximum population (inclusive)"
        },
        "min_population": {
          "type": "integer",
          "maximum": 9007199254740991,
          "minimum": 0,
          "description": "Minimum population (inclusive)"
        }
      }
    }
    arguments 62 lines
  • list_by_type unknown 39h ago

    List all PSGC entities of a given geographic level. Barangay (Bgy) is excluded because there are 42,000+ barangays. To find barangays, use 'search' with a name query or 'list_children' on a city/municipality. Paginated (default limit: 50).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "level"
      ],
      "properties": {
        "level": {
          "enum": [
            "Reg",
            "Prov",
            "Dist",
            "City",
            "Mun",
            "SubMun",
            "SGU"
          ],
          "type": "string",
          "description": "Geographic level: Reg (region), Prov (province), Dist (district), City, Mun (municipality), SubMun (sub-municipality), SGU (special geographic unit)"
        },
        "limit": {
          "type": "integer",
          "maximum": 200,
          "minimum": 1,
          "description": "Max records to return (default 50, max 200)"
        },
        "offset": {
          "type": "integer",
          "maximum": 9007199254740991,
          "minimum": 0,
          "description": "Number of records to skip (default 0)"
        }
      }
    }
    arguments 34 lines
  • lookup unknown 12h ago

    Look up a Philippine geographic entity by its 10-digit PSGC code. Returns the full entity record including name, level, parent, population, and classification data.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "code"
      ],
      "properties": {
        "code": {
          "type": "string",
          "pattern": "^\\d{10}$",
          "maxLength": 10,
          "minLength": 10,
          "description": "10-digit PSGC code"
        }
      }
    }
    arguments 16 lines
  • search unknown never probed

    Search Philippine geographic entities by name. Supports partial matching. Use the level filter to narrow results (e.g. only cities, only provinces). For barangay searches, include the parent city/municipality name to get better results.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "query"
      ],
      "properties": {
        "level": {
          "enum": [
            "Reg",
            "Prov",
            "Dist",
            "City",
            "Mun",
            "SubMun",
            "SGU",
            "Bgy"
          ],
          "type": "string",
          "description": "Filter by geographic level"
        },
        "limit": {
          "type": "integer",
          "maximum": 50,
          "minimum": 1,
          "description": "Max results (default 10, max 50)"
        },
        "query": {
          "type": "string",
          "minLength": 1,
          "description": "Search query (place name or partial name)"
        },
        "strict": {
          "type": "boolean",
          "description": "Exact name match only (no partial/substring matching)"
        }
      }
    }
    arguments 38 lines
  • get_hierarchy unknown 39h ago

    Get the full administrative hierarchy for a PSGC entity. Returns the chain from the entity up through its parent city/municipality, province, and region.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "code"
      ],
      "properties": {
        "code": {
          "type": "string",
          "pattern": "^\\d{10}$",
          "maxLength": 10,
          "minLength": 10,
          "description": "10-digit PSGC code"
        }
      }
    }
    arguments 16 lines
  • list_children unknown 12h ago

    List the direct children of a PSGC entity. For a region, returns provinces/districts. For a province, returns cities/municipalities. For a city/municipality, returns barangays. Optionally filter by level. Paginated (default limit: 50).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "code"
      ],
      "properties": {
        "code": {
          "type": "string",
          "pattern": "^\\d{10}$",
          "maxLength": 10,
          "minLength": 10,
          "description": "10-digit PSGC code of the parent entity"
        },
        "level": {
          "enum": [
            "Reg",
            "Prov",
            "Dist",
            "City",
            "Mun",
            "SubMun",
            "SGU",
            "Bgy"
          ],
          "type": "string",
          "description": "Filter children by geographic level"
        },
        "limit": {
          "type": "integer",
          "maximum": 200,
          "minimum": 1,
          "description": "Max records to return (default 50, max 200)"
        },
        "offset": {
          "type": "integer",
          "maximum": 9007199254740991,
          "minimum": 0,
          "description": "Number of records to skip (default 0)"
        }
      }
    }
    arguments 42 lines
  • batch_lookup unknown 39h ago

    Look up multiple PSGC entities in one call. Pass an array of 10-digit codes (max 50). Returns results in the same order as input, with null for codes not found.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "codes"
      ],
      "properties": {
        "codes": {
          "type": "array",
          "items": {
            "type": "string",
            "pattern": "^\\d{10}$",
            "maxLength": 10,
            "minLength": 10
          },
          "maxItems": 50,
          "minItems": 1,
          "description": "Array of 10-digit PSGC codes (1-50)"
        }
      }
    }
    arguments 21 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 4f2078f91382909e.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/4f2078f91382909e/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/4f2078f91382909e/badge.svg)](https://brick.blue/agent/4f2078f91382909e?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.