last-mile-mcp
Related Servers
Alternatives to last-mile-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables controlled AI-agent access to enterprise-shaped tools with a deny-by-default gated write path, human approval, dry-run execution, and append-only audit logging.1-
- AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible AI agents to safely act on business backends by enforcing per-agent permissions, autonomy thresholds, human approval with review-and-edit, and full audit trails.MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to securely call enterprise MCP tools with tenant-scoped RBAC, human approvals, audit logging, and multi-tool workflows across customer, order, document, and ticket data.-
- AlicenseNot gradedqualityAmaintenanceExperimental read-only MCP for Supabase application data: memory_search, memory_get and memory_list_recent under user-bound PostgreSQL RLS. Setup and demo: https://github.com/jryski/Supabase_user_MCP/blob/main/docs/GETTING_STARTED.md . Public preview is POSIX-only and synthetic-only; native Windows, hosted OAuth, one-click installation and writes are not available.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceGates agent tool execution with human approval, audit trails, and replay-resistant permits, enabling safe use of tools in agent loops.15 PyPIMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to securely invoke tools by enforcing identity proof, capability verification, and risk scoring on every request, blocking unsafe calls before they execute.MIT
TDQS
Scored across 8 tools
Each tool serves a distinct purpose: customer lookup, ticket listing, invoice listing, combined health view, ticket creation, invoice draft creation, draft listing, and identity/grants. No two tools overlap in intent, and the descriptions clarify any potential ambiguity (e.g., account_health explicitly combines data from other tools).
Naming mixes verb-first (find_customer, open_ticket, prepare_invoice) with noun-first (customer_tickets, customer_invoices, account_health) and possessive (my_drafts, whoami). The pattern is readable but not consistent, lacking a uniform verb_noun or resource_noun structure.
8 tools is well-scoped for a customer service and billing domain. Each tool covers a core operation without unnecessary bloat, and the count feels neither thin nor overwhelming.
The surface covers customer lookup, ticket listing/creation, invoice listing/drafting, health summaries, and identity. Missing update/close actions for tickets or invoices, but these are intentionally excluded (e.g., invoice issuance is human-only), so the gaps are not fatal and agents can work within the design.