MCP servers › io.github.jukky-source › wealth-agent
MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23
io.github.jukky-source/wealth-agent
x402 pay-per-call tools for AI agents: code review, data clean, briefs, regex, diff, URL meta. — the publisher's description
Summary
io.github.jukky-source/wealth-agent is a remote MCP server listed in the official MCP registry at version 1.0.2. On 2026-10-23 ProtocolProbe connected to it in read-only mode and read its inventory: 35 tools, 0 resources and 0 prompts.
Record checks
4 of 5 record checks met · 4 do not apply
- met: Registry entry is active and says how to run it
- met: Source repository link opens
- met: Repository is not archived
- met: Code pushed to the repository in the 90 days before our check
- not met: Repository publishes a security policy (SECURITY.md)
- not applicable: Package names its licence with a standard (SPDX) identifier
- not applicable: The version the registry lists can be installed and is not withdrawn
- not applicable: npm package carries build provenance (attestation)
- not applicable: No known critical or high advisory in the package or its dependencies
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: 0 stars (ranked from 10)
From public records, not a safety rating. Each check with its reason · Is it safe to install?
Key facts
- Runs
- remote (hosted by the publisher)
- Transport
- streamable HTTP
- Sign-in
- none needed to open a session
- Repository
- public
- Tools
- 35
- Described as changing data
- 11 of 35 toolsAI-classified
- Topic
- developer-toolsAI-classified
- Last tested
- 2026-10-23
Worth knowing before you connect it
- 11 tools are described as changing something (buy_research_brief, buy_data_clean, buy_code_review, …): our AI model's reading of the descriptions, not something we tested, and the server opened a session without any credential. We did not call them.
Each line comes from a section below, with its source and date.
How fresh this is
- Live-tested
- yes, a real session (not a text-only review)
- Last tested
- 2026-10-23
- Mode
- read-only (no tool calls)
- Latest version
- 1.0.2, published 2026-10-18 (registry, as of the 2026-10-23 snapshot)
- First listed version
- 2026-10-16 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 3 versions listed, 2026-10-16 to 2026-10-18; 3 in the 90 days before the 2026-10-23 snapshot.(versions still listed in the registry only)
Most recent 3 versions
1.0.2· 2026-10-181.0.1· 2026-10-181.0.0· 2026-10-16
- Registry data
- snapshot 2026-10-23
- Package and repository
- checked 2026-10-23
- Engine
- mcp-runtime-engine@0.1.0 · sdk@1.32.0
Changes since the last refresh
New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 1.0.2 (published 2026-10-18).
Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.
What it is
What does this server offer?
Observed inventory11 of 35 tools are described as changing something (creating, editing, deleting, sending or running).
“Spot prices for up to 10 crypto symbols in one call, quoted in the currency you name (default USD).”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
Takes no inputs.
“Foreign-exchange reference rates for a base currency and up to 12 target currencies, with the reference date and the source that answered.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
Takes no inputs.
- defi-tvlreads or searches
“Total value locked read from DefiLlama: pass a protocol slug (for example aave) for that protocol TVL, or omit it to get the top chains ranked by TVL, or filter by one chain.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
Takes no inputs.
“Resolve one hostname for one record type (A, AAAA, MX, TXT, NS, CNAME, SOA, CAA) over DNS-over-HTTPS, returning every record with its TTL, the resolver that answered and the DNS response code.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
Takes no inputs.
- crypto-hashcalculates or converts
“Deterministic hashing on the server: SHA-256, SHA-384, SHA-512 or SHA-1 over your text, or HMAC with the same digests when you pass a key.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
Takes no inputs.
- time-convertcalculates or converts
“Convert one instant into the local time of up to 12 IANA time zones at once, with the UTC offset in minutes for each, plus the Unix seconds and the canonical ISO-8601 UTC form.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
Takes no inputs.
- diligence-packreads or searches
“One call, one consolidated due-diligence pack: (1) a read-only capability map of one public website or API - entry points, forms, MCP tools, auth behaviour, with the evidence behind every claim; (2) …”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
Takes no inputs.
- buy_research_briefgenerates contentdescribed as changing data
“Returns a one-page research brief with cited source URLs, key findings and open gaps for a question.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
1 input, 1 required
questionstringrequired“The question to research (5-400 chars, any language)”
- buy_data_cleancalculates or convertsdescribed as changing data
“Cleans a CSV/TSV/JSON table: removes duplicate and empty rows, trims whitespace, and returns the cleaned CSV with before/after quality checks and per-column stats.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
2 inputs, 1 required
datastringrequired“Table as CSV / TSV text or a JSON array of objects (max 60,000 chars)”formatstring“Optional input format; auto-detected when omitted”
- buy_code_reviewcalculates or convertsdescribed as changing data
“Reviews source code and returns line-numbered findings with severity and a concrete fix, combining deterministic static rules (eval, SQL concat, secrets, shell injection) with an AI review.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
2 inputs, 1 required
codestringrequired“Source code to review (10-60,000 chars)”languagestring“Optional language hint, e.g.”
- url-metareads or searchesdescribed as changing data
“Fetch one public URL and return machine-readable page metadata: HTTP status, title, meta/og description, canonical URL, language, link count and a short text sample.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
1 input, 1 required
urlstringrequired“Absolute http(s) URL of a public page”
- csv-jsoncalculates or convertsdescribed as changing data
“Convert tabular data between CSV/TSV and a JSON array of objects, in either direction, with detected delimiter and typed columns.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
2 inputs, 1 required
datastringrequired“CSV/TSV text or a JSON array of objects”tostring“Target format (optional; inferred when omitted)”
Show 23 more tools
“Apply one regular expression to a text blob on the server and return every match with its index and capture groups.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
3 inputs, 2 required
patternstringrequired“Regular expression (max 200 chars)”textstringrequired“Text to search (max 20,000 chars)”flagsstring“g, i, m, s, u, y (optional)”
- randomon 6 other servers
“Generate verifiable random values: up to 64 integers in a range, or a fair pick of n items from your own list, derived from a drand League of Entropy beacon round and returned together with the round…”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
6 inputs
ninteger“How many values to draw (1-64, default 1)”mininteger“Inclusive lower bound of the integer range (default 0)”maxinteger“Inclusive upper bound of the integer range (default 1000000)”choicesarray“Optional: draw n distinct items from this list instead of integers (max 64)”saltstring“Optional string mixed into the derivation so two callers get different draws from the same beacon round”roundinteger“Optional: pin a past drand round instead of the latest”
- onchain-balancereads or searches
“Read one EVM address and return its native coin balance and up to five ERC-20 token balances on Base or Ethereum, every figure tied to the block height it was read at.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
3 inputs, 1 required
addressstringrequired“EVM address to read, 0x + 40 hex chars”chainstring“Which chain to read (default base)”tokensarray“Optional ERC-20 contract addresses (0x + 40 hex) to read balances for, max 5”
“Return the line-level diff between two texts as added/removed/unified hunks with counts.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
2 inputs, 2 required
astringrequired“Original text”bstringrequired“Changed text”
- buy_rea_reportreads or searchesdescribed as changing data
“Full-surface analysis of a public website, API or shipped JS bundle: maps the capabilities it exposes, its entry points and feature flags, with the evidence behind every claim, and lists what could n…”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
3 inputs
urlstring“Public https URL to analyze (website, API or MCP server)”targetstring“Alternative: a local file path (app.asar, *.exe, *.so, *.apk).”focusstring“Optional: what you want to learn, e.g.”
- buy_surface_reportreads or searchesdescribed as changing data
“Inspect one publicly reachable website or API and return a machine-readable capability report: the entry points it exposes (endpoints, forms, feeds, MCP tools), the evidence behind every finding, and…”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
2 inputs, 1 required
urlstringrequired“Public https URL to inspect (site root or any public page on it)”focusstring“Optional: what you want to learn”
“Translate one block of text into a target language using Cloudflare Workers AI.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
Takes no inputs.
“Summarize one block of text into a short bullet list using Cloudflare Workers AI.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
Takes no inputs.
“Extract named entities from one block of text using Cloudflare Workers AI.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
Takes no inputs.
“Extract the main keywords or tags from one block of text using Cloudflare Workers AI.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
Takes no inputs.
- seo-auditreads or searches
“Audit one public page for on-page SEO: title and meta description length, canonical, robots meta, heading structure, missing image alt text, lang, viewport, https, robots.txt and sitemap.xml presence…”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
Takes no inputs.
- perk_deadlinesreads or searches
“日本のお得情報（特典・ポイント還元・キャンペーン）を締切が近い順に返す。実額・期限・出典URLつき。【無料】最大5件。全件と条件・手順・人の操作が必要な部分は /api/perks（オーナー向け）。”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs
within_daysnumber“何日以内の締切を返すか（既定7・最大60）”limitnumber“件数（既定5・最大5）”
- perk_searchreads or searches
“日本のお得情報を本文から検索して返す（実額・期限・出典URLつき）。【無料】最大5件。”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
qstringrequired“検索語（例: Google Play, ローソン, ポイント還元）”limitnumber“件数（既定5・最大5）”
- rea_inspectreads or searches
“REA: 対象の「表面」を解析し、できること（根拠つき）と入口の候補と、分からなかったことを返す。URL ならサイト/API/MCP を、ローカルのパス（.asar/.exe/.so/.apk 等）なら実行手順を返す。【無料】要約版。全件＋根拠の全文は buy_rea_report（0.5 USDC）。認証回避・課金回避・DRM解除はしない。”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs
urlstring“公開URL（サイト・API・MCP）”targetstring“ローカルのパス。Worker では実行できないので手順を返す”
- rea_planreads or searches
“REA: ローカルのファイル種別（elf / pe / macho / asar / apk / jar / js）ごとの解析手順を、実行せずに返す。【無料】実行するのは手元の tools/rea-cli.mjs。”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
kindstring“elf / pe / macho / asar / apk / jar / js / unknown”
- rea_runsreads or searches
“REA: 直近の解析の状態遷移（queued → fetching → parsing → probing → evidence → done/blocked）を返す。【無料】観測用。”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
limitnumber“件数（既定20・最大50）”
“このエージェントの収益ファネル（拾う→試す→生きていると確認→売り物→掲置→来訪→支払い）を実測値で返し、どこで詰まっているかと次に打つ手を示す。【無料】”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
- rea_queuereads or searches
“REA の自動投入キュー（X / Reddit / scout / perks から拾った解析対象）の件数と直近の結果を返す。【無料】”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
limitnumber“件数（既定10・最大20）”
- surface_inspectreads or searches
“公開URLを解析し、そのサービスが公開している入口（エンドポイント候補・フォーム・フィード・MCPツール）と根拠、そして分からなかったことを返す。【無料】要約版。全件＋根拠の全文は buy_surface_report（0.25 USDC）。認証回避はしない。”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
1 input, 1 required
urlstringrequired“公開 https URL”
- lab_loopreads or searchesdescribed as changing data
“FX論理の試行錯誤ループ（無料）。状態では「今ぶつかっている壁」と「次の打ち手」を返し、run:true でその場で1ラウンド回して結果を記録する。”
Publisher declares: read-only no
2 inputs
modestring“own=自己資金 / e8=E8チャレンジ（既定 own）”runboolean“true で1ラウンド実行（既定は状態のみ）”
- improve_statusreads or searches
“全般の改善ループの状態（無料）。レーンごとの壁・打ち手・判定と、直近の記録を返す。”
Publisher declares: read-only yes
Takes no inputs.
- improve_rounddescribed as changing data
“全般の改善ループをその場で回す（無料）。lane を指定しなければカーソル順に n レーン回す。”
Publisher declares: read-only no
2 inputs
lanestring“fx / funnel / playbook / perks / rea / discovery / catalog”nnumber“回すレーン数（既定1）”
“販売中の有料サービスと価格・支払い条件の一覧（無料）”
Publisher declares: read-only yes
Takes no inputs.
Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.
How well are its tools described?
Features #4 and #5
How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.
Descriptions
AI reading of each description
- Says what the tool does
- 100% of 35 tools
- Says what it returns
- 100% of 35 tools
- States limits, defaults or errors
- 100% of 35 tools
- Says when to use it
- 100% of 35 tools
- Items covered per tool
- 4.0 of 4 on average
Counted from the listing
- Parameters with a description
- 100% of 41
- Tools with a description
- 100% of 35
- Typical description length
- 381 characters
The tool set
Counted from the listing
- Tools
- 35
- Size of the list
- about 6,470 tokens for an agent to load (characters ÷ 4)
- Naming
- 17 of 35 names use snake_case
AI reading: easy to mix up
No pair found.
The AI items cover 35 of 35 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.
How do I add it to my client?
Config from the registry entry
From the remote endpoint (Streamable HTTP)
We connected to this URL on 2026-10-23 (a read-only session: no tool was called).
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.
Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste: https://wealth-agent.wealthagent-app.workers.dev/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"wealth-agent": {
"url": "https://wealth-agent.wealthagent-app.workers.dev/mcp"
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"wealth-agent": {
"type": "http",
"url": "https://wealth-agent.wealthagent-app.workers.dev/mcp"
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"wealth-agent","type":"http","url":"https://wealth-agent.wealthagent-app.workers.dev/mcp"}'Claude Code
claude mcp add --transport http wealth-agent https://wealth-agent.wealthagent-app.workers.dev/mcp
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://wealth-agent.wealthagent-app.workers.dev/mcp --transport http
- The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
Does the registry listing match what we found?
Feature #6The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Remote endpoint wealth-agent.wealthagent-app.workers.dev/mcp | Session opened | matches | our test · 2026-10-23 |
| No credential declared as required | Opened a session without any credential | matches | our test · 2026-10-23 |
| Repository github.com/jukky-source/wealth-agent | Opens publicly | matches | api.github.com · 2026-10-23 |
Who made it?
Feature #7 · lineage
Facts about the publisher. We do not turn them into a trust score.
- Namespace
- io.github.jukky-source
- GitHub owner
- a personal account (jukky-source)
- Repository
- github.com/jukky-source/wealth-agent
- Stars
- 0
- Repository age
- 0–30 days
- Last push
- 0–30 days ago
- Archived
- no
- Security policy
- none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)
Source: the registry entry and api.github.com · 2026-10-23; security policy read from GitHub · 2026-10-23.
Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.
Choosing
Record checks
Public records · not a safety rating4 of 5 record checks met · 4 do not apply
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: 0 stars (ranked from 10)
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- MetSource repository link opensThe linked GitHub repository is public.
- MetRepository is not archivedNot archived.
- MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
- Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.
- Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
- Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
- Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
- Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards
Common questions about io.github.jukky-source/wealth-agent
Answered from the data aboveIs io.github.jukky-source/wealth-agent safe to install?
We do not rate servers as safe or unsafe. 4 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. 11 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.
Does io.github.jukky-source/wealth-agent need an API key or sign-in?
It opened a session without any credential on 2026-10-23. The registry entry declares no required credential; no declaration is not a guarantee.
Has io.github.jukky-source/wealth-agent been security tested?
Partly. 2 of the 14 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security verdict is published before verification.
What can io.github.jukky-source/wealth-agent do?
It lists 35 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search, generate content and calculate or convert. We did not call any tool, so this describes the text, not the behaviour.
Can io.github.jukky-source/wealth-agent change or delete data?
11 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.
Does io.github.jukky-source/wealth-agent publish a security policy?
We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.
Where is the source code of io.github.jukky-source/wealth-agent?
In github.com/jukky-source/wealth-agent, which opens publicly.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Similar servers
Same topic · AI-read
- io.github.SceneView/mcpalso has tools that calculates or converts, generates content, reads or searchescompare with this one
- io.github.sceneview/mcpalso has tools that calculates or converts, generates content, reads or searchescompare with this one
- io.github.tomyud1/godot-mcpalso has tools that calculates or converts, generates content, reads or searchescompare with this one
- dev.svelte/mcpSvelte MCPalso has tools that calculates or converts, generates content, reads or searchescompare with this one
- io.github.pglejzer/timepicker-ui-mcpalso has tools that calculates or converts, generates content, reads or searchescompare with this one
- io.github.bourhaouta/tailwindshadesTailwind Shadesalso has tools that calculates or converts, generates content, reads or searchescompare with this one
Active servers whose topic is also “developer-tools” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
What did we test, and what did we leave out?
18 checks · features #1, #2
Not probed (we call no server's tools)
We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.
- Inventory: exercised
- Hidden instructions: exercised
- Real execution: not run · our policy
- Secret leak: not run · nothing to check it against
- Internal addresses: not run · our policy
- Unconfirmed changes: not run · our policy
- Bad input: not run · our policy
- Model requests: not run · nothing to check it against
- Sensitive questions: not run · nothing to check it against
- Folder boundary: not run · our policy
- Log leaks: not run · nothing to check it against
- Hidden content: not run · nothing to check it against
- Fake assistant turns: not applicable
- Token passthrough: not applicable
- Token audience: not applicable
- Sign-in redirect: not run · our policy
- Consent handling: not testable from outside
- Sign-in metadata: not applicable
2 exercised12 not run (reason given)4 not applicable
Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.
- 1Inventory
tool-listReads the declared tools, resources and prompts.exercised - 2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
- 3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against - 16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy - 17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
- 13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable - 14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable - 15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable - 18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable
Source: our own test, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.
What happened during the test?
Feature #8
The steps in order, as the test record holds them.
- 0 msStarted a read-only session with the server's remote endpoint
- 270 msConnected after 0 redirects. No credential was sent or needed.
- Read the inventory: 35 tools, 0 resources, 0 prompts.
- 1,394 msFinished: 2 checks exercised.
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “io.github.jukky-source/wealth-agent: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.jukky-source/wealth-agent
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/io.github.jukky-source/wealth-agent)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.
Write to hello@protocolprobe.com · corrections log · methodology