Meridian Bank MCP Server (saivarmadpr/meridian-mcp) is an MCP server listed on the M8ven Trust Index. It scores 68 out of 100, grade C. It declares 20 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Caution
68/100

Meridian Bank MCP Server

A production-grade MCP server for a fictional digital bank, exposing tools for an AI copilot to service customers across the full risk spectrum from read-only lookups to money movement and destructive admin actions, with OAuth 2.1 security and a realistic dataset.

→ saivarmadpr/meridian-mcp· listed on glama

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

saivarmadpr

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Secret credentials may flow to a network call
3 flows detected: OAUTH_CLIENT_SECRET. We can’t prove the destination matches the brand the credential belongs to.
🚨
Known vulnerabilities in dependencies: 1 critical, 2 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
// tools this server exposes20 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

list_accounts

List all accounts for a customer.

get_account

Fetch a single account by id.

get_balance

Fetch the current balance and status of an account.

list_transactions

List an account's transactions, newest first, with keyset pagination.

get_transaction

Fetch a single transaction by id.

freeze_account

Freeze an account (blocks activity; reversible).

unfreeze_account

Reactivate a frozen account.

reverse_transaction

Reverse a posted transaction, creating a compensating entry and adjusting the balance.

close_account

Close an account. The balance must be zero.

adjust_balance

Apply an administrative credit (positive) or debit (negative) to an account.

list_cards

List cards for an account.

freeze_card

Freeze a card (reversible).

unfreeze_card

Reactivate a frozen card.

search_customers

Search customers by name, email, or phone (partial match).

get_customer

Fetch a customer profile by id (includes PII: DOB, SSN last-4).

open_dispute

Open a dispute against a transaction.

create_payee

Add a payment recipient (ACH or wire) for a customer. Account/routing numbers are stored masked.

create_transfer

Move money between two Meridian accounts. Atomic and idempotent.

initiate_ach_payment

Send an ACH payment from an account to a registered payee. Atomic and idempotent.

initiate_wire

Send a wire transfer to a registered payee. Requires BOTH payments:write and wire:write scopes.

// known CVEs in dependencies1 critical2 high1 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

criticalvitest@2.1.9GHSA-5xrq-8626-4rwp

When Vitest UI server is listening, arbitrary file can be read and executed

high@faker-js/faker@9.9.0GHSA-qxc2-j82w-r537

Faker: helpers.fake exploitable into arbritary code execution

highdrizzle-orm@0.36.4GHSA-gpj5-g38j-94v9

Drizzle ORM has SQL injection via improperly escaped SQL identifiers

lowvitest@2.1.9GHSA-82fw-gwwq-j7x9

Vitest: Path Traversal / Arbitrary File Read via @vitest/mocker Redirect Mock

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployDATABASE_URL
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

20/20 tools missing one or more hints — list_accounts (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_account (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_balance (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +17 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tool test coverage

Only 4/20 tools referenced in tests (20%)

Write tests that reference each tool by name so every tool has at least one test.

Production dependencies are patched

0 critical, 2 high severity in production deps — @faker-js/faker@9.9.0 (high), drizzle-orm@0.36.4 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Dev dependencies

1 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 6 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/saivarmadpr/meridian-mcp?variant=verified)](https://m8ven.ai/mcp/saivarmadpr/meridian-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 461f0867615bfb29ca14ed1ae5c07ef0bb126ba9
code hash: 19c86fc3d4fbfd3fbc24dd0a2d47c6a1a47862f0713f831d20d2d11dcd9551f2
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client