@apifreaks/mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFREAKS_API_KEY | Yes | Your APIFreaks API key — get one at apifreaks.com |
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 |
|---|---|
| list_modulesA | APIFreaks module catalog (opt-in via ENABLE_MODULES). Call when a needed capability is missing from your tool list, or to check whether APIFreaks covers a topic. Live tools for enabled modules already appear in tools/list; this returns needs_enable[] with paste-ready enable_line values — give the user that ENABLE_MODULES=... line and ask them to restart. Modules: ip-intelligence, geocoding, whois, dns, scraper, email-validation, phone-validation, ssl, domain, screenshot, pdf, currency, commodity, financial, zipcode, weather, geography, timezone, user-agent. ENABLE_MODULES unset — only this tool is registered (example: ENABLE_MODULES=ip-intelligence,whois,dns,domain,weather). |
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 1 tool
With only one tool, there is no risk of confusion or misselection between tools. The tool's purpose (listing available APIFreaks modules) is clearly distinct.
The single tool name list_modules follows a clear verb_noun snake_case convention. Consistency is trivially perfect for a one-tool server.
One tool is borderline thin for a server intended to expose many APIFreaks capabilities. The discovery gate design is reasonable, but the default surface feels under-scoped.
The default surface only lists modules and provides enable instructions, with no actual API operations available until restart. This is a significant gap for agents expecting to use APIFreaks services immediately.