
Djd Agent Score
io.github.jacobsd32-cpuPublished by GitHub account jacobsd32-cpuv1.0.1Updated Oct 24, 2026
Reputation scoring for AI agent wallets on Base. Trust scores, fraud checks, x402.
Overview
Wraps the DJD Agent Score API as MCP tools so an assistant can look up reputation scores, fraud reports and leaderboards for AI agent wallets on Base.
- What you can do
- Look up wallet reputation: basic score with tier and confidence, full dimension breakdown, and re-scoring with fresh chain data
- Check fraud data: query the fraud blacklist and submit fraud reports
- Browse public data: top-scored wallet leaderboard, embeddable SVG badge, and system health status
- Register an agent wallet with metadata
- When to use it
- Useful when an assistant needs to judge whether an AI agent wallet on Base looks trustworthy before interacting with it, or when it must check or file fraud reports and compare wallets on a leaderboard.
- Requirements
- Runs locally via npm or npx (Node.js). No authentication is declared. Optional environment variables DJD_BASE_URL (defaults to the hosted production API) and DJD_TIMEOUT_MS; TRANSPORT and PORT for HTTP mode. Network access to the DJD API is required.
Installation
In SourceWeft
- Open Djd Agent Score in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
djd-agent-score-mcp
MCP server for DJD Agent Score — a reputation scoring API for AI agent wallets on Base.
[Listed in the Coinbase x402 Ecosystem] [npm version]
This server exposes the DJD Agent Score REST API as Model Context Protocol tools, so any MCP-compatible agent (Claude, GPT, Gemini, LangChain, etc.) can call scoring endpoints natively.
Tools
Installation
Or run directly with npx:
Configuration
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
Cursor
Add to .cursor/mcp.json in your project root:
Claude Code
Add to your project's .mcp.json:
Generic MCP Client (Streamable HTTP)
Start the server in HTTP mode:
Then connect your MCP client to http://localhost:3000/mcp.
Environment Variables
Development
To point at a local API during development:
x402 Payment
Some endpoints require x402 micropayments. When an agent calls a paid tool, the API responds with HTTP 402 and payment instructions. Your agent framework must:
- Detect the 402 response
- Complete the x402 payment (USDC on Base)
- Retry the request with the payment proof
The MCP server surfaces the 402 details in the tool's error response so the agent can handle it.
License
MIT
Source: README.md at commit bbfe0af
Tools
0Version history
1- v1.0.1LatestSep 16, 2026
Score
50% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 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