Agent to Brokerage Resolver MCP Server
Related Servers
Alternatives to Agent to Brokerage Resolver MCP Server
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityCmaintenanceEnables AI assistants and agents to query U.S. real estate data, including property lookups, comparables, property searches, skip tracing, phone/address verification, and investor buy boxes, through plain-language requests.1MIT- AlicenseAqualityAmaintenanceEnables listing and verifying licensed contractors across California, Texas, Washington, Oregon, and Louisiana by state, trade, city, county, license number, or business name, returning license status, expiration, classifications, owners, address, and phone.174 npmMIT
- AlicenseAqualityDmaintenanceReal-time contractor license verification across 45 US states. Verifies license status, expiration, and disciplinary history directly against state licensing board portals.471 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents and procurement systems to verify contractor licenses against official state boards, search contractors by trade and location, audit workers' comp, surety bonds and OSHA safety records, and check SAM.gov federal debarment status. It returns a deterministic ALLOW/WARN/BLOCK compliance decision plus registry health metrics for US trade contractors.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to research U.S. companies and associated people using official state registries and free regulatory datasets, with normalized evidence and optional browser automation.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to query and analyze self-hosted real-estate public-records data through 20 read-only MCP tools, including property search, foreclosure and distress signals, comps, market context, and optional license-gated deal scoring.MIT
TDQS
Scored across 1 tool
With a single tool, there is no possibility of misselection between tools. The tool's purpose (resolving an agent to a brokerage via three explicit modes) is unambiguous.
The sole tool uses a clear snake_case verb_noun pattern (resolve_agent_brokerage). With only one tool there is no internal inconsistency, and the name is readable and domain-specific.
One tool for an entire server is on the thin side; the three modes are packed into a single tool rather than exposed as separate operations. It is defensible for a narrow resolver, but by the stated guidance 1-2 tools is borderline.
The lookup, roster_firm, and roster_zip modes cover the main access patterns for agent and brokerage data. Minor gaps exist (e.g., no direct supported-states/coverage query or explicit brokerage lookup by name), but core workflows are covered.