gatefareio/mcp-server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Log level (e.g., debug for verbose stderr) | info |
| GATEFARE_PAT | No | Personal Access Token for publisher tools | |
| WALLET_NETWORK | No | Network identifier (e.g., eip155:84532 for Sepolia testnet) | eip155:8453 |
| GATEFARE_BASE_URL | No | Override for self-hosted Gatefare instance | https://gatefare.io |
| WALLET_BUDGET_USD | No | Optional spend cap for wallet | unlimited |
| WALLET_PRIVATE_KEY | No | Private key for wallet (required for buyer tools) |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gatefare.search_apisB | Search the Gatefare catalog for paid APIs by text, price, category, or sort order. Returns paginated results with publisher info. |
| gatefare.get_apiA | Get full details for a specific API by slug, or by handle + urlName pair. Returns pricing, stats, uptime, and publisher info. |
| gatefare.list_categoriesA | List all available API categories in the Gatefare catalog with API counts. |
| gatefare.suggestB | Autocomplete search suggestions for API discovery. |
| gatefare.report_abuseA | Report an API for abuse — CSAM, fraud, malware, copyright, trademark, etc. Returns a reference ID for tracking. Submitting a report does not guarantee removal; trust & safety reviews each report. |
| gatefare.publisher_reputationA | Look up the publisher of an API and return their positive-only trust badges: Established (>=3 months tenure), Top contributor (>=1M lifetime successful calls), Highly rated (>=4.5 avg across >=10 reviews). New publishers come back unmarked — absence of badges is NOT a warning, just a lack of accumulated signal. Use this BEFORE calling an unfamiliar API to gauge counterparty risk. |
| gatefare.sample_responseA | Fetch the publisher-pasted representative response for an API. This is what the publisher claims their API returns on a typical successful call. Compare against |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose: search, details, categories, suggestions, reporting, reputation, and sample responses. Even get_api and sample_response are well-separated by their descriptions.
Most tools follow the verb_noun pattern (search_apis, get_api, list_categories, report_abuse), but suggest and publisher_reputation deviate (bare verb, noun_noun). Overall snake_case and gatefare prefix maintain readability.
Seven tools is ideal for this domain, covering discovery, inspection, reputation, and feedback without bloat or redundancy.
The surface fully covers the API catalog workflow: search, suggest, categories, detailed lookups, publisher trust evaluation, sample response verification, and abuse reporting—no obvious dead ends or missing critical operations.