Skip to main content
Glama
thanhnv2210

finpay-mcp-server

by thanhnv2210

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LOG_LEVELNodebug | info | warn | errorinfo
DOCU_RAG_URLNoBase URL of the docu-rag API. Enables search_docs tool.

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

CapabilityDetails
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": true
}
resources
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_transactionA

Look up a single FinPay transaction by its ID. Returns the full transaction object including status, amount, currencies, exchange rate, sender/recipient names, and hub assignment. Returns a NOT_FOUND error if the ID does not exist.

list_transactionsA

List recent FinPay transactions with optional filters. Returns up to 50 transactions ordered by createdAt descending. Supports filtering by status and/or hubId. Returns an empty array if no transactions match the filters.

get_payment_hubA

Get a payment hub's current details and health metrics. Returns hub status, supported currencies, supported countries, transfer amount limits, average latency, and 24h success rate. Returns a NOT_FOUND error if the hub ID does not exist.

list_payment_hubsA

List all payment hubs in the FinPay platform with their current status and health metrics. Returns all 4 hubs: GlobalPay (global), SwiftRoute (SWIFT high-value), MobileFirst (mobile money), and RegionalX (Southeast Asia).

explain_serviceA

Get a detailed explanation of a FinPay microservice: its purpose, owning team, implementation language, upstream dependencies, downstream dependents, current health status, and port. Also returns a human-readable dependency graph description. Returns a NOT_FOUND error if the service name does not exist.

list_servicesA

List all 7 microservices in the FinPay platform with their metadata and current health status. Services include: api-gateway, transaction-service, hub-adapter-service, compliance-service, fx-service, notification-service, and audit-service.

get_system_healthA

Get a unified health snapshot of the entire FinPay platform. Returns overall system status (HEALTHY, DEGRADED, or DOWN), per-service health, per-hub health with success rates, and any active alerts. Use this tool first when triaging incidents.

search_docsA

Full-text search over FinPay architecture documentation via the docu-rag API. Returns a synthesised answer plus the top matching document chunks. Requires the DOCU_RAG_URL environment variable to be set; returns a disabled error if it is not configured.

Prompts

Interactive templates invoked by user choice

NameDescription
architecture-reviewLoad full FinPay system context (all services, all hubs, dependency graph) and conduct a structured architecture review. Optionally focus on a specific quality attribute such as resilience, scalability, or security.
incident-triageLoad current system health, recent failed or degraded transactions, and hub health metrics. Guides a structured incident triage. Optionally focus on a specific transaction ID.

Resources

Contextual data attached and managed by the client

NameDescription
services-catalogFull JSON catalog of all 7 FinPay microservices. Each entry includes the service name, description, owning team, implementation language, upstream dependencies, downstream dependents, current health status, port, and repository. Read this resource first to understand the platform before asking tool questions.
architecture-overviewMarkdown document describing the FinPay system architecture: components, transaction lifecycle, dependency graph, payment hubs, key design decisions, and known trade-offs. Read this resource to get a complete system picture before conducting an architecture review or incident triage.

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/thanhnv2210/finpay-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server