Nulucre Wallet Reputation MCP server
online · 100% uptimeio.github.vjshaw/nulucre-wallet-reputation·v1.1.0Wallet trust scores for AI agents. Stellar, XRPL, EVM 81+ chains. OFAC sanctions. x402 payments.
0 stars
Reviews
Write oneNobody has reviewed Nulucre Wallet Reputation yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Nulucre Wallet Reputation tools (5)
write = sends, deletes, buys or postsnulucre_check_service_statusFreeCheck whether the live Nulucre reputation oracle service is online. This is a free endpoint that requires no payment. Use this tool to verify Nulucre is reachable before relying on it for wallet scoring decisions, or for general uptime monitoring. Args: none Returns: Structured data with schema: { "status": string, // "online" if the service is reachable "service": string // service name } Examples: - Use when: "Is Nulucre up?" -> no params needed - Use when: checking service availability before a batch of scoring calls Error Handling: - Returns "Error: ..." with details if the service is unreachable
nulucre_get_evm_wallet_scoreFreeGet a 0-100 trust score for an EVM wallet address (0x...) from Nulucre, a multi-chain wallet reputation oracle covering 81+ chains. The score is computed from on-chain data including wallet age, transaction volume, DeFi activity, and multi-chain presence, pulled from Etherscan, Moralis, Alchemy, and Ankr. Use this tool to assess counterparty risk before an agent interacts with or pays an EVM wallet on Ethereum, Base, Polygon, Arbitrum, Optimism, or any of the 81+ supported chains. Args: - wallet (string): EVM wallet address starting with '0x' (42 characters) - signed (boolean): If true, request an ECDSA-P256 signed score for independent verification via Nulucre's public JWKS endpoint (default: false) - response_format ('markdown' | 'json'): Output format (default: 'markdown') Returns: For JSON format: Structured data with schema: { "wallet": string, "score": number, // 0-100 "status": string, // TRUSTED | VERIFIED | CAUTION | RISKY | BLACKLISTED "breakdown": { "<signalName>": { "score": number, "raw": string }, ... }, "chains"?: string[], "dataSource": string, "timestamp": string, "signature"?: string // present only when signed=true } Examples: - Use when: "Is this Ethereum wallet trustworthy?" -> wallet="0xabc...", signed=false - Use when: "Get a verifiable score for this 0x address" -> wallet="0xabc...", signed=true - Don't use when: scoring a Stellar G... address (use nulucre_get_stellar_wallet_score instead) Error Handling: - Returns "Error: Invalid EVM wallet address" if the address format is invalid - Returns a payment-required explanation if the free evaluation quota is exhausted
nulucre_get_solana_wallet_scoreFreeGet a 0-100 trust score for a Solana wallet address from Nulucre. Scored using 7 native Solana RPC signals: account age, transaction volume, SOL balance, token diversity, recent activity, program account status, and failed transaction ratio. Includes real-time OFAC/UN/EU sanctions screening. Use before paying or interacting with any Solana wallet. Pay per query via x402 USDC micropayments.
nulucre_get_stellar_wallet_scoreFreeGet a 0-100 trust score for a Stellar wallet address (G...) from Nulucre, a live Stellar-native wallet reputation oracle. The score is computed from 8 signals pulled directly from the Stellar Horizon API and Stellar Expert — account age, transaction volume, asset diversity, SDEX DEX participation, network trust, claimable balance activity, Soroban contract interactions, and liquidity pool participation, plus a spam detection penalty. No EVM data is used. Every score includes a real-time sanctions screening result against the OFAC SDN, OFAC Non-SDN, EU Financial Sanctions, and UN Security Council Sanctions lists. A wallet matching any of these lists automatically receives a score of 0 and status BLACKLISTED. Use this tool to assess counterparty risk before an agent interacts with or pays a Stellar wallet — for example before executing a payment, approving a swap counterparty, or evaluating a new account. Args: - g_address (string): Stellar wallet address starting with 'G' (56 characters) - signed (boolean): If true, request an ECDSA-P256 signed score for independent verification via Nulucre's public JWKS endpoint (default: false) - response_format ('markdown' | 'json'): Output format (default: 'markdown') Returns: For JSON format: Structured data with schema: { "wallet": string, "network": "stellar:pubnet", "score": number, // 0-100 "status": string, // TRUSTED | VERIFIED | CAUTION | RISKY | BLACKLISTED "breakdown": { "accountAge": { "score": number, "raw": string }, "txVolume": { "score": number, "raw": string }, "assetDiversity": { "score": number, "raw": string }, "dexParticipation": { "score": number, "raw": string }, "networkTrust": { "score": number, "raw": string }, "claimableActivity": { "score": number, "raw": string }, "sorobanUsage": { "score": number, "raw": string }, "liquidityPools": { "score": number, "raw": string }, "spamPenalty": { "score": number, "raw": string }, "sanctionsCheck": { "score": number, "raw": "CLEAR"|"SANCTIONED"|"UNCHECKED", "source": string } }, "dataSource": string, "timestamp": string, "signature"?: string // present only when signed=true } Examples: - Use when: "Is this Stellar wallet safe to pay?" -> g_address="GABC...", signed=false - Use when: "Get a verifiable score I can check independently" -> g_address="GABC...", signed=true - Don't use when: scoring an Ethereum or other EVM address (use nulucre_get_evm_wallet_score instead) Error Handling: - Returns "Error: Invalid Stellar wallet address" if the address format is invalid - Returns a payment-required explanation if the free evaluation quota is exhausted
nulucre_get_xrpl_wallet_scoreFreeGet a 0-100 trust score for an XRPL wallet address (r...) from Nulucre. Scored using 7 XRPL Ledger signals: account age, transaction volume, trustline diversity, DEX participation, network trust, payment activity, and spam detection. Includes real-time OFAC/UN/EU sanctions screening. Use before paying or interacting with any XRPL wallet.
Public scan report
scanner v0.1.10 · 2026-10-28 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 696ms20/20
- Tool poisoning5 tool descriptions checked13/15
- Auth qualityopen endpoint, read-only tools10/15
- Maintenancelast push 8 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Findings (1)
- lowUnusually long tool description (over 2,000 characters)
poison.long-descriptiontool nulucre_get_stellar_wallet_score: …Get a 0-100 trust score for a Stellar wallet address (G...) from Nulucre, a live Stellar-native wallet reputation oracle. The score is computed from 8 signals pulled directly from the Stellar Horizon API and Stellar Expert — account age, transaction volume, asset diversity, SDEX DEX participation, network trust, claimable balance activity, Soroban contract interactions, and liquidity pool participation, plus a spam detection penalty. No EVM data is used. Every score includes a real-time sanctions screening result against the OFAC SDN, OFAC Non-SDN, EU Financial Sanctions, and UN Security Council Sanctions lists. A wallet matching any of these lists automatically receives a score of 0 and status BLACKLISTED. Use this tool to assess counterparty risk before an agent interacts with or pays a Stellar wallet — for example before executing a payment, approving a swap counterparty, or evaluating a new account. Args: - g_address (string): Stellar wallet address starting with 'G' (56 characters) - signed (boolean): If true, request an ECDSA-P256 signed score for independent verification via Nulucre's public JWKS endpoint (default: false) - response_format ('markdown' | 'json'): Output format (default: 'markdown') Returns: For JSON format: Structured data with schema: { "wallet": string, "network": "stellar:pubnet", "score": number, // 0-100 "status": string, // TRUSTED | VERIFIED | CAUTION | RISKY | BLACKLISTED "breakdown": { "accountAge": { "score": number, "raw": string }, "txVolume": { "score": number, "raw": string }, "assetDiversity": { "score": number, "raw": string }, "dexParticipation": { "score": number, "raw": string }, "networkTrust": { "score": number, "raw": string }, "claimableActivity": { "score": number, "raw": string }, "sorobanUsage": { "score": number, "raw": string }, "liquidityPools": { "score": number, "raw": string }, "spamPenalty": { "score": number, "raw": string }, "sanctionsCheck": { "score": number, "raw": "CLEAR"|"SANCTIONED"|"UNCHECKED", "source": string } }, "dataSource": string, "timestamp": string, "signature"?: string // present only when signed=true } Examples: - Use when: "Is this Stellar wallet safe to pay?" -> g_address="GABC...", signed=false - Use when: "Get a verifiable score I can check independently" -> g_address="GABC...", signed=true - Don't use when: scoring an Ethereum or other EVM address (use nulucre_get_evm_wallet_score instead) Error Handling: - Returns "Error: Invalid Stellar wallet address" if the address format is invalid - Returns a payment-required explanation if the free evaluation quota is exhausted…
How Nulucre Wallet Reputation compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 88/100
- higher than 75% of 48,255 servers
- Tools
- 5
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 771 ms
- faster than 17% of 30,031 servers
What its tools let an agent do: 5 read
Install Nulucre Wallet Reputation in Claude Code, Cursor or VS Code
claude mcp add --transport http nulucre-wallet-reputation https://agents.nulucre.com/mcp
What the publisher says
From the Nulucre Wallet Reputation repository's README, as published. We do not edit it. Read it on GitHub
Nulucre Agents — Wallet Reputation Oracle for AI Agents
Real-time wallet trust scores across 4 chains, paid via x402 micropayments. No API keys, no accounts, no subscriptions — pure agent-to-agent commerce.
Base URL: https://agents.nulucre.com Methodology: https://agents.nulucre.com/methodology MCP Server: https://agents.nulucre.com/mcp
Endpoints
Payment Networks
Score Bands
Full methodology: https://agents.nulucre.com/methodology
Standard Response
{
"wallet": "0x123...abc",
"score": 74,
"status": "VERIFIED",
"network": "evm",
"breakdown": {
"walletAge": { "score": 28, "raw": "3400 days" },
"txVolume": { "score": 35, "raw": "2100 txs" },
"defiActivity": { "score": 6, "raw": "3 protocols" },
"multiChain": { "score": 5, "raw": "2 EVM chains" }
},
"timestamp": "2026-10-20T00:00:00.000Z"
}Thin-file response:
{
"wallet": "0x123...abc",
"score": null,
"status": "INSUFFICIENT_DATA",
"message": "Too few transactions to score reliably",
"timestamp": "2026-10-20T00:00:00.000Z"
}How x402 Payment Works
- Agent calls endpoint
- Server returns 402 Payment Required with payment details (Base, Stellar, or Solana)
- Agent sends USDC on chosen network
- Agent includes payment proof in next request header
- Server verifies and returns score
No accounts. No API keys. Fully autonomous.
Cryptographic Verification
Signed endpoints return an ECDSA-P256 signature verifiable against the Nulucre public key.
- JWKS: https://nulucre.com/.well-known/jwks.json
- Algorithm: ECDSA-P256 / SHA-256 / IEEE P1363
Agent Discovery
https://agents.nulucre.com/reputation/ https://nulucre.com/.well-known/agent.json https://nulucre.com/.well-known/x402.json https://nulucre.com/.well-known/jwks.json https://nulucre.com/openapi.json
Quick Start
# Free health check
curl https://agents.nulucre.com/health
# Free TVL lookup
curl https://agents.nulucre.com/tvl/aave
# EVM wallet score (requires x402 payment)
curl https://agents.nulucre.com/reputation/0xYourWalletAddress
# EVM signed score with ECDSA proof
curl https://agents.nulucre.com/reputation/signed/0xYourWalletAddress
# Stellar wallet score
curl https://agents.nulucre.com/reputation/stellar/GYourStellarAddressShortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Nulucre Wallet Reputation: common questions
- Is Nulucre Wallet Reputation MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the Nulucre Wallet Reputation safety report
- How do I install Nulucre Wallet Reputation?
- It runs remotely at agents.nulucre.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Nulucre Wallet Reputation need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Nulucre Wallet Reputation maintained?
- The last commit was 15 days ago (2026-10-20). The latest release is v1.1.0.
- Is Nulucre Wallet Reputation up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Nulucre Wallet Reputation compare with other MCP servers?
- safety score 88/100 (higher than 75% of 48,255 servers); tools 5 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.