intelligence-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_PAT | Yes | GitHub Personal Access Token for scanning repositories and issues | |
| ANTHROPIC_API_KEY | Yes | Anthropic API key for classifying and scoring opportunities |
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 |
|---|---|
| scan_opportunitiesC | Scan the agent payments ecosystem for actionable opportunities. |
| get_protocol_infoC | Get details about a specific agent payment protocol. |
| compare_protocolsB | Compare agent payment protocols across key dimensions. |
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 clearly distinct purpose: comparative analysis (compare_protocols), detailed retrieval (get_protocol_info), and ecosystem discovery (scan_opportunities). No functional overlap exists between them.
All three tools follow a consistent verb_noun snake_case pattern (compare_protocols, get_protocol_info, scan_opportunities) with predictable action words appropriate to their functions.
Three tools is borderline thin for the domain; while it covers basic read/compare/scan operations, the minimal surface leaves little room for additional analytical or filtering capabilities that intelligence workflows typically require.
Notable gap exists in protocol discovery: get_protocol_info and compare_protocols appear to require specific protocol identifiers, but no list_protocols or search_protocols tool is provided to discover available identifiers before using the other tools.