fgiscs-history-mcp
Related Servers
Alternatives to fgiscs-history-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceOffline MCP server for querying Russian construction normative rates (FSNB-2022/GESN) via SQLite with full-text search.510 npmMIT
- AlicenseNot gradedqualityAmaintenanceMCP server for parsing, diffing, and validating Turkish public construction unit price catalogs (ÇŞB birim fiyat) from PDFs, enabling AI agents to compute with structured price data.1MIT
- AlicenseCqualityBmaintenanceLocal-first MCP server enabling catalog discovery, dataset context, and safe downloads of construction datasets.18Apache 2.0
- AlicenseNot gradedqualityBmaintenanceMCP server that provides read-only access to 1C:Enterprise configuration metadata extracted into SQLite, enabling LLMs to inspect objects, modules, and validate 1C queries.MIT
- AlicenseAqualityAmaintenanceMCP server for the Russian state registries EGRUL (legal entities) and EGRIP (individual entrepreneurs), built on official Federal Tax Service open-data dumps. Self-hosted via local SQLite.856 PyPI2MIT
- AlicenseBqualityAmaintenanceMCP server that provides programmatic access to the Israeli Central Bureau of Statistics (CBS) price indices and economic data913 npm4MIT
TDQS
Scored across 4 tools
Each tool targets a distinct purpose: listing datasets, showing version history, salary dynamics for a specific region, and regional ranking by salary growth. No two tools overlap in function, and the descriptions make their differences clear.
All names use lowercase snake_case with descriptive two-word compounds. While 'list_datasets' is verb-first, the others are noun phrases (dataset_versions, salary_history, salary_growth_ranking), but the style is uniform and predictable.
With only 4 tools, the server is well-scoped and focused on its purpose of providing historical data analysis. Each tool serves a distinct need, and the count is neither too thin nor excessive.
The server covers listing, version history, and two specific salary analyses, but lacks a tool to retrieve the actual data content of a dataset version. This leaves a notable gap for users who need raw historical dataset values rather than derived salary insights.