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.

FoundMoney

REMOTE · FOUND-MONEY.DROPWATCHHQ.COM

Search open US class-action settlements to claim + official free state unclaimed-money portals.

0 this week 72 Trust /100

Last scanned (13 hours ago)

Scores higher than 58% 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 Security46
Transport & Reachability100
Schema Quality & AI Usability83
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 273 tokens (~136/item across 2 items; 2 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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://found-money.dropwatchhq.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=dropwatchhq.com CN=WE1,O=Google Trust Services,C=US 18 Oct 2026 16 Jan 2027 ECDSA 256 ECDSA-SHA256 b5697f39d821b0de130d39f62912d88d
SANs: dropwatchhq.com, found-money.dropwatchhq.com, *.found-money.dropwatchhq.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 found-money.dropwatchhq.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
dropwatchhq.com. No DS 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://found-money.dropwatchhq.com/mcp Verified 200
http (plaintext) http://found-money.dropwatchhq.com/mcp Served over HTTP 200
MCP tools · 2 exposed · ~273 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
search_settlements ~189

Search currently-open US class-action settlements you may be able to claim for free. Filter by keyword (company/brand), category (e.g. data-breach, privacy, junk-fees), and whether proof is required. Returns each settlement's payout, claim deadline, days-left, proof requirement, category, and official claim URL. Sorted by soonest deadline. Use to find money a user may be owed.

NameTypeReqDescription
categorystring–Category slug filter, e.g. 'data-breach', 'privacy', 'junk-fees', 'auto-vehicle'.
keywordstring–Company/brand or topic to match, e.g. 'Equifax' or 'breach'.
limitnumber–Max results (default 20, max 100).
noProofOnlyboolean–If true, only return settlements that appear to need no purchase proof.

No output schema declared.

No examples provided.

unclaimed_money_portal ~84

Get the official, free unclaimed-property (unclaimed money) search portal for a US state plus the national NAUPA/missingmoney.com link. Use to direct someone to where they can search for forgotten bank accounts, refunds, etc.

NameTypeReqDescription
statestringyesState name or 2-letter code, e.g. 'Texas' or 'TX'.

No output schema declared.

No examples provided.

Install

How do I install the FoundMoney MCP server?

FoundMoney is a hosted endpoint at https://found-money.dropwatchhq.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 · found-money.dropwatchhq.com

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

What is the FoundMoney MCP server?

FoundMoney is an MCP server listed in the public MCP registry as com.dropwatchhq/found-money. Search open US class-action settlements to claim + official free state unclaimed-money portals. This page covers its hosted endpoint (https://found-money.dropwatchhq.com/mcp).

Is the FoundMoney MCP server safe to use?

FoundMoney scores 72 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 FoundMoney MCP server expose?

FoundMoney exposes 2 tools: search_settlements, unclaimed_money_portal. Their descriptions and schemas cost roughly 273 tokens of context every time the server is loaded.

Does the FoundMoney MCP server require authentication?

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

Is the FoundMoney MCP server still maintained?

FoundMoney 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.

What did VerifyMCP test on the FoundMoney MCP server?

VerifyMCP ran 12 checks on FoundMoney, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about FoundMoney: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.