mcp-server-starter-sample
Related Servers
Alternatives to mcp-server-starter-sample
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables read-only discovery and retrieval of allowlisted catalog datasets with host-assigned roles, strict tool validation, SQLite read-only enforcement, and audit hash chaining. It supports querying bounded daily aggregates while preventing arbitrary SQL, file access, shell commands, credential use, or role escalation.-
- AlicenseBqualityBmaintenanceEnables AI assistants and MCP clients to safely inspect allow-listed SQLite databases by listing tables, describing schemas, running capped read-only queries, sampling rows, and exporting CSV, with writes blocked unless explicitly enabled.7MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents and other MCP clients to run read-only, policy-checked SQL queries against SQLite databases, with table and column allowlists, PII restrictions, audit logging, and time and row budgets.MIT
- AlicenseNot gradedqualityCmaintenanceEnables exploring and querying a SQLite database loaded into memory through validated read-only SELECT/WITH statements, with enforced limits on database size, rows, result bytes, cells, and parameters.MIT
- AlicenseAqualityDmaintenanceEnables safe, read-only SQL access to SQLite databases for AI agents, allowing schema exploration and SELECT queries with defense-in-depth protections.3MIT
- AlicenseAqualityBmaintenanceEnables secure, read-only PostgreSQL queries, sandboxed file reads within a confined directory tree, and host CPU, memory, and disk metrics over stdio. It exposes these capabilities through narrowly scoped tools with strict validation and fail-closed guardrails.1MIT
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: running a SQLite SELECT versus fetching an allowlisted URL. There is no realistic overlap or misselection risk between them.
Both names use snake_case, but the patterns differ: sqlite_query is resource_action while fetch_url is verb_noun. The names remain readable, but there is no consistent verb-first convention.
Two tools is thin even for a starter sample server. The scope is understandable, but the surface feels more like a minimal demo than a well-rounded tool set.
The SQLite tool is read-only and the URL tool only fetches, so write and broader lifecycle operations are absent. For a starter sample this may be intentional, but agents needing mutation or schema inspection would hit gaps.