bandiradar-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENAI_API_KEY | No | OpenAI API key. Required if BANDIRADAR_LLM_PROVIDER is 'openai'. | |
| ANTHROPIC_API_KEY | No | Anthropic API key. Required if BANDIRADAR_LLM_PROVIDER is 'anthropic'. | |
| BANDIRADAR_LLM_PROVIDER | No | LLM provider for relevance scoring. Options: 'anthropic' or 'openai'. If not set, falls back to offline heuristic. |
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 |
|---|---|
| list_sourcesA | List the registered funding sources as [{id, kind}]. |
| fetch_opportunitiesC | Ingest a source into the store, saving progressively. |
| search_opportunitiesA | Rank opportunities for a profile (offline in sample mode). |
| score_opportunityC | Score one stored opportunity for a profile; returns a single Match dict. |
| get_matchesA | Return PERSISTED matches for this profile_version (no recompute). |
| get_profileC | Return the parsed profile as a dict. |
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 6 tools
Each tool has a distinct role in the workflow: listing sources, ingesting opportunities, ranking opportunities, scoring a single opportunity, retrieving persisted matches, and inspecting the profile. Even the related matching tools are clearly separated by computation versus persistence.
All tool names follow a consistent snake_case verb_noun pattern with clear, imperative verbs. There is no mixing of conventions or vague generic names.
Six tools is a well-scoped size for a funding opportunity matching server. Each tool covers a meaningful part of the workflow without redundancy or bloat.
The core lifecycle of fetching sources, searching/ranking opportunities, scoring individual opportunities, and retrieving persisted matches is covered. Minor gaps exist around direct opportunity detail retrieval and profile management, but these are workable through existing tools.