io.github.leohoudinisanders-byte/forensics-mcp
REMOTE · SOLENE-FA2010DA.BASE44.APP
x402-payable on-chain forensics tools: token verdicts, settle-safe RWA screens, wallet trust screens
Available components
Last scanned (1 hour ago)
Scores higher than 47% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Crypto and Web3
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 Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 783 tokens (~130/item across 6 items; 6 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 Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 58% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
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.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 20 Oct 26 62
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 23 Oct 2026 · Probed https://solene-fa2010da.base44.app/functions/forensicsMcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.base44.app | CN=YR2,O=Let's Encrypt,C=US | 12 Sept 2026 | 11 Dec 2026 | RSA 2048 | SHA256-RSA | 5b99279f037a30a0bbe8d284eab58237ba3 |
| SANs: *.base44.app, base44.app | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of solene-fa2010da.base44.app. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| base44.app. | present | 2371 | 13 | Verified |
| solene-fa2010da.base44.app. | Verified address RRset verified with the apex keys |
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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| content-security-policy | script-src 'none'; object-src 'none'; |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://solene-fa2010da.base44.app/functions/forensicsMcp | Verified | 200 | |
| http (plaintext) | http://solene-fa2010da.base44.app/functions/forensicsMcp | HTTPS enforced | 301 | https://solene-fa2010da.base44.app/functions/forensicsMcp |
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 →
diligence_memo ~132
$0.25 composed Token Due-Diligence Memo (decision-grade, reproducible, no LLM calls): verdict + supply/flow forensics + settle-safe screen + narrative risk assessment. $0.35 when counterparty is provided (adds the settlement counterparty trust screen). EVM or XRPL.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | – |
| chain | string | – | – |
| counterparty | string | – | optional settlement counterparty (adds trust screen, +$0.10) |
| currency | string | – | XRPL currency code (chain=xrp) |
| token | string | – | token alias |
No output schema declared.
No examples provided.
forensics_info ~65
FREE. Service directory for the On-chain Forensics MCP server: endpoint catalog, chains supported (Base, Ethereum, XRPL), pricing, tokenized-equity aliases (btsla, bcspx, rlusd, bitstamp-usd, ...) and usage examples.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
settle_safe ~180
$0.02. FLAGSHIP pre-trade settle-safe screen for AI agents trading tokenized equities/RWAs: canonical-asset check against the verified registry (EVM: btsla/bcspx/bnvda/aapl/nvda/usdy/ousg/...; XRPL issuers: rlusd, gatehub-usd, bitstamp-usd/eur), freeze/clawback flags, trustline breadth, optional counterparty wallet trust tier.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | EVM token contract or XRPL issuer |
| chain | string | – | – |
| counterparty | string | – | optional settlement counterparty wallet to trust-screen |
| currency | string | – | XRPL currency code (chain=xrp) |
| token | string | – | token alias (btsla, rlusd, bitstamp-usd, ...) |
No output schema declared.
No examples provided.
token_profile ~80
$0.05. Full ERC-20 forensics profile on Base or Ethereum: exact 24h net supply change, recent mint/burn events, holder concentration, top transfers, whale moves.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | – |
| chain | string | – | – |
| token | string | – | token alias (ondo, edel, buidl, ...) |
No output schema declared.
No examples provided.
token_verdict ~200
$0.02. Token verdict card for any ERC-20 on Base or Ethereum (address+chain), any registered alias (token=btsla|ondo|edel|...), or any XRPL issued currency (chain=xrp + issuer + currency): activity score 0-100, verdict tier (RED_HOT/HEAVY_FIRE/ACTIVE/THIN/SUSPICIOUS_THIN/DORMANT), transfers, unique wallets, mints/burns, concentration, whale flags, plain-English take.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | EVM token contract (0x...) or XRPL issuer (r...) |
| chain | string | – | – |
| currency | string | – | XRPL issued-currency code (3 letters or 40-char hex), for chain=xrp |
| token | string | – | token alias (btsla, bcspx, ondo, edel, rlusd, bitstamp-usd, ...) |
No output schema declared.
No examples provided.
wallet_screen ~74
$0.05. Wallet trust screen for any wallet on Base, Ethereum or XRPL (chain=xrp): balance, tx count, flows, top counterparties, contract-interaction risk, trust tier. For XRPL also trustlines and issuer screens.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| chain | string | – | – |
No output schema declared.
No examples provided.
How do I install the io.github.leohoudinisanders-byte/forensics-mcp server?
io.github.leohoudinisanders-byte/forensics-mcp is a hosted endpoint at https://solene-fa2010da.base44.app/functions/forensicsMcp, 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 · solene-fa2010da.base44.app
claude mcp add --transport http leohoudinisanders-byte-forensics-mcp 'https://solene-fa2010da.base44.app/functions/forensicsMcp'
What is the io.github.leohoudinisanders-byte/forensics-mcp server?
io.github.leohoudinisanders-byte/forensics-mcp is listed in the public MCP registry as io.github.leohoudinisanders-byte/forensics-mcp. x402-payable on-chain forensics tools: token verdicts, settle-safe RWA screens, wallet trust screens. This page covers its hosted endpoint (https://solene-fa2010da.base44.app/functions/forensicsMcp).
Is the io.github.leohoudinisanders-byte/forensics-mcp server safe to use?
io.github.leohoudinisanders-byte/forensics-mcp scores 63 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 io.github.leohoudinisanders-byte/forensics-mcp server expose?
io.github.leohoudinisanders-byte/forensics-mcp exposes 6 tools: forensics_info, token_verdict, settle_safe, wallet_screen, token_profile, diligence_memo. Their descriptions and schemas cost roughly 731 tokens of context every time the server is loaded.
Does the io.github.leohoudinisanders-byte/forensics-mcp server require authentication?
No. We connected to io.github.leohoudinisanders-byte/forensics-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.leohoudinisanders-byte/forensics-mcp server still maintained?
io.github.leohoudinisanders-byte/forensics-mcp is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.