Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.jacobsd32-cpu/djd-agent-score

NPM · DJD-AGENT-SCORE-MCP · SCANNED SEP 20

Reputation scoring for AI agent wallets on Base. Trust scores, fraud checks, x402.

Available components

+2 this week 84 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 39 of 123 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1017 tokens (~113/item across 9 items; 9 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 Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.jacobsd32-cpu/djd-agent-score MCP server?

io.github.jacobsd32-cpu/djd-agent-score runs locally as an npm package, launched with npx -y djd-agent-score-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · djd-agent-score-mcp

# add to Claude Code
claude mcp add jacobsd32-cpu-djd-agent-score -- npx -y djd-agent-score-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "jacobsd32-cpu-djd-agent-score": {
      "command": "npx",
      "args": [
        "-y",
        "djd-agent-score-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "jacobsd32-cpu-djd-agent-score": {
      "command": "npx",
      "args": [
        "-y",
        "djd-agent-score-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add jacobsd32-cpu-djd-agent-score -- npx -y djd-agent-score-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "jacobsd32-cpu-djd-agent-score": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "djd-agent-score-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add jacobsd32-cpu-djd-agent-score --command npx --arg -y --arg djd-agent-score-mcp
# ~/.hermes/config.yaml
mcp_servers:
  jacobsd32-cpu-djd-agent-score:
    command: "npx"
    args: ["-y", "djd-agent-score-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "jacobsd32-cpu-djd-agent-score": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "djd-agent-score-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add jacobsd32-cpu-djd-agent-score -t stdio -c npx -a -y djd-agent-score-mcp
// mcp.json
{
  "mcpServers": {
    "jacobsd32-cpu-djd-agent-score": {
      "command": "npx",
      "args": [
        "-y",
        "djd-agent-score-mcp"
      ]
    }
  }
}
Changelog

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.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 15 Sept 26 +2
    • CVE-2026-82562 no longer affects this package security
    • CVE-2026-82417 no longer affects this package security
    • Known CVEs: fail → pass security
    • Stability: 0.97 → pass security
    • Security disclosure: unverified → fail functional
  • 14 Sept 26 +1
    • Security disclosure: fail → unverified functional
  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 −2
    • Stability: pass → 0.80 functional
  • 8 Sept 26 0
    • Stability: 0.97 → pass security
Diagnostics

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 20 Sept 2026 · Analysed npm/djd-agent-score-mcp@1.0.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 123 packages
Packages resolved 123
Stale 39
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~1,017 tokens

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 →

Tool Tokens
check_blacklist ~84

Check if a wallet has any fraud reports filed against it. PAID endpoint — requires x402 payment ($0.05 USD). Args: - wallet (string): Ethereum wallet address to check Returns: { wallet, reported, reportCount, reports[] }

NameTypeReqDescription
walletstringyesEthereum wallet address (e.g. 0xAbC...123)

No output schema declared.

No examples provided.

get_badge ~101

Get the embeddable SVG badge URL for a wallet's reputation score. Returns the badge endpoint URL and the raw SVG content. The URL can be embedded in markdown, HTML, or any context that supports images. This is a FREE endpoint. Args: - wallet (string): Ethereum wallet address Returns: { badgeUrl, svg }

NameTypeReqDescription
walletstringyesEthereum wallet address (e.g. 0xAbC...123)

No output schema declared.

No examples provided.

get_leaderboard ~51

Get the leaderboard of top-scored AI agent wallets. Returns a ranked list of wallets with their scores and tiers. This is a FREE endpoint. Returns: Array of { wallet, score, tier }

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

health_check ~34

Check the DJD Agent Score API system status. This is a FREE endpoint. Returns: { status, version, uptime }

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

register_agent ~151

Register an AI agent wallet with metadata (name, description, optional GitHub URL). This is a FREE endpoint. Args: - wallet (string): Ethereum wallet address to register - name (string): Display name for the agent - description (string): What this agent does - github_url (string, optional): GitHub repository URL Returns: { success, message }

NameTypeReqDescription
descriptionstringyesWhat this agent does
github_urlstringGitHub repository URL for the agent (optional)
namestringyesDisplay name for the agent
walletstringyesEthereum wallet address (e.g. 0xAbC...123)

No output schema declared.

No examples provided.

report_fraud ~143

Submit a fraud report for a wallet with supporting transaction hashes and evidence. PAID endpoint — requires x402 payment ($0.02 USD). Args: - wallet (string): Ethereum wallet address of the suspected fraudster - tx_hashes (string[]): Array of transaction hashes as evidence - evidence (string): Text description of the fraudulent behavior Returns: { success, reportId, message }

NameTypeReqDescription
evidencestringyesText description of the fraudulent behavior
tx_hashesarrayyesTransaction hashes that demonstrate the fraudulent behavior
walletstringyesEthereum wallet address (e.g. 0xAbC...123)

No output schema declared.

No examples provided.

score_basic ~165

Get the basic reputation score for an AI agent wallet on Base. Returns a numeric score (0-1000), tier (e.g. "Trusted", "Neutral", "Risky"), confidence level, recommendation text, and model version. This is a FREE endpoint — no x402 payment required. Args: - wallet (string): Ethereum wallet address (0x + 40 hex chars) Returns: { score, tier, confidence, recommendation, modelVersion } Examples: - "What's the reputation of 0xABC...?" -> score_basic with that wallet - "Is this agent wallet trustworthy?" -> score_basic to get tier/recommendation

NameTypeReqDescription
walletstringyesEthereum wallet address (e.g. 0xAbC...123)

No output schema declared.

No examples provided.

score_full ~168

Get the full reputation score with dimension breakdown for an AI agent wallet. Returns everything from basic score PLUS: - dimensions: { reliability, viability, identity, capability } - integrityFlags: flags about suspicious activity - dataQuality: metrics about data completeness PAID endpoint — requires x402 payment ($0.10 USD). If your agent framework supports x402, the 402 response will contain payment instructions. Complete the payment and retry the request. Args: - wallet (string): Ethereum wallet address (0x + 40 hex chars) Returns: { score, tier, confidence, recommendation, modelVersion, dimensions, integrityFlags, dataQuality }

NameTypeReqDescription
walletstringyesEthereum wallet address (e.g. 0xAbC...123)

No output schema declared.

No examples provided.

score_refresh ~120

Force a re-score of an AI agent wallet using the latest on-chain data. Use this when you suspect the cached score is stale or after known on-chain activity that should change the score. PAID endpoint — requires x402 payment ($0.25 USD). Args: - wallet (string): Ethereum wallet address (0x + 40 hex chars) Returns: { score, tier, confidence, recommendation, modelVersion, refreshedAt }

NameTypeReqDescription
walletstringyesEthereum wallet address (e.g. 0xAbC...123)

No output schema declared.

No examples provided.

Common questions

What is the io.github.jacobsd32-cpu/djd-agent-score MCP server?

io.github.jacobsd32-cpu/djd-agent-score is an MCP server listed in the public MCP registry as io.github.jacobsd32-cpu/djd-agent-score. Reputation scoring for AI agent wallets on Base. Trust scores, fraud checks, x402. This page covers its npm package (djd-agent-score-mcp).

Is the io.github.jacobsd32-cpu/djd-agent-score MCP server safe to use?

io.github.jacobsd32-cpu/djd-agent-score scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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.jacobsd32-cpu/djd-agent-score MCP server expose?

io.github.jacobsd32-cpu/djd-agent-score exposes 9 tools: score_basic, score_full, score_refresh, report_fraud, check_blacklist, and 4 more. Their descriptions and schemas cost roughly 1,017 tokens of context every time the server is loaded.

Is the io.github.jacobsd32-cpu/djd-agent-score MCP server still maintained?

io.github.jacobsd32-cpu/djd-agent-score is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.jacobsd32-cpu/djd-agent-score MCP server under?

io.github.jacobsd32-cpu/djd-agent-score declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.