Skip to main content
Glama
mambalabsdev

Agent to Brokerage Resolver MCP Server

by mambalabsdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Agent to Brokerage Resolver MCP Server

No user-submitted related servers found.

    Related Servers

    • contractor-license-mcp-server

      Noquarter6
      A
      license
      A
      quality
      D
      maintenance
      Real-time contractor license verification across 45 US states. Verifies license status, expiration, and disciplinary history directly against state licensing board portals.
      4
      34 npm
      MIT

    • LicenseGround MCP Server

      bdzgroup12
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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

    • real-estate-data-mcp-server

      AiAgentKarl
      A
      license
      A
      quality
      D
      maintenance
      Provides US real estate data including housing stats, demographics, nearby amenities, area comparisons, cost-of-living analysis, and neighborhood search via free public APIs without any API keys.
      6
      MIT
    • BizVerify MCP Server by BizVerify

      BizVerify MCP Serverofficial

      BizVerify
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to verify and search business entities across US state and international company registries, providing real-time confirmation of legal existence, status, and filings.
      9
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.5/5.0

    Scored across 1 tool

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count3/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityNo data
    ResponsivenessNo issues

    Resources