ulasim
Related Servers
Alternatives to ulasim
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants and MCP clients to ask natural-language questions about DuckDB or CSV data and receive safe, read-only SQL-generated tabular insights with automatic schema discovery and multi-table joins.1-
- FlicenseNot gradedqualityDmaintenanceEnables running read-only SQL queries and exploring DuckDB databases through MCP tools like listing tables, describing schemas, and fetching paginated data.-
- AlicenseNot gradedqualityCmaintenanceLets an AI assistant explore and query Postgres, DuckDB, or Snowflake with read-only SQL, table and schema discovery, sampling, and explainable guardrails.MIT
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients and LLMs to interact with a DuckDB database through SQL query execution, table creation, and schema inspection, with optional read-only operation.-
- AlicenseNot gradedqualityCmaintenanceProvides read-only SQL analytics on local CSV, Parquet, and JSON datasets using DuckDB, with pagination, security guardrails, and health monitoring.MIT
- FlicenseNot gradedqualityAmaintenanceEnables executing SQL queries and inspecting or modifying DuckDB database schemas through MCP, with optional read-only mode and connection reuse for secure local analysis.-
TDQS
Scored across 3 tools
Each tool has a clearly distinct role: sema inspects schema metadata, sorgu executes a SELECT query, and istasyon_bul searches for a station by name. There is little risk of confusing these actions, even for an agent unfamiliar with the domain.
The names mix bare nouns (sema, sorgu) with a noun+verb compound (istasyon_bul), so there is no predictable verb_noun pattern across the set. They remain readable and domain-appropriate, but the convention is inconsistent.
Three tools is a lean but reasonable surface for a read-only transport data query server. Each tool covers a necessary step—schema discovery, query execution, and station lookup—though the set feels slightly minimal.
The tools cover the core read-only workflow: learn the schema, run a SELECT, and resolve station names. Minor gaps exist, such as no explicit table listing or richer result metadata, but these are workable through sema and sorgu.