KeepUp
REMOTE · API.KEEPUP.FINANCE
Net worth percentiles by country and age, and how KeepUp users compare. Read-only, no key.
Available components
Last scanned (6 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 720 tokens (~144/item across 5 items; 5 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 Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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 →
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.
- 5 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 4 Nov 26 71
First indexed and scored.
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://api.keepup.finance/mcp/connector
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=keepup.finance | CN=YE1,O=Let's Encrypt,C=US | 31 Oct 2026 | 29 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6e084ad6237222fd4a24935e437e202922b |
| SANs: *.keepup.finance, keepup.finance | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.keepup.finance. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| finance. | DS published | 28624, 46861 | 8, 8 | Verified |
| keepup.finance. | 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://api.keepup.finance/mcp/connector | Verified | 200 | |
| http (plaintext) | http://api.keepup.finance/mcp/connector | HTTPS enforced | 301 | https://api.keepup.finance/mcp/connector |
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 →
country_net_worth_thresholds Net worth thresholds by country ~104
Return the household net worth (USD) needed to reach the median and the top 25%, 10%, 5%, and 1% in a given country. Use for 'what net worth is top 1% in the UK' or to build a wealth-distribution table. Public data.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | ISO 3166-1 alpha-2 country code (e.g. US, DE, JP) or 'WORLD'. |
No output schema declared.
No examples provided.
keepup_users_net_worth How KeepUp users compare ~140
How KeepUp users compare: net worth at the 25th, 50th, 75th and 90th percentiles and the asset class most of them are led by, worldwide or in one country, optionally within an age band. Rounded group figures over users on KeepUp's public leaderboard (groups of five or more), never an individual. A self-selected group, not a whole country's population.
| Name | Type | Req | Description |
|---|---|---|---|
| age_band | string | – | Optional age band. |
| country | string | – | ISO 3166-1 alpha-2 country code (e.g. US, DE) or 'WORLD'. Omit for WORLD. |
No output schema declared.
No examples provided.
list_supported_countries Supported countries ~45
List every country KeepUp has wealth-distribution data for, with whether it has full survey breakpoints (higher precision at the tails). Call this to discover valid country codes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
net_worth_by_age Net worth by age ~164
Household net worth by age of the household head in a country: the median and the top 10% and top 1% cutoffs for each age group (under 35, 35 to 44 … 75 or older). Pass an age to single out its group. Use for 'what is the average net worth at 30', 'top 1% net worth at 40 in the US' or 'median net worth by age in Germany'. US medians are the Federal Reserve's; other countries are labeled estimates.
| Name | Type | Req | Description |
|---|---|---|---|
| age | integer | – | Optional age: marks the age group it falls in. |
| country | string | yes | ISO 3166-1 alpha-2 country code (e.g. US, DE, JP). |
No output schema declared.
No examples provided.
net_worth_percentile Net worth percentile ~181
Given a household net worth in USD and a country (and optionally the age of the household head), return the wealth percentile it falls in and the 'top X%'. Answers questions like 'what percentile is a $500k net worth in Germany', 'is $1M a lot in Japan' or 'is $200k good at 30 in the US'. Public aggregate data, no personal or account information.
| Name | Type | Req | Description |
|---|---|---|---|
| age | integer | – | Optional age of the household head: ranks the net worth among households of that age group in the country (needs a country). |
| country | string | – | ISO 3166-1 alpha-2 country code (e.g. US, DE, JP) or 'WORLD'. Omit for the worldwide distribution. |
| net_worth_usd | number | yes | Household net worth in US dollars. |
No output schema declared.
No examples provided.
How do I install the KeepUp MCP server?
KeepUp is a hosted endpoint at https://api.keepup.finance/mcp/connector, 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 · api.keepup.finance
claude mcp add --transport http finance-keepup-keepup 'https://api.keepup.finance/mcp/connector'
What is the KeepUp MCP server?
KeepUp is an MCP server listed in the public MCP registry as finance.keepup/keepup. Net worth percentiles by country and age, and how KeepUp users compare. Read-only, no key. This page covers its hosted endpoint (https://api.keepup.finance/mcp/connector).
Is the KeepUp MCP server safe to use?
KeepUp 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 KeepUp MCP server expose?
KeepUp exposes 5 tools: net_worth_percentile, country_net_worth_thresholds, net_worth_by_age, list_supported_countries, keepup_users_net_worth. Their descriptions and schemas cost roughly 634 tokens of context every time the server is loaded.
Does the KeepUp MCP server require authentication?
No. We connected to KeepUp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the KeepUp MCP server still maintained?
KeepUp 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 KeepUp MCP server?
VerifyMCP ran 13 checks on KeepUp, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.