Georgia Heritage
NPM · @PIPEWORX/MCP-GEORGIA-HERITAGE · 2 COMPONENTS
Georgia (the country) — National Register of Immovable Cultural Heritage.
Available components
Last scanned (3 hours ago)
Scores higher than 72% of npm servers
Category Education and Research
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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-georgia-heritage). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1254 tokens (~250/item across 5 items; 5 tools + 0 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 Management23
- Stability observed for 7 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 0
- Package version: 0.2.0 → 0.2.1 functional
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 79
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-georgia-heritage@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-georgia-heritage |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-georgia-heritage/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3637323999 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:cb9d8f9957f51c63c7b14bf50ef4d6a85d9a17ba79c6640b170142b416da710c32090181a62bab5dd698bfb777b0c5c1dd26fa8c3bd3da883833edbc2 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
georgia_heritage_facets ~188
List the distinct values, with record counts, that the Georgian (country) heritage register actually uses for a field — region, municipality, settlement, category, status, classification, physical_state, current_function, world_category or period. This is the discovery step for a register written entirely in Georgian script: read the exact stored value here, then pass it to georgia_heritage_search.
| Name | Type | Req | Description |
|---|---|---|---|
| field | string | yes | One of: region, municipality, settlement, category, status, classification, physical_state, current_function, world_category, period. |
| limit | number | – | Max distinct values, 1-500 (default 50), most frequent first. |
| municipality | string | – | Optional: restrict the facet to one municipality (Georgian or English). |
| region | string | – | Optional: restrict the facet to one region (Georgian or English). |
No output schema declared.
No examples provided.
georgia_heritage_museums ~122
Museums registered by the National Agency for Cultural Heritage Preservation of Georgia (the country): name, region, municipality, address, coordinates, and the visitor contact details, opening hours and ticket price the agency publishes for each.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max museums, 1-100 (default 50). |
| municipality | string | – | Municipality, Georgian or English. |
| query | string | – | Free text over museum name and address (Georgian, or English where mapped). |
| region | string | – | Region, Georgian or English. |
No output schema declared.
No examples provided.
georgia_heritage_nearby ~155
Cultural-heritage monuments near a point in Georgia (the country), by latitude/longitude and radius. Returns each object with its straight-line distance in metres from the register's recorded point, nearest first — for "what heritage is around this village / trailhead / development site".
| Name | Type | Req | Description |
|---|---|---|---|
| latitude | number | yes | WGS84 latitude, e.g. 41.8458 (Mtskheta). |
| limit | number | – | Max monuments, 1-200 (default 25). |
| longitude | number | yes | WGS84 longitude, e.g. 44.7194. |
| radius_m | number | – | Search radius in metres, 50-50000 (default 2000). |
No output schema declared.
No examples provided.
georgia_heritage_object ~155
Full register record for one Georgian (country) cultural-heritage object, by its registry number (reg_num / RegNum) or its stable ImmovableObjectID. Returns the description, dating, initial and current function, physical state, the listing decree number and date, coordinates, photo URL, and how many physical and visual protection zones the agency has drawn around it.
| Name | Type | Req | Description |
|---|---|---|---|
| object_id | number | – | ImmovableObjectID — the stable upstream identifier, present on every record. Prefer this for anything you store. |
| reg_num | string | – | Registry number as printed in the register, e.g. "4". RegNum is null for objects recorded but not yet numbered — use object_id for those. |
No output schema declared.
No examples provided.
georgia_heritage_search ~576
Search the National Register of Immovable Cultural Heritage of Georgia — the country in the Caucasus (საქართველო), NOT the US state. 20,706 monuments and heritage objects (churches, monasteries, fortresses, Svan towers, archaeological sites, listed houses and bridges) published by the National Agency for Cultural Heritage Preservation of Georgia. Filter by free text, region, municipality, settlement, category, listing status, classification or physical state. Returns the true total (not just the page), the registry number (RegNum), the stable ImmovableObjectID, WGS84 coordinates, the listing decree number and date, and a source_url plus portal_url per record. The register is Georgian-script only; common English terms and place names ("church", "Tbilisi", "Svetitskhoveli") are translated automatically and the Georgian terms actually searched come back in query_terms.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | CategoryName value, e.g. "ეროვნული" (national significance). Use georgia_heritage_facets to list them. |
| classification | string | – | Classification value, e.g. "არქეოლოგიური" (archaeological), "არქიტექტურის" (architectural). |
| limit | number | – | Records per page, 1-200 (default 25). |
| listed_only | boolean | – | Only objects that carry monument status (excludes the ~10,800 recorded objects with no listed status). |
| municipality | string | – | Municipality, Georgian or English (e.g. "Mtskheta", "მცხეთა"). |
| offset | number | – | Pagination offset into the full result set (default 0). |
| period | string | – | Substring of the Period field, e.g. "მე-19 ს." for the 19th century. |
| physical_state | string | – | PhysicalState value, e.g. "დანგრეული" (ruined), "კარგი" (good). |
| query | string | – | Free text over object name, settlement, address and description. Georgian script is used verbatim; English is translated where known (e.g. "monastery" → მონასტერი). |
| region | string | – | Region, Georgian or English (e.g. "Kakheti", "Samtskhe-Javakheti", "კახეთი"). |
| settlement | string | – | Settlement / village name. |
| status | string | – | StatusName value, e.g. "კულტურული მემკვიდრეობის ძეგლი" (listed monument). |
| with_coordinates_only | boolean | – | Only records that carry usable WGS84 coordinates. |
| world_significance_only | boolean | – | Only the 87 objects categorised as of world significance (მსოფლიო მნიშვნელობის). |
No output schema declared.
No examples provided.
How do I install the Georgia Heritage MCP server?
Georgia Heritage runs locally as an npm package, launched with npx -y @pipeworx/mcp-georgia-heritage. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-georgia-heritage
claude mcp add pipeworx-io-georgia-heritage -- npx -y @pipeworx/mcp-georgia-heritage
What is the Georgia Heritage MCP server?
Georgia Heritage is an MCP server listed in the public MCP registry as io.github.pipeworx-io/georgia-heritage. Georgia (the country), National Register of Immovable Cultural Heritage. This page covers its npm package (@pipeworx/mcp-georgia-heritage).
Is the Georgia Heritage MCP server safe to use?
Georgia Heritage scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Georgia Heritage MCP server expose?
Georgia Heritage exposes 5 tools: georgia_heritage_search, georgia_heritage_object, georgia_heritage_nearby, georgia_heritage_facets, georgia_heritage_museums. Their descriptions and schemas cost roughly 1,196 tokens of context every time the server is loaded.
Is the Georgia Heritage MCP server still maintained?
Georgia Heritage is still listed as active in the MCP registry. We last reached this channel on 5 November 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 Georgia Heritage MCP server under?
Georgia Heritage declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.