assessorai-dados
OfficialRelated Servers
Alternatives to assessorai-dados
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceProvides tools to search and retrieve US federal and state legislative data, including bills, votes, campaign contributions, and legislator information, with provenance tracking.81MIT
- AlicenseAqualityBmaintenanceEnables querying Brazilian Chamber of Deputies open data for constitutional amendment proposals (PECs), including details, authorship, legislative history, roll-call votes, and party voting guidance.8MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to query Brazilian Senate data including senators, bills, voting records, committees, and plenary sessions through natural language.9 npm6MIT
- AlicenseAqualityAmaintenanceMCP server for the Brazilian Chamber of Deputies open-data API, enabling search and retrieval of federal legislative bills and their status.1542 PyPI1Apache 2.0
- FlicenseNot gradedqualityDmaintenanceEnables access to comprehensive U.S. legislative and governmental data from GovInfo.gov and Congress.gov APIs, including bills, Congressional records, Federal Register documents, member information, and committee activities.1-
- AlicenseBqualityNot gradedmaintenanceEnables interaction with the Brazilian Chamber of Deputies Open Data API, providing access to information about legislators, legislative proposals, voting records, events, committees, and parliamentary activities through 57 typed and validated tools.63-
TDQS
Scored across 7 tools
Each tool targets a distinct task: metadata lookup, source enumeration, search, text paging, related-item discovery, release manifest retrieval, and download URL resolution. Even the release/download pair is clearly separated by manifest metadata versus asset URL.
All tool names follow a consistent snake_case verb_noun pattern (get, list, search, read, find). The naming style is uniform and predictable across the entire set.
Seven tools is well-scoped for a read-only legislative data API. Each tool covers a meaningful part of the workflow without redundancy or bloat.
The tool surface covers the full read-only lifecycle: discovery via search, metadata retrieval, full-text access, related-proposition exploration, and dataset distribution. Dependencies between tools are coherent, with no obvious dead ends for common workflows.