Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

PlugCat

REMOTE · PLUGCAT.COM

Check if a US bank, credit union or brokerage connects to Monarch, YNAB and other finance apps

Available components

71 Trust /100

Last scanned (5 hours ago)

Scores higher than 57% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability72
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 539 tokens (~134/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
  • Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 89% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 3 Nov 26 70

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://plugcat.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=plugcat.com CN=WE1,O=Google Trust Services,C=US 18 Oct 2026 16 Jan 2027 ECDSA 256 ECDSA-SHA256 c640bab4988d1a82133452d2cbaed7f0
SANs: plugcat.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of plugcat.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
plugcat.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://plugcat.com/mcp Verified 200
http (plaintext) http://plugcat.com/mcp HTTPS enforced 301 https://plugcat.com/mcp
MCP tools · 4 exposed · ~414 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_institution ~178

Find a bank, credit union or brokerage by name and say which finance apps likely connect to it. Pass `app` to focus on one app. If several institutions share the name, the largest is used and the others are listed; pass `state` or call get_institution with the right URL.

NameTypeReqDescription
appstring–Optional app name or slug: rocket-money, lunch-money, monarch, copilot, ynab, simplifi, tiller, pocketguard, empower, wave, xero, quickbooks.
kindstring–Only return this kind of institution.
namestringyesInstitution name or brand, e.g. "Chase", "Navy Federal", "Fidelity".
statestring–Two-letter US state code, e.g. "TX", to narrow common names.

No output schema declared.

No examples provided.

get_institution ~91

Full app-by-app results for one institution: status and reason per app, the name to search for in the app, FAQs and identifiers. Takes a URL or path from search_institutions.

NameTypeReqDescription
urlstringyesPage URL or path, e.g. "https://plugcat.com/bank/jpmorgan-chase-bank/" or "/credit-union/navy-federal-credit-union/".

No output schema declared.

No examples provided.

list_apps ~36

The finance apps PlugCat tracks: budgeting apps and accounting tools, the bank-data providers each uses, prices and whether they link investment accounts.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_institutions ~109

Search 8,500+ US banks, credit unions and brokerages by name (and optionally city). Returns matches with their Plaid status and page URLs, largest institutions first.

NameTypeReqDescription
kindstring–Only return this kind of institution.
limitinteger––
querystringyesName, brand or "name city", at least 2 characters.
statestring–Two-letter US state code, e.g. "TX", to narrow common names.

No output schema declared.

No examples provided.

Install

How do I install the PlugCat MCP server?

PlugCat is a hosted endpoint at https://plugcat.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · plugcat.com

# add to Claude Code
claude mcp add --transport http com-plugcat-plugcat 'https://plugcat.com/mcp'
Common questions

What is the PlugCat MCP server?

PlugCat is an MCP server listed in the public MCP registry as com.plugcat/plugcat. Check if a US bank, credit union or brokerage connects to Monarch, YNAB and other finance apps. This page covers its hosted endpoint (https://plugcat.com/mcp).

Is the PlugCat MCP server safe to use?

PlugCat scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the PlugCat MCP server expose?

PlugCat exposes 4 tools: check_institution, search_institutions, get_institution, list_apps. Their descriptions and schemas cost roughly 414 tokens of context every time the server is loaded.

Does the PlugCat MCP server require authentication?

No. We connected to PlugCat without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the PlugCat MCP server still maintained?

PlugCat is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.