A
licenseNot graded
qualityB
maintenanceAn MCP server for searching current class-action settlement records by keywords and structured filters, retrieving settlement details, and performing batch searches to identify plausible claim matches.
MIT
FoundMoney
Server Details
Search open US class-action settlements to claim + official free state unclaimed-money portals.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Available Tools
2 toolssearch_settlementsAInspect
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.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results (default 20, max 100). | |
| keyword | No | Company/brand or topic to match, e.g. 'Equifax' or 'breach'. | |
| category | No | Category slug filter, e.g. 'data-breach', 'privacy', 'junk-fees', 'auto-vehicle'. | |
| noProofOnly | No | If true, only return settlements that appear to need no purchase proof. |
TDQS
A4.4/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It discloses that only currently-open settlements are returned, sorted by soonest deadline, and lists exact return fields (payout, deadline, days-left, etc.). This gives good behavioral insight for a search tool. No mention of destructive behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Four sentences with no redundancy: first states purpose and scope, second explains available filters, third specifies return data and sorting, fourth gives a concrete use case. Every sentence adds value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the description explains return fields and sorting. It covers filters and purpose. Missing details like pagination or error handling, but for a straightforward search tool it is sufficiently complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so parameters are already documented. The description adds value by explaining that 'keyword' matches company/brand, 'category' uses slugs like 'data-breach', and 'noProofOnly' filters by proof requirement. It does not mention 'limit' but that is covered by schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Search' and the resource 'currently-open US class-action settlements'. It specifies the scope (US, class-action, free) and distinguishes from the sibling tool 'unclaimed_money_portal' by focusing on settlements specifically.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description includes 'Use to find money a user may be owed' as a usage guideline. It implies when to use (when looking for free, open settlements) but does not explicitly state when not to use or compare with the sibling tool. The context is clear but lacks explicit alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
unclaimed_money_portalAInspect
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.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| state | Yes | State name or 2-letter code, e.g. 'Texas' or 'TX'. |
TDQS
A3.7/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description lacks behavioral details such as return format, authentication requirements, rate limits, or side effects. For an unannotated tool, this is a significant gap.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two concise sentences that immediately state the purpose and use case, with no unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema or annotations, the description does not specify what the tool returns (e.g., a URL, HTML page, or structured data). While the purpose is clear, an agent lacks full context on how to process the result.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema covers the single parameter 'state' with full description. The description adds minimal value by mentioning 'US state' and the national link, but the schema already explains the parameter sufficiently, meeting the baseline for 100% coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool retrieves official unclaimed property search portals for US states and the national NAUPA/missingmoney.com link, effectively differentiating from sibling tool 'search_settlements' which handles settlements.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly says 'Use to direct someone to where they can search', providing a clear usage scenario. It does not explicitly state when not to use or compare to sibling, but the purpose naturally excludes settlement searches.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user or an account that owns the GitHub organization, then choose Claim with GitHub.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
Search current class-action settlements and identify possible matches using structured filters.
Find evidence-backed U.S. free trials and savings; public benefits are available by explicit scope.
Informational Q&A: money owed to consumers (deposits, claims, unclaimed funds). No debt relief.
Search verified-open US grants (federal, state, foundation). Read-only MCP for AI agents.
Related MCP Servers
- FlicenseAqualityBmaintenanceSearches US colleges and scholarships using government data, enabling comparisons of tuition, debt, earnings, and program-specific outcomes.4
- AlicenseNot gradedqualityDmaintenanceQuery 13,000+ US consumer lenders with eligibility criteria, rates, CFPB complaints, and ratings. Find matching lenders by borrower profile, get full profiles, compare lenders, and check eligibility.MIT
CourtAPI MCP Serverofficial
AlicenseAqualityDmaintenanceSearch and retrieve US federal court cases, dockets, claims, and documents via PACER — directly from Claude and other MCP-compatible AI assistants.1060MIT
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.9/5.0
Disambiguation5/5
The two tools have completely distinct purposes: one searches active class-action settlements, the other provides links to state unclaimed property portals. There is no ambiguity between them.
Naming Consistency5/5
Both tool names use snake_case and are descriptive of their functions (search_settlements, unclaimed_money_portal), maintaining a consistent style.
Tool Count3/5
With only 2 tools, the server feels thin for a domain like 'found money.' It covers two basic needs but lacks auxiliary tools (e.g., for claims or direct searches), though the count is not extreme.
Completeness2/5
The server only provides search for settlements and portal links for unclaimed property, omitting any tool for actual claims or direct searches within state databases. Users must leave the MCP to complete even basic workflows.