A local MCP server that exposes Brighty banking functions to an AI agent through Brighty's API. MCP lets an agent call tools from another program.

Use it to run the Brighty server with npx and connect it to Brighty's banking API using BRIGHTY_API_KEY and BRIGHTY_API_URL.

It provides a configured bridge to Brighty when you have the required API key and service URL.

brighty — MCP server for Claude Code and Codex by razz-team: A local MCP server that exposes Brighty banking functions…

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add mcp/razz-team/brighty-agent-toolkit/brighty

Clone the repo

git clone --depth 1 https://github.com/razz-team/brighty-agent-toolkit

Made for: Claude Code, Codex, Cursor.

Or install brighty, the plugin that ships this one along with the rest of its 4 skills, 1 MCP server.

Per session not measured What this adds to a session before it is invoked.

When invoked not measured Not applicable: nothing here is loaded into a session.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Security

Grade A, and why

brighty scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.mcp.json · 16 lines

What it actually says

{
  "brighty": {
    "type": "stdio",
    "command": "npx",
    "args": [
      "-y",
      "-p",
      "@brighty-app/[email protected]",
      "brighty-mcp"
    ],
    "env": {
      "BRIGHTY_API_KEY": "${BRIGHTY_API_KEY}",
      "BRIGHTY_API_URL": "${BRIGHTY_API_URL}"
    }
  }
}

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

3d ago First seen · 16 lines scan A 8bcbaada55d1

Subscribe to this mod's changes

brighty is an MCP server published in the GitHub repository razz-team/brighty-agent-toolkit (2 stars, last pushed 21d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Finance and fintech

brighty

Getting it into your agent

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other mcp servers, from other repositories

options-chain-mcp

sap-mcp

nestegg-calculators

workday-hcm

vertex-o

monarch-mcp