mcp-onprem-starter
Related Servers
Alternatives to mcp-onprem-starter
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceThis MCP server starter template enables developers to quickly build production-ready MCP servers with Streamable HTTP, stateless design, and OAuth 2.1 authorization. It provides a structured, capability-based architecture with Postgres audit logging and centralized scope enforcement.-
- FlicenseNot gradedqualityDmaintenanceA starter template for building MCP servers in Python using the streamable HTTP transport protocol. Provides a foundation with the MCP Python SDK and example configuration to quickly develop custom MCP servers.2-
- AlicenseNot gradedqualityDmaintenanceA production-ready FastMCP server template supporting local development with stdio and secure web deployment with HTTPS and OAuth.4MIT
- FlicenseNot gradedqualityNot gradedmaintenanceA corporate MCP server template in Python, built with FastMCP for stateless, scalable deployment behind a load balancer with health/readiness endpoints and JSON structured logging.-
- AlicenseNot gradedqualityCmaintenanceOpinionated template for building read-only MCP servers with I/O timeouts, offline tests, compact text outputs, and least-privilege security guidance.MIT
- FlicenseBqualityBmaintenanceA starter template for building an MCP server with Vault-based secret management and Postgres-backed configuration, featuring tool-level authorization and redacted output.11-
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: list_records for querying/searching with pagination, and create_record for inserting new records. No overlap or ambiguity exists.
Both tools follow a consistent verb_noun pattern (list_records, create_record), making the API predictable and easy to navigate.
At 2 tools, the set is on the thin side, but for a 'starter' server it could be intentionally minimal. However, the reference to get_record suggests at least one more expected tool.
The set is missing get_record, update_record, and delete_record. list_records explicitly instructs agents to use get_record, but that tool does not exist, creating a clear dead end and significant coverage gap.