VectorSmith
Related Servers
Alternatives to VectorSmith
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables agents to dynamically generate typed MCP tool schemas, validate Python execution ASTs against unsafe imports, and hot-plug sandboxed callable handlers into an active runtime. This allows new tools to be synthesized and safely executed on demand.7MIT
- AlicenseNot gradedqualityAmaintenanceConverts a GraphQL schema into MCP tools, allowing AI to discover and call GraphQL queries and mutations via natural language.131 npmMIT
- AlicenseBqualityCmaintenanceTransforms OpenAPI definitions into MCP tools for seamless LLM-API integration.819 npm1MIT
- AlicenseNot gradedqualityBmaintenanceExposes Iceberg-backed ontology objects, links, and actions as typed MCP tools for LLM agents, enabling governed data access and operations without raw SQL.MIT
- AlicenseNot gradedqualityBmaintenanceEnables declaring a catalog of tools for LLMs, filtering them by role, validating arguments, guarding sensitive calls with server-side confirmations, and recording an audit log.17 npmMIT

TCPcore Governance Kernelofficial
AlicenseNot gradedqualityAmaintenanceCompiles YAML adapters or OpenAPI specs into a minimal MCP tool surface that exposes only declared capabilities to agents, with risk-tiered execution, human approval queues, credential brokering, prompt-injection sanitising and NIST AU-3 audit logging. This lets operators put scoped identity, permissions and kill switches in front of any API so agents can call exactly the tools they need and nothing more.3MIT
TDQS
Scored across 7 tools
get_invoice, count_invoices, and the meta discovery/execution tools are distinct, though run_tool is a catch-all that could execute any of the invoice tools. The real ambiguity is that search_invoices already supports status filtering, making search_paid_invoices and list_overdue_invoices overlapping subsets. The use-when guidance helps, but an agent could reasonably pick either general or specialized tools for paid/overdue queries.
All tool names follow a predictable snake_case verb_noun pattern: search_invoices, get_invoice, count_invoices, list_overdue_invoices, search_paid_invoices, run_tool, and list_available_tools. The meta tools do not break the convention, so naming is consistent across the set.
Seven tools is well within the ideal scope, with two infrastructure tools for dynamic discovery/execution and five read-only invoice tools. Each tool has a reasonable purpose, and the count does not feel bloated or thin.
The read-only invoice workflow is well covered: search, get by ID, count, overdue list, and paid search. It lacks create/update/delete operations and an explicit 'list all invoices' tool, but search with filters can work around the latter, and the descriptions imply a query/reporting focus.