Skip to main content
Glama
ramaibrm

amanahfy-ai-mcp

by ramaibrm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PORTNoPort for HTTP transport8000
DEBUGNoEnable debug loggingfalse
NODE_ENVNoNode environment (development/production)production
TRANSPORT_MODENoTransport mode: stdio or httpstdio
IPAPI_API_TOKENNoOptional API token for ipapi
AMANAHFY_API_BASENoBase URL for Amanahfy APIhttps://api.amanahfy.com/api

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
resources
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
ip_get_detailsA

Retrieves detailed geolocation and network information for a public IP address (ipAddress). If no IP is provided, automatically uses the server's current public IP. Returns comprehensive location data including country, region, city, coordinates, timezone, and network details like ISP and organization. Use includeExtendedData to get additional information such as ASN, mobile/proxy detection (requires API token). Note: Cannot lookup private IPs (e.g., 192.168.x.x, 10.x.x.x). Powered by ip-api.com. Enable useHttps for secure connections (required for paid tier).

campaign_get_detailsA

Retrieves detailed information about a donation campaign from Amanahfy by campaign slug. Returns comprehensive campaign data including fundraising progress, organization details, timeline, and campaign features. Use this tool to get current information about active fundraising campaigns. Example slug: "gaza-100k-in-72hrs". Configure timeout and retries for reliability.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
ip-lookup
campaign-lookup
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