Skip to main content
Glama
vishalhabib99

listing-claim-check

by vishalhabib99
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to listing-claim-check

No user-submitted related servers found.

    Related Servers

    • AgentGround Cross-Check

      Arafel187
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to cross-verify candidate claims against caller-supplied source texts, flagging hallucinations, numerical drift, entity mismatches, contradictions, and unverified assertions. It returns sentence-level verdicts with matched evidence snippets and machine-readable factual grounding confidence scores, exposed over MCP stdio, HTTP REST, and A2A discovery routes.
      MIT

    • claimgate

      caseone115
      A
      license
      A
      quality
      A
      maintenance
      Enables MCP clients to gate drafts before publishing by extracting and checking claims against supplied evidence, enforcing configured policy rules, and flagging missing AI-disclosure requirements. It exposes tools for draft checks, claim listing, policy-only checks, and server metadata.
      5
      MIT

    • One1 Trademark Risk Check

      Yusanfeng134
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables cross-border e-commerce sellers to run pre-listing clearance checks on brand names, listing copy, and logos against tens of millions of registered marks across dozens of jurisdictions, and to see whether an owner is a frequent TRO or Schedule A enforcer. It works as a hosted remote server inside any MCP-compatible AI assistant, with coverage and data-freshness lookups included.
      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.8/5.0

    Scored across 1 tool

    Disambiguation5/5

    There is only one tool, so there is no possibility of confusion or misselection between overlapping tools. Its single responsibility is clearly described and easy to identify.

    Naming Consistency5/5

    With a single tool, the naming is trivially consistent: 'check_listing' follows a clear verb_noun pattern and aligns with the server's purpose.

    Tool Count4/5

    One tool is below the typical well-scoped range of 3-15, so it feels slightly thin, but the server's narrow purpose genuinely requires only this one operation.

    Completeness5/5

    The tool fully covers the stated domain: it checks listing claims against item specifics, classifies them, and returns a publish or review decision. No additional endpoints are needed for this focused workflow.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources