io.github.LizzleChen/local-dfw-mcp
NPM · LOCAL-DFW-MCP · SCANNED SEP 20
Your AI's DFW guide: events, appraisals, Dallas 311, crime, floods, schools, utilities, districts.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 63 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 5314 tokens (~332/item across 16 items; 14 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (64% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.LizzleChen/local-dfw-mcp server?
io.github.LizzleChen/local-dfw-mcp runs locally as an npm package, launched with npx -y local-dfw-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · local-dfw-mcp
claude mcp add lizzlechen-local-dfw-mcp -- npx -y local-dfw-mcp
{
"mcpServers": {
"lizzlechen-local-dfw-mcp": {
"command": "npx",
"args": [
"-y",
"local-dfw-mcp"
]
}
}
} {
"servers": {
"lizzlechen-local-dfw-mcp": {
"command": "npx",
"args": [
"-y",
"local-dfw-mcp"
]
}
}
} codex mcp add lizzlechen-local-dfw-mcp -- npx -y local-dfw-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"lizzlechen-local-dfw-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"local-dfw-mcp"
],
"enabled": true
}
}
} openclaw mcp add lizzlechen-local-dfw-mcp --command npx --arg -y --arg local-dfw-mcp
mcp_servers:
lizzlechen-local-dfw-mcp:
command: "npx"
args: ["-y", "local-dfw-mcp"] {
"McpServers": {
"lizzlechen-local-dfw-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"local-dfw-mcp"
]
}
}
} assistant mcp add lizzlechen-local-dfw-mcp -t stdio -c npx -a -y local-dfw-mcp
{
"mcpServers": {
"lizzlechen-local-dfw-mcp": {
"command": "npx",
"args": [
"-y",
"local-dfw-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −2
- Stability: pass → 0.83 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −3
- Stability: pass → 0.80 functional
- 9 Sept 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/local-dfw-mcp@0.2.4
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
about ~39
Show information about this MCP server: name, version, coverage, data sources, license, and provenance. Always available. (via local-dfw-mcp)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
dfw_311 ~266
City of Dallas only (v0.1). Search Dallas 311 service requests by address and/or type. Types use the city's official names -- potholes are "street repair"; also "illegal dumping", "animal loose", "parking", "noise". Returns request number, type, department, status, dates, and council district. Use for neighborhood quality-of-life research. Authoritative source: City of Dallas Open Data.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Street address, contains-match. Example: "1500 Marilla St". |
| city | string | – | Jurisdiction override. v0.1 covers "dallas" only; "auto" (default) resolves from the address. |
| cursor | string | – | Opaque pagination cursor from a previous call. |
| limit | integer | – | Max results (default 25). |
| service_type | string | – | Contains-match on the official type name, e.g. "street repair" (= potholes), "illegal dumping", "animal loose". |
| since_year | integer | – | Only requests created on/after this year. Defaults to 2 years back. |
| status | string | – | "open" (New/In Progress/Escalated/On Hold), "closed", or an exact status like "In Progress". |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | Number of results in this page. |
| nextCursor | string|null | – | Opaque pagination cursor for the next page; null if no more results. |
| offset | integer | – | Current page offset for pagination. |
| query | – | – | Echo of the input filters. |
| results | array | yes | Result rows. |
No examples provided.
dfw_appraisal ~245
Look up the county appraisal-district record for a DFW address (Texas statewide; DFW's 4 core counties verified): owner, appraised land / improvement / market value from the 2025 certified appraisal roll, year built, land use, acreage. Appraised value is NOT a tax bill. Not a consumer report — not for FCRA-regulated (tenant/employment) screening. Source: TxGIO StratMap (county appraisal data).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Full address. Example: "1500 Marilla St Dallas TX 75201". Either address or latitude+longitude required. Geocoding lands in the street right-of-way, so a single hit can occasionally be the NEIGHBOR's… |
| latitude | number | – | Latitude (WGS-84). Use with longitude to skip geocoding. Place the point on the building rooftop, not the street centerline — the parcel lookup is point-in-polygon. |
| longitude | number | – | Longitude (WGS-84, negative in Texas). Use with latitude to skip geocoding. |
No output schema declared.
No examples provided.
dfw_code_cases ~427
Fort Worth (default), McKinney (city="mckinney", v0.3), or Arlington (city="arlington", v0.3) -- Dallas's code-compliance publication stalled 2025-01-31 and is not wired (see project plan); do not claim Dallas coverage here. Search code-compliance (property maintenance / high grass / zoning / animal / solid waste, etc.) cases by address, complaint type, or status. Returns case ID, complaint type, status, created/updated/closed dates, and the assigned officer (Fort Worth/McKinney only). NOT a consumer report -- do not use for tenant, employment, or other FCRA-regulated screening. Sources: City of Fort Worth / McKinney / Arlington Open Data (ArcGIS).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Contains-match against the violation address (a single field for all three cities, e.g. "500 Main St" or just "Main St"). |
| city | string | – | Jurisdiction: "fortworth" (default), "mckinney" (v0.3), or "arlington" (v0.3) are wired; "dallas" is refused -- Dallas code-case publication stalled 2025-01-31, not covered (see project plan). |
| complaint_type | string | – | Free text, contains-match against the complaint/case type, e.g. "high grass", "property maintenance", "zoning", "animal", "solid waste". |
| cursor | string | – | Opaque pagination cursor from a previous call. |
| limit | integer | – | Max results (default 25). |
| since_date | string | – | ISO date (YYYY-MM-DD); only cases created/opened on/after it. Omit for the most recent cases regardless of date. |
| status | string | – | Free text, contains-match against the case status, e.g. "open", "closed". Fort Worth uses a clean Open/Closed enum; McKinney/Arlington status text may vary. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | Number of results in this page. |
| nextCursor | string|null | – | Opaque pagination cursor for the next page; null if no more results. |
| offset | integer | – | Current page offset for pagination. |
| query | – | – | Echo of the input filters. |
| results | array | yes | Result rows. |
No examples provided.
dfw_crime ~408
City of Dallas (default), Fort Worth (city="fortworth", v0.2), or Denton (city="denton", v0.3) -- no other city wired. Search police incidents by (block-level) address and/or offense type. Returns incident number, offense, date, premise (Dallas) or location type (Fort Worth) or agency (Denton), division/sector/beat (Dallas/Fort Worth), and status. Addresses are block-level (privacy-rounded upstream). NOT a consumer report — do not use for tenant, employment, or other FCRA-regulated screening. Sources: Dallas Police Department Open Data / City of Fort Worth Police Crime Data / City of Denton Police crime data (CKAN).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Block-level street address, contains-match. Example: "3400 Ladd St". |
| city | string | – | Jurisdiction: "dallas" (default) queries Dallas PD (Socrata); "fortworth" (v0.2) queries Fort Worth PD Crime Data (ArcGIS); "denton" (v0.3) queries Denton PD crime data (CKAN, 2019-11-06 -> present);… |
| cursor | string | – | Opaque pagination cursor from a previous call. |
| limit | integer | – | Max results (default 25). |
| offense | string | – | Free-text offense filter, e.g. "burglary", "theft", "assault". |
| since_date | string | – | ISO date (YYYY-MM-DD); only incidents on/after it. Defaults to 90 days ago. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | Number of results in this page. |
| nextCursor | string|null | – | Opaque pagination cursor for the next page; null if no more results. |
| offset | integer | – | Current page offset for pagination. |
| query | – | – | Echo of the input filters. |
| results | array | yes | Result rows. |
No examples provided.
dfw_district_lookup ~165
Given a DFW street address, returns the districts/jurisdictions it falls in: county (all 4 core counties), City of Dallas council district + council member (City of Dallas only), whether it is inside City of Dallas limits, and school district (ISD). Call this FIRST for an unfamiliar address: it tells you whether the City-of-Dallas-only tools (dfw_311, dfw_crime's default path) apply, and its ISD feeds dfw_tea_schools' district filter. Pipeline: U.S. Census geocoder → point-in-polygon against Dallas GIS and statewide Texas ArcGIS layers.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Full street address. Example: "1500 Marilla St Dallas TX 75201". |
No output schema declared.
No examples provided.
dfw_events ~280
Upcoming DFW events. Official city calendars (keyless): Dallas Parks & Rec ONLY (no citywide Dallas feed), Garland, Frisco, Mesquite, McKinney. Plus concerts/sports/theater metro-wide via Ticketmaster when DFW_TICKETMASTER_API_KEY is set. Filter by city, category, date range, free text. Other cities (Plano, Arlington, Fort Worth, Irving, ...) have no calendar feed -- say so rather than guessing.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | "city" = official city calendars only; "concert"/"sports"/"theater" = Ticketmaster only (needs key); "all" (default) merges both tiers. |
| city | string | – | City calendar to search; "all" (default) merges every covered city. "dallas" = Parks & Rec calendar only. |
| cursor | string | – | Opaque pagination cursor from a previous call. |
| date_from | string | – | Only events on/after this date (YYYY-MM-DD). Defaults to today for commercial events. |
| date_to | string | – | Only events on/before this date (YYYY-MM-DD). |
| limit | integer | – | Max results (default 25). |
| search | string | – | Free-text filter on title/description/venue. Example: "farmers market", "Mavericks". |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | Number of results in this page. |
| nextCursor | string|null | – | Opaque pagination cursor for the next page; null if no more results. |
| offset | integer | – | Current page offset for pagination. |
| query | – | – | Echo of the input filters. |
| results | array | yes | Result rows. |
No examples provided.
dfw_fema_flood ~213
Look up the FEMA flood zone for a DFW address. Returns the zone code (A, AE, X, V, VE, etc.), Special Flood Hazard Area (SFHA) status, base flood elevation, and a plain-English risk + insurance interpretation (Zone A/AE/V require federal flood insurance). Long-term zone mapping only -- for weather alerts happening now use dfw_nws_alerts; for the property's value/owner use dfw_appraisal. Source: FEMA National Flood Hazard Layer (NFHL). Geocodes via U.S. Census.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Full address. Example: "1500 Marilla St Dallas TX 75201". Either address or lat+long required. |
| latitude | number | – | Latitude (WGS-84). Use with longitude to skip geocoding — checks the flood zone at exactly this point. |
| longitude | number | – | Longitude (WGS-84, negative in Texas). Use with latitude to skip geocoding. |
No output schema declared.
No examples provided.
dfw_health ~159
Diagnostic. Pings every upstream data provider this MCP depends on (Dallas Open Data, data.texas.gov, FEMA NFHL, PUC CCN, Dallas GIS, TxGIO StratMap, Census, NWS, CivicPlus city calendars, Ticketmaster, Fort Worth traffic accidents, Dallas ROW permits, TxDOT AADT/Projects, Fort Worth permits / code violations / crime data, McKinney code cases / permits (ArcGIS), Denton crime data (CKAN), Arlington permits / code complaints / ROW closures (ArcGIS)) in parallel with a 3.5s timeout and reports per-source status, HTTP code, and latency. Use when many tools return errors to tell which provider is down vs which tool is broken.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| checks | array | yes | – |
| summary | object | yes | – |
No examples provided.
dfw_nws_alerts ~177
Active National Weather Service alerts (severe thunderstorm, tornado, flood, heat, freeze, fire weather) for a DFW location. Defaults to downtown Dallas when no address is supplied. Returns severity, urgency, headline, area, and expiration for each active alert covering the point. This is CURRENT alerts only -- for a property's long-term flood ZONE use dfw_fema_flood instead. Source: National Weather Service (api.weather.gov).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Street address to check (geocoded). Example: "1500 Marilla St Dallas TX". Defaults to downtown Dallas. |
| lat | number | – | Latitude (WGS-84). Use with lng to skip geocoding. |
| lng | number | – | Longitude (WGS-84). Use with lat to skip geocoding. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | Number of results in this page. |
| nextCursor | string|null | – | Opaque pagination cursor for the next page; null if no more results. |
| offset | integer | – | Current page offset for pagination. |
| query | – | – | Echo of the input filters. |
| results | array | yes | Result rows. |
No examples provided.
dfw_permits ~642
Fort Worth (default), McKinney (city="mckinney", v0.3), or Arlington (city="arlington", v0.3) -- Dallas building-permit feeds are stale/dead and not wired (see project plan); do not claim Dallas coverage here. Search building/development permits. Fort Worth addresses are componentized upstream -- match on `street` (+ optional `addr_no`), not a one-line address. McKinney's source has NO DATE FIELD, so `address` is REQUIRED for city="mckinney" and results are ordered by case number (not strictly chronological), not File_Date. Arlington's `address` IS a single string (like McKinney), issued permits only. Returns permit number/ID, type, status, dates or filed-YYYY-MM (McKinney), address, and owner/job value (Fort Worth only). Sources: City of Fort Worth / McKinney / Arlington Open Data (ArcGIS).
| Name | Type | Req | Description |
|---|---|---|---|
| addr_no | integer | – | Fort Worth only. House/building number (Addr_No), exact match. Combine with `street` to scope to one address. |
| address | string | – | McKinney (REQUIRED for city="mckinney" -- the McKinney source has no date field, so browsing/newest-first listing is not possible there) or Arlington (optional). Contains-match against the permit add… |
| city | string | – | Jurisdiction: "fortworth" (default), "mckinney" (v0.3), or "arlington" (v0.3) are wired; "dallas" is refused -- Dallas permit feeds are stale/dead, not covered (see project plan). |
| cursor | string | – | Opaque pagination cursor from a previous call. |
| limit | integer | – | Max results (default 25). |
| permit_type | string | – | Free text, contains-match against Permit_Type / Permit_SubType / Permit_Category (Fort Worth), Work Class (McKinney), or FOLDERTYPE/WORKDESC (Arlington), e.g. "electrical", "residential building", "r… |
| since_date | string | – | Fort Worth/Arlington. ISO date (YYYY-MM-DD); only permits filed/issued on/after it (File_Date / ISSUEDATE). Ignored (with a note) for city="mckinney", which has no date field. Omit for the most recen… |
| status | string | – | Free text, contains-match against Current_Status (Fort Worth), ENT_STATUS (McKinney), or STATUSDESC (Arlington), e.g. "issued", "finaled", "in review". |
| street | string | – | Fort Worth only. Street name only, contains-match against Street_Name (address is componentized -- do not include house number or suffix). Example: "Main", not "500 Main St". |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | Number of results in this page. |
| nextCursor | string|null | – | Opaque pagination cursor for the next page; null if no more results. |
| offset | integer | – | Current page offset for pagination. |
| query | – | – | Echo of the input filters. |
| results | array | yes | Result rows. |
No examples provided.
dfw_tea_schools ~255
Texas public schools + TEA A-F accountability ratings (latest published: 2022-2023). Search by campus name, district, or county (e.g. DALLAS, TARRANT, COLLIN, DENTON). Returns overall rating, sub-scores (Student Achievement, School Progress, Closing the Gaps), enrollment, and demographics. Does NOT map an address to its assigned schools — attendance zones are managed by individual ISDs. To find which ISD an address is in, call dfw_district_lookup first, then filter here by that district. Source: Texas Education Agency.
| Name | Type | Req | Description |
|---|---|---|---|
| campus | string | – | Campus name, contains-match. Example: "Booker T Washington", "Frisco HS". |
| county | string | – | County name. Example: "DALLAS", "TARRANT", "COLLIN", "DENTON". |
| district | string | – | District name, contains-match. Example: "Dallas ISD", "Frisco ISD", "Plano". |
| limit | integer | – | Max results (default 25). |
| rating | string | – | Filter by overall A-F rating. |
| school_type | string | – | Filter by campus level. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | Number of results in this page. |
| nextCursor | string|null | – | Opaque pagination cursor for the next page; null if no more results. |
| offset | integer | – | Current page offset for pagination. |
| query | – | – | Echo of the input filters. |
| results | array | yes | Result rows. |
No examples provided.
dfw_traffic ~366
DFW-area traffic: real-time incidents (Fort Worth only), street/lane closures from right-of-way permits (Dallas + Arlington, merged and labeled by city), TxDOT annual traffic counts (AADT) by county, and TxDOT highway construction projects by county. Counties: Dallas, Tarrant, Collin, Denton. Default kind=all merges live incidents+closures only (counts/projects need an explicit kind). Arlington closures are ordered approximately (permit-ID sequence, flagged in notes) -- its source publishes no per-record date.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | Scopes incidents (fortworth only) / closures (dallas or arlington). Omit with kind="closures" to merge both cities (each result is labeled with its `city`). With kind="all", narrows the merge to just… |
| county | string | – | Scopes counts/projects to one of the 4 core counties; omit to query all four. |
| cursor | string | – | Opaque pagination cursor from a previous call. |
| kind | string | – | "incidents" (Fort Worth), "closures" (Dallas + Arlington ROW permits, merged), "counts" (TxDOT AADT), "projects" (TxDOT construction), or "all" (default: merges incidents+closures only). |
| limit | integer | – | Max results (default 25). |
| search | string | – | Free text: matches street/cross-street/address for incidents, address/location for closures (Arlington also matches its ScopeOfWork/Segment free-text fields, which do not reliably carry an address),… |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | Number of results in this page. |
| nextCursor | string|null | – | Opaque pagination cursor for the next page; null if no more results. |
| offset | integer | – | Current page offset for pagination. |
| query | – | – | Echo of the input filters. |
| results | array | yes | Result rows. |
No examples provided.
dfw_utility_providers ~139
Find the WATER and SEWER (wastewater) utility obligated to serve a DFW address — the 'who turns on my water' question. DFW is a patchwork of cities, MUDs/WCIDs, water-supply corporations, and private utilities. Returns the certificated (CCN) provider for the exact point. Source: Texas PUC Certificate of Convenience and Necessity boundaries. Covers all of Texas. Does NOT start service — it tells you who to contact.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Street address in DFW. Example: "6801 Warren Pkwy, Frisco TX 75034". |
No output schema declared.
No examples provided.
What is the io.github.LizzleChen/local-dfw-mcp server?
io.github.LizzleChen/local-dfw-mcp is listed in the public MCP registry as io.github.LizzleChen/local-dfw-mcp. Your AI's DFW guide: events, appraisals, Dallas 311, crime, floods, schools, utilities, districts. This page covers its npm package (local-dfw-mcp).
Is the io.github.LizzleChen/local-dfw-mcp server safe to use?
io.github.LizzleChen/local-dfw-mcp scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.LizzleChen/local-dfw-mcp server expose?
io.github.LizzleChen/local-dfw-mcp exposes 14 tools: about, dfw_health, dfw_311, dfw_crime, dfw_permits, and 9 more. Their descriptions and schemas cost roughly 3,781 tokens of context every time the server is loaded.
Is the io.github.LizzleChen/local-dfw-mcp server still maintained?
io.github.LizzleChen/local-dfw-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.LizzleChen/local-dfw-mcp server under?
io.github.LizzleChen/local-dfw-mcp declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.