
EuroRWA Analyst
io.github.crytobot459Published by GitHub account crytobot459v1.0.0Updated Oct 24, 2026
EuroRWA analyst: tokenized money-market fund signals, snapshots, analytics and alerts.
Overview
Remote MCP endpoint for EuroRWA research data on tokenized money-market funds, offering snapshots, signals, analytics and alerts.
- What you can do
- Retrieve daily snapshots of public tokenized money-market fund data (TVL, yield, flows, holders) across EU and US issuers.
- Get deterministic scoring and analyst-layer signals built from news, on-chain flows and macro context.
- Check snapshot attestations: keccak-256 payload hashes signed and published to a Sepolia contract, re-verifiable by anyone.
- Receive alerts and analytics derived from the collected fund data.
- When to use it
- Useful for research or analysis of tokenized money-market funds and for checking that a published fund snapshot matches its on-chain attestation. The README frames the project as study code rather than a supported product, so treat it as an experimental data source.
- Requirements
- A remote streamable HTTP endpoint; no authentication, environment variables or headers are declared. The README states the read-only REST endpoints and MCP server need no credentials. Credentialed paths described in the README (Binance signed calls, on-chain attestation) belong to the local code, not the hosted endpoint.
Installation
In SourceWeft
- Open EuroRWA Analyst in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.crytobot459%2Feurorwa-analyst/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"eurorwa-analyst": {
"type": "http",
"url": "https://rwa-dashboard-gamma.vercel.app/mcp"
}
}
}README
EuroRWA — Research Project
Independent research into public data transparency and verifiable snapshots for tokenized money-market funds (MMFs).
This repository is a research project. It studies how publicly available tokenized-MMF data can be collected, stored, and independently verified. It is provided as code and methodology for studying open financial data — not a product, service, or offering, and no hosted service, dashboard, or bot is operated here.
Free and open. The code is MIT-licensed and free to fork and use. There is no paywall and no advertising — every endpoint (REST + MCP) is open and the whole verification path runs with no credentials. The one exception is spelled out under Status: a Binance account key for signed calls, and a signing key to attest on-chain. Monetization and freelance/lead-generation features that previously existed here have been removed.
Research questions
- How can a daily fund snapshot be made independently verifiable (keccak-256 hash → signed → published on-chain)?
- What does public tokenized-MMF data look like across EU + US issuers (TVL, yield, flows, holders)?
- Can an analyst layer produce reproducible, explainable signals from that data?
What the code does
- Collect public fund data (rwa.xyz) → SQLite snapshots.
- Attest each snapshot: hash it (keccak-256), sign with a dedicated key, and publish the signature to a Sepolia contract.
- Analyze: deterministic scoring plus an analyst layer over news / on-chain flows / macro context.
- Verify: anyone can re-hash the data and check the on-chain signature.
Components
Verify an attestation
Verifies the payload hash matches the published keccak-256 and that the recovered signer is the agent wallet.
Status
Research code, provided as-is for study. No hosted service is operated.
What needs credentials, stated plainly rather than as a blanket "no keys":
So a stranger can clone this and run the whole verification path with no credentials at all. The credentialed paths are the ones that touch an account.
Compliance
Per Vietnamese law (prohibition on crypto/coin advertising and registration, effective 1 Sep 2026), this repository contains no public web dashboard and no advertising. It is distributed solely as open research code.
MIT © 2026 — data sourced from rwa.xyz public APIs. Not financial advice.
Source: README.md at commit 8fd2a95
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listedRequired15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts