Business operationsPublic source

Credit Bureau MCP Server

A credit-reporting (credit bureau) platform for ADK-Rust Enterprise banking agents. 14 MCP tools covering consumers, credit reports (tradelines, inquiries, public records), scores with reason factors,…

Open the source Read the official guide ↗

What it gives an agent

A purpose-built capability behind one MCP connection.

The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.

Consumers — fictitious identities (SSN as a reference handle, minimal address PII) with a security freeze flag.

Credit file — tradelines (revolving/installment/mortgage/auto/student) with balances, limits, payments, lates; public records (bankruptcy/lien/judgment); inquiries.

Scores — a transparent 300–850 rule-based model (utilization, delinquencies, derogatory accounts, public records, hard inquiries, thin file, age) with adverse-action reason factors.…

Report pulls — pull_credit_report assembles the file under a stated permissible purpose; credit_application is a hard inquiry (affects score), others are soft.

Affordability — utilization, monthly obligations, and DTI vs a stated income (healthy/elevated/high) for underwriting and limit review.

Disputes — FCRA disputes flag the tradeline and set a ~30-day reinvestigation due date; resolution clears the flag.

Monitoring — alerts (new inquiry, delinquency, etc.).

Architecture

How Credit Bureau MCP Server fits into an agent system.

The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.

ADK-Rust agent

Chooses a capability from the reviewed tool catalog.

→

MCP client

Discovers schemas, sends calls, and receives typed content.

→

Credit Bureau MCP Server

Validates the request and owns 14 documented tool contracts.

→

Domain system

Keeps the API, data, credentials, and business rules behind the server.

Connection: stdio · Server framework: ADK MCP SDK + rmcp

Credit Bureau MCP Server architecture diagram from its official repository

Tool catalog

What can an agent ask Credit Bureau MCP Server to do?

Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.

14 named tools

create_consumer

Create a consumer record (fictitious identity)

internal write

get_consumer

Get a consumer's identity record (access-logged)

read only

find_consumers

Find consumers by name/ssn_ref (access-logged)

read only

set_freeze

Place/lift a security freeze (blocks new-credit pulls)

internal write

add_tradeline

Add a tradeline to a consumer's file

internal write

add_public_record

Add a public record (bankruptcy/lien/judgment)

internal write

pull_credit_report

Pull a report under a permissible purpose (hard inquiry) — gated

external write

get_score

Get a credit score with reason factors (access-logged)

read only

affordability

Affordability/DTI analysis for decisioning (access-logged)

read only

file_dispute

File an FCRA dispute (flags tradeline, sets due date)

internal write

resolve_dispute

Resolve a dispute reinvestigation — gated

internal write

list_disputes

List disputes by consumer/open status

read only

Governance

Understand the effect of every tool.

A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.

7 read only6 internal write1 external write

The registry manifest declares internal write, read only, external write tool risk classes.

MCP surface

What the current documentation declares.

MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.

The current README concentrates on its tool surface. Check the source and release notes before relying on optional MCP capabilities beyond tool discovery and invocation.

ADK MCP SDKrmcpRegistry manifest

Install and connect

Follow the project’s documented starting point.

Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.

Install

cargo install mcp-credit-bureau

ADK-Rust connection shape

let toolset = McpToolset::from_stdio(
    "mcp-credit-bureau",
    ["mcp-credit-bureau"],
).await?;

let agent = LlmAgentBuilder::new("agent")
    .tools(toolset.tools().await?)
    .build()?;

Commands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.

Official documentation

Continue with the project maintainers’ source of truth.

This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.

Overview ↗README.md CHANGELOG ↗CHANGELOG.md Architecture ↗docs/architecture.svg Issues and support ↗github.com issues

Keep exploring