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 gradedqualityBmaintenanceEnables AI agents to call tools through a security gateway that intercepts requests, enforces deterministic policy and risk checks, blocks or escalates high-risk actions for human approval, and keeps tool credentials and audit logs protected.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to call backend tools under per-agent policy, deciding which tools each agent can see, what arguments it may pass, how often it may call, and which writes wait for human approval. It also redacts secrets and PII from tool results, fences untrusted output against injection, and records every call in a hash-chained audit log.25 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to safely invoke enterprise tools such as Supabase PostgreSQL and the Notion API through a zero-trust gateway that performs server-side policy and risk evaluation, cryptographically binds approval tickets to exact parameters, and requires out-of-band human approval for destructive operations. It also scrubs credentials from logs and responses while providing audit trails, rate limiting, and a web console for reviewing pending authorizations.Apache 2.0
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.