Forency
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| lookup_tech_stackA | Detect the technologies a website runs: CMS, ecommerce platform, JavaScript frameworks, analytics, CRM, marketing automation, payment processors, chat widgets, CDN, and hosting. Use it to research a competitor, qualify a sales prospect, or check what a site is built with. Reads the HTML and headers the server sends, so anything injected only by client-side JavaScript may not appear — a sparse result means little was detectable, not that the site runs nothing. Counts as one scan against the caller's plan. |
| batch_lookupA | Detect the technology stacks of up to 25 websites in one call, returning the full detail for each. Use it when working through a list of prospects, competitors, or portfolio sites. If you want a side-by-side view of who uses what, use compare_stacks instead. Counts one scan per URL against the caller's plan. |
| compare_stacksA | Scan 2-25 websites and return a side-by-side table of which technologies each one uses. Answers questions like 'which of these prospects use HubSpot vs Salesforce?' or 'how does our stack compare to our competitors?'. For the full per-site detail rather than a table, use batch_lookup. Counts one scan per URL against the caller's plan. |
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 3 tools
Each tool serves a distinct workflow: single-site lookup, bulk detail lookup, and side-by-side comparison. The descriptions explicitly cross-reference each other, making it clear when to choose one over the other.
Two names follow a verb_noun pattern (lookup_tech_stack, compare_stacks), while batch_lookup is a modifier_noun form. The inconsistency is minor and all names are still clear and predictable.
Three tools is well-scoped for a tech-stack detection server. Each tool covers a distinct usage size: single, batch, and comparative, with no redundant or unnecessary additions.
The tool surface covers the full intended workflow: looking up one site, looking up many sites, and comparing stacks across sites. There are no obvious dead ends or missing operations within the stated domain.