Skip to main content
Glama
ramaibrm

amanahfy-ai-mcp

by ramaibrm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to amanahfy-ai-mcp

No user-submitted related servers found.

    Related Servers

    • apicrate-mcp by apicrateio

      apicrate-mcpofficial

      apicrateio
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides AI agents with 22 data tools across 9 domains, including IP geolocation, email risk scoring, postal codes, countries, timezones, user-agent parsing, cryptographic hashing, Bible search, and QR code generation.
      MIT

    • @ipgeolocationapi/mcp

      thebigasif
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to query IP intelligence tools such as geolocation, VPN/security checks, ASN, timezone, astronomy, user-agent parsing, abuse contacts, and bulk lookups via natural language.
      19 npm
      MIT

    • mcp-ip2location

      eweley95
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to perform IP geolocation, proxy detection, and domain WHOIS lookups using IP2Location.io and IP2WHOIS data.
      5
      MIT

    • AgencyAnalytics MCP Server

      osherai
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to manage campaigns, users, backlinks, keywords, and SEO rankings through natural language using the AgencyAnalytics API.
      20
      1
      MIT

    • amazonads-mcp

      cprice70
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to interact with the Amazon Advertising API to manage campaigns, keywords, product ads, and retrieve performance metrics.
      9
      20 npm
      3
      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.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools are entirely unrelated in purpose: one handles IP geolocation and the other retrieves campaign details. There is zero overlap or ambiguity between them.

    Naming Consistency5/5

    Both tools follow the same 'get_details' verb-noun pattern with clear prefixes ('ip' and 'campaign'), creating a consistent and predictable naming convention.

    Tool Count3/5

    With only 2 tools, the server feels thin. While each tool is distinct, the low count is borderline for a server that appears to cover two separate domains.

    Completeness2/5

    Each domain is only minimally covered: IP lookup has no additional operations beyond details, and campaigns similarly lack listing or mutation endpoints. The server leaves significant gaps for any broader workflow.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources