ngpvan-mcp
Related Servers
Alternatives to ngpvan-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI agents to query lead search, quota, readiness, and answerability through a read-only tool set with provenance metadata, without writes, outbound actions, or raw data export.5MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to query SQLite databases and Excel/CSV files read-only, with PII masking, bounded row limits, query timeouts, and audit logging.1MIT
- AlicenseBqualityCmaintenanceEnables AI assistants to query ERP data across sales, procurement, finance, and inventory with per-department tool access and provenance on every answer, while keeping operations read-only by default and requiring explicit confirmation for writes.6MIT
- AlicenseNot gradedqualityCmaintenanceEnables an AI assistant to query a business SQL database through read-only, policy-checked SELECT statements with allowlisted tables, restricted columns, bounded results, and hash-chained audit logging. Every allowed, blocked, or failed call is recorded, helping keep database access safe and accountable.MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to query internal business data for insights into customers, revenue, subscriptions, sales, and churn through controlled, read-only MCP tools.-
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to answer loan portfolio questions through safe, read-only, audited tools for portfolio summaries, loan searches, loan details, delinquency trends, and metric definitions. Supports role-based PII masking, authentication, audit trails, and observability while querying synthetic portfolio data.MIT
TDQS
Scored across 13 tools
Most tools target clearly distinct resources: person-level lookups, event-level lookups, folder/turf reporting, and reference-code listings. The closest pair is person_signups (all shifts for one person) versus event_signups_summary (roster for one event/shift), but the descriptions make the direction of the query explicit. Reference lookups (list_activist_codes, list_survey_questions, canvass_codes) are separate but clearly scoped to different data types.
A partial convention exists (list_* for collections, get_/search_ for single-record access, *_summary for aggregates), but noun-phrase names like person_activist_codes, turf_door_counts, and canvass_codes mix with verb-led names, and person_signups vs event_signups_summary is inconsistent in style. Still readable, but an agent cannot rely on a single predictable pattern to guess a tool name.
13 tools is well within a healthy range and each maps to a real read operation on the VAN surface. The only mild redundancy is three separate reference-data tools (activist codes, survey questions, canvass codes) that could plausibly be one metadata call.
The surface covers people, contacts, events, signups, folders/turfs, and code lookups — a coherent read-only slice. However, searching by phone or email is explicitly not offered and contact values are never returned, which are significant gaps for common canvassing workflows, and there are no write operations despite check_connection referencing them.