acn-preflight-mcp
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bounty_reality_checkA | Check current public GitHub evidence for a bounty or issue before contributing. |
| repo_contribution_readinessB | Assess repository contribution readiness before an agent starts work. |
| payment_preflightB | Run technical payment preflight before a payment attempt. |
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
payment_preflight is clearly distinct, but repo_contribution_readiness and bounty_reality_check both target pre-contribution GitHub checks and could be confused. The descriptions clarify that one is about repository health and the other about bounty/issue evidence, but the boundary is somewhat subtle.
All names use lowercase snake_case noun phrases that lead with the domain (repo, payment, bounty). They are readable and consistent in style, though they mix suffixes like _readiness, _preflight, and _reality_check rather than following a single verb_noun pattern.
Three tools is minimal but reasonable for a focused preflight server. Each tool covers a distinct preflight scenario and none feels redundant, though the surface is on the small side.
For a preflight-focused server, the three core scenarios (repository, payment, bounty/issue) are covered and give an agent the checks needed before acting. There are minor gaps, such as no generic environment or dependency preflight, but they do not create dead ends.