
Revnuvo Trust
io.github.hardeyhemyPublished by GitHub account hardeyhemyv0.1.1Updated Oct 24, 2026
Verify companies, domains and counterparties before transacting. Sanctions, UBO, fraud scoring.
Overview
Lets an assistant verify companies, domains and counterparties, including sanctions, beneficial-ownership and fraud-scoring checks, before a transaction.
- What you can do
- Revnuvo Trust is a verification service exposed as an MCP server. According to its registry description, it lets an assistant check companies, domains and counterparties before transacting, covering sanctions screening, ultimate beneficial ownership (UBO) and fraud scoring. The manifest does not list individual tools, so the exact call names and output formats are not documented here.
- When to use it
- Worth adding when an assistant needs to screen a business partner, vendor, domain or counterparty as part of onboarding, due diligence or pre-payment checks. Less useful if you only need general web research rather than structured sanctions, ownership or fraud signals.
- Requirements
- Can be used as a remote streamable HTTP endpoint or as a local npm package (revnuvo-trust-mcp) over stdio. An API key is supplied through the environment variable REVNUVO_API_KEY; the manifest marks it optional, since x402 pay-per-call is used when it is omitted. Network access to the provider's API is required.
Installation
In SourceWeft
- Open Revnuvo Trust 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.hardeyhemy%2Frevnuvo-trust-mcp/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": {
"revnuvo-trust": {
"type": "http",
"url": "https://api.revnuvo.site/mcp"
}
}
}Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
60% 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
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.