LTS MCP Server
Server Details
A Model Context Protocol server that provides Philippine License to Sell (LTS) verification data to LLMs. Built on Cloudflare Workers with Supabase.
Public, read-only, no authentication required. Data sourced from the Department of Human Settlements and Urban Development (DHSUD) License to Sell registry and cross-referenced with published real estate projects on REN.PH.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
12 toolslts_by_cityInspect
Rank cities by LTS count with province, region, law breakdown, active/expired split, and top developer per city. Groups by city+province to avoid merging same-name cities across provinces. Use for housing pressure indices, city-level market analysis, and identifying emerging development hotspots. Cross-reference with PSGC MCP for city classification and population. Capped at 25k rows; check truncated flag and narrow filters if true.
| Name | Required | Description | Default |
|---|---|---|---|
| law | No | Filter by housing law: BP220 (socialized/economic) or PD957 (open market) | |
| year | No | Filter by LTS issue year | |
| limit | No | Max cities to return, sorted by count desc | |
| region | No | Filter to a specific DHSUD region |
lts_by_developerInspect
Rank developers by LTS count with regional footprint, law breakdown, and active/expired split. Use for developer intelligence, competitive analysis, and identifying which developers dominate specific regions or housing segments. Capped at 25k rows; check truncated flag and narrow filters if true.
| Name | Required | Description | Default |
|---|---|---|---|
| law | No | Filter by housing law: BP220 (socialized/economic) or PD957 (open market) | |
| year | No | Filter by LTS issue year | |
| limit | No | Max developers to return, sorted by count desc | |
| region | No | Filter to a specific DHSUD region |
lts_by_lawInspect
Break down LTS records by housing law (BP220 socialized/economic vs PD957 open market). Shows regional distribution per law and year-over-year shift in BP220 share (when no year filter). Use for housing policy analysis and socialized housing supply tracking. Capped at 25k rows; check truncated flag and narrow filters if true.
| Name | Required | Description | Default |
|---|---|---|---|
| year | No | Filter by LTS issue year. Omit for YOY shift calculation | |
| region | No | Filter to a specific DHSUD region |
lts_by_regionInspect
Aggregate LTS records by DHSUD region. Returns count, market share, law breakdown (BP220/PD957), and active/expired split per region. Use for State of RE reports and regional housing market analysis. Cross-reference with PSGC MCP search for population data to compute per-capita density. Capped at 25k rows; check truncated flag and narrow filters if true.
| Name | Required | Description | Default |
|---|---|---|---|
| law | No | Filter by housing law: BP220 (socialized/economic) or PD957 (open market) | |
| year | No | Filter by LTS issue year | |
| status | No | Filter by derived LTS status: active (expiry >= today) or expired |
lts_checkInspect
Check if a specific LTS number exists in the system. Returns whether it exists in lts_records, in project_lts, or both. Includes full record details when found.
| Name | Required | Description | Default |
|---|---|---|---|
| ltsNumber | Yes | The LTS number to look up (e.g., 'LS 0001234') |
lts_expiry_riskInspect
Find LTS records expiring within a given number of days. Returns records sorted by urgency (soonest first) with days remaining, plus summary counts by region and developer. Use for compliance monitoring, renewal pipeline tracking, and risk assessment. Capped at 25k rows; check truncated flag and narrow filters if true.
| Name | Required | Description | Default |
|---|---|---|---|
| law | No | Filter by housing law: BP220 (socialized/economic) or PD957 (open market) | |
| days | No | Look-ahead window in days from today (default 90) | |
| region | No | Filter to a specific DHSUD region |
lts_filtersInspect
Get available filter values for LTS queries. Returns distinct regions and cities from the verification queue. Optionally filter cities by region. Use this before calling lts_queue or lts_search with region/city filters to get valid values.
| Name | Required | Description | Default |
|---|---|---|---|
| region | No | If provided, only return cities within this region |
lts_projectInspect
Get the complete LTS picture for a single project: all LTS records with computed fields (is_expired, days_until_expiry), summary counts, and the primary LTS number. Pass either a project UUID or a project name (fuzzy matched).
| Name | Required | Description | Default |
|---|---|---|---|
| projectId | No | Project UUID. Takes priority over projectName if both provided | |
| projectName | No | Project name or slug for fuzzy lookup. Use when you don't have the UUID |
lts_recordsInspect
Browse LTS records from DHSUD with filters. Shows normalized records with confidence levels. Filter by confidence (high/medium), linked status (has project_id), region, or text search. Use expiringWithinDays to find records expiring soon.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results | |
| linked | No | true = linked to project, false = unlinked | |
| offset | No | Pagination offset | |
| region | No | Filter by region (use lts_filters to get valid values) | |
| search | No | Text search: project name, LTS number, or developer | |
| sortBy | No | Sort field | created_at |
| sortOrder | No | Sort direction | desc |
| confidence | No | Filter by data confidence level | |
| expiringWithinDays | No | Show records with expiry date within N days from today |
lts_searchInspect
Search across DHSUD LTS records and published projects by name, LTS number, developer, or city. Returns matches from both lts_records and published projects. Universal entry point for LTS data.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results per category | |
| query | Yes | Search term: project name, LTS number, developer name, or city | |
| offset | No | Pagination offset |
lts_statsInspect
Get system-wide LTS statistics. Returns two sections: (1) lts_records stats (total, by confidence, linked/unlinked, active/expired, unique developers/cities), and (2) project LTS stats (total records, verified, expired, expiring within 30 days, projects with LTS).
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
lts_trendsInspect
Show LTS issuance trends over time with annual or quarterly granularity. Returns period counts with law breakdown, peak period, and year-over-year growth percentage. Use for housing supply pipeline analysis and market timing. Capped at 25k rows; check truncated flag and narrow filters if true.
| Name | Required | Description | Default |
|---|---|---|---|
| law | No | Filter by housing law: BP220 (socialized/economic) or PD957 (open market) | |
| region | No | Filter to a specific DHSUD region | |
| to_year | No | End year (inclusive) | |
| from_year | No | Start year (inclusive) | |
| granularity | No | Time bucket granularity | annual |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!