BankRegPulse
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Optional port for HTTP/SSE mode, defaults to 3000. | 3000 |
| MCP_TRANSPORT | No | Set to 'http' to run the MCP server as an HTTP endpoint instead of stdio. | |
| BANKREGPULSE_API_URL | No | Set environment variable to use a custom API endpoint (e.g., https://your-custom-api.com). |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_daily_briefingB | Get the latest daily banking regulatory intelligence briefing with summaries and key developments from OCC, FDIC, CFPB, Federal Reserve, and all 50 state banking departments. |
| get_daily_podcastC | Get the latest daily regulatory podcast audio URL. Listen to an AI-generated summary of the day's regulatory developments. |
| get_linkedin_postB | Get a pre-formatted LinkedIn post about today's regulatory developments, ready to copy and share on social media. |
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 has a clearly distinct purpose: get_daily_briefing provides text summaries, get_daily_podcast delivers audio content, and get_linkedin_post offers social media formatting. There is no overlap in functionality, making it easy for an agent to select the right tool based on the desired output format.
All tool names follow a consistent verb_noun pattern with 'get_' as the prefix, followed by a descriptive noun phrase (daily_briefing, daily_podcast, linkedin_post). This uniformity enhances readability and predictability across the tool set.
With only 3 tools, the server feels thin for the domain of banking regulatory intelligence, which might involve more operations like searching archives or filtering by agency. While the tools cover core outputs, the count is borderline low for comprehensive coverage.
The tool set is severely incomplete for a regulatory intelligence server, as it only provides retrieval of pre-formatted outputs without any CRUD operations, search capabilities, or filtering options. Agents cannot interact with historical data, customize queries, or manage content, leading to significant gaps in functionality.