Geekflare
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | Your Geekflare API key | |
| API_BASE_URL | No | Override the API base URL (default: https://api.geekflare.com) | https://api.geekflare.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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| webScrapeC | Scrape a webpage with custom options |
| metaScrapeC | Scrape meta tags from a URL |
| screenshotC | Capture a screenshot of a website |
| searchB | Search the web and return clean results in JSON, Markdown, or HTML |
| dnsRecordC | Retrieve DNS records for a domain |
| siteStatusC | Check if a site is up or down |
| redirectCheckB | Check the redirect chain of a URL |
| brokenLinkC | Find broken links on a webpage |
| url2PdfD | Convert a URL to PDF |
| openPortsC | Scan open ports on a host |
| tlsScanB | Scan TLS/SSL configuration of a domain |
| loadTimeC | Measure page load time for a URL |
| ttfbC | Measure Time To First Byte (TTFB) for a URL |
| httpHeaderB | Fetch HTTP response headers for a URL |
| httpProtocolC | Detect HTTP protocol versions supported by a URL |
| mixedContentC | Check for mixed content issues on a site |
| dnsSecB | Check if DNSSEC is enabled for a domain |
| mtrC | Perform MTR network diagnostic test |
| pingC | Ping a host |
| lighthouseC | Run Lighthouse audit on a website |
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 20 tools
Each tool has a distinct purpose, ranging from DNS checks to performance measurements, with no apparent overlap. An agent can reliably select the correct tool for a given task.
Tools follow a consistent camelCase pattern (e.g., brokenLink, dnsRecord, httpHeader) with occasional single-word names (ping, search) that do not break consistency.
20 tools is on the higher side but justified by the broad scope of web and network diagnostics. Each tool serves a specific function, and the count feels appropriate rather than bloated.
The tool set covers a wide range of diagnostic and scraping tasks, including DNS, HTTP, security, performance, and network tools. Minor gaps exist (e.g., no whois lookup) but the surface is largely complete for its domain.