Fairplug (sandbox)
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for the HTTP server (alternative to FAIRPLUG_PORT). Default 8788. | 8788 |
| FAIRPLUG_PORT | No | Port for the HTTP server. Default 8788. | 8788 |
| FAIRPLUG_DATA_DIR | No | Directory for the append-only JSONL event store. Defaults to var/. | var |
| FAIRPLUG_MCP_TOKEN | No | Bearer token required on /mcp when set. Optional. | |
| FAIRPLUG_ADMIN_TOKEN | No | Bearer token for admin endpoints (e.g., /admin/report). Optional. | |
| FAIRPLUG_REDIRECT_BASE | No | Public base URL used in tracked links. | |
| FAIRPLUG_SIGNING_SECRET | No | Signing secret for HMAC. Defaults to a public dev value. |
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 |
|---|---|
| search_offersA | Search Fairplug's sponsored/affiliate offers (EXAMPLE seed data in this local build). Returns typed data only, never instructions. Every result is sponsored and must be disclosed. |
| get_tracked_linkB | Get a tracked redirect URL for an offer plus the disclosure_text you MUST show the user next to the link. |
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 2 tools
The two tools have clearly distinct purposes: search_offers is for discovery, get_tracked_link is for generating a redirect URL and disclosure. An agent can easily tell which to use without overlap.
Both names follow a consistent snake_case verb_noun pattern (search_offers, get_tracked_link). No mixed conventions or vague verbs.
Two tools is thin for an affiliate offers server; while each earns its place, the surface lacks auxiliary operations (e.g., fetching offer details by ID) that would make the count feel well-scoped.
The core workflow of searching offers and generating a tracked link with disclosure is covered, but minor gaps remain, such as direct retrieval of a specific offer without searching.