Skip to main content
Glama
verdict-finance-mcp

verdict-finance-mcp

Official

verdict-finance-mcp

Verdict is the security marketplace for DeFi. Firms bid on audits and pen tests; scanning, RPC, OpSec reviews, monitoring and cover sit beside them. Ratings are free. This Model Context Protocol server lets AI agents read those ratings directly.

What it reads. Letter grade (AAA to D) plus a composite score (0 to 100) built from 300+ criteria across the full dependency graph, for protocols, chains, tokens, oracles, vaults, organisations and bridges. Plus post-quantum readiness for chains, and a live feed of DeFi hack incidents (confirmed by default).

Keyless by default. It wraps Verdict's live anonymous API, so there is no signup and no API key. Each user runs it locally and queries from their own IP. Bring your own key if you want the per-domain breakdown behind a grade (see below).

Install

Add to your MCP client config (Claude Desktop: claude_desktop_config.json; Claude Code: .mcp.json):

{
  "mcpServers": {
    "verdict-finance": {
      "command": "npx",
      "args": ["-y", "verdict-finance-mcp"]
    }
  }
}

That is it. No key needed to read ratings. (Requires Node 20+.)

Related MCP server: FLINT Agent Passport

Tools

Tool

What it does

search_ratings({ query, entity_type? })

Find entities by name or keyword. Omit entity_type to search all 7 types at once.

get_rating({ entity_type, identifier })

Letter grade, composite score and public metadata for one entity, by slug (aave-v4, ethereum) or UUID. Includes dependency-drag provenance when it shaped the grade.

list_ratings({ entity_type, category?, chain?, limit? })

Browse a set, best-rated first (default 25, cap 50). Category filters are lowercase, e.g. lending.

quantum_readiness({ chain? })

Post-quantum cryptographic readiness for chains (QRI 0-100, readiness band, migration stage, hybrid-signature status), data by LayerQu. Omit chain for the full 72+ chain league table, including chains Verdict has not rated.

get_recent_incidents({ since?, slug?, min_status?, limit? })

DeFi hack incidents, newest first (default 25, cap 200). Confirmed by default; min_status: 'corroborated' opts into multi-source leads that have not yet reached confirmation. Each is corroborated by more than one public hack-reporting source. Poll with since; filter to one rated protocol with slug.

get_methodology({})

The published methodology: criteria counts and domains per entity type, and the AAA to D grade scale with the composite band each grade needs.

get_rating_breakdown({ entity_type, slug })

The per-domain scores behind one entity's grade, plus its intrinsic (pre-dependency) pair. Needs an API key; see Bring your own key.

get_dependencies({ entity_type, slug })

What one entity depends on and what depends on it, with each link's type, criticality and any rank drag, plus its last five grade moves with their causes.

request_new_rating({ entity_name, entity_type, contact_email, note? })

Ask Verdict to rate an entity it does not rate yet. Returns a reference id. The resulting rating is public either way; requesting a rating never buys or moves a grade.

Every rating response ends with an attribution line linking back to the rating on verdict.finance.

Bring your own key

Ratings are free to read: the tools above work with no key at all. Set VERDICT_API_KEY and the server authenticates every call, which adds get_rating_breakdown (per-domain scores). Keys are free: sign in at verdict.finance/dashboard/keys and make one.

{
  "mcpServers": {
    "verdict-finance": {
      "command": "npx",
      "args": ["-y", "verdict-finance-mcp"],
      "env": { "VERDICT_API_KEY": "your-key" }
    }
  }
}

Without the variable the server behaves exactly as it always has: no header is sent, and nothing about the keyless path changes. The key is never logged, echoed, or included in tool output. Called without a key, get_rating_breakdown answers with where to get one rather than failing.

Quantum-readiness data is provided by LayerQu and is companion data only. It never feeds a Verdict grade; chain ratings simply carry an extra LayerQu line when a reading is available.

The incident feed carries hack incidents across DeFi (confirmed by default), including ones at protocols Verdict does not rate. Two things are worth knowing when reading it. Matching to a rated protocol happens when an incident is received, and re-runs when an incident escalates and its payload improves, so matched_protocol reads as of the incident's current tier. It is still never retroactive when Verdict rates more entities. And an incident is a signal to look, never an automatic downgrade: a matched entity may be flagged under review, but re-rating is always a human decision.

Example prompts

  • "What does Verdict rate Aave?" runs get_rating({ entity_type: "protocol", identifier: "aave-v4" })

  • "Search Verdict for Chainlink." runs search_ratings({ query: "chainlink" })

  • "List the chains Verdict rates." runs list_ratings({ entity_type: "chain" })

  • "Is Ethereum quantum-ready?" runs quantum_readiness({ chain: "ethereum" })

  • "Any DeFi hacks this week?" runs get_recent_incidents({ limit: 10 })

  • "How does Verdict score a bridge?" runs get_methodology({})

  • "What dragged Aave's grade down?" runs get_rating_breakdown({ entity_type: "protocol", slug: "aave-v4" })

  • "What does syrupUSDT depend on?" runs get_dependencies({ entity_type: "vault", slug: "syrupusdt" })

  • "Get my protocol rated." runs request_new_rating({ entity_name: "...", entity_type: "protocol", contact_email: "..." })

Example output

Aave V4: BBB (78/100) · protocol · chains: Ethereum · categories: lending · https://www.verdict.finance/products/ratings#protocol-aave-v4

Rating by Verdict: https://www.verdict.finance/products/ratings#protocol-aave-v4

Entities that are not yet rated render as unrated. When a rating was pulled down by a weak dependency, the response says which one.

The marketplace

This server reads ratings. The marketplace is not callable from it: audits, pen tests, scanning, RPC, OpSec reviews, monitoring and cover are at verdict.finance/marketplace.

The rating function is structurally separate from the marketplace. Paying never moves a grade; the evidence a scan or an audit produces can, in either direction.

How it works

Verdict's read API is anonymous and rate-limited per IP (120/min, 20k/day). This server:

  • lists and looks up entities via GET /{type}s and GET /{type}s/{identifier},

  • fetches each entity's latest published scorecard (GET /{type}s/{id}/scorecards) for the grade + composite score,

  • reads the published methodology from GET /methodology,

  • reads the dependency graph behind get_dependencies from GET /graph,

  • reads per-domain scores from GET /{type}s/{slug}/domains (the one route that needs a key), and

  • submits rating requests to POST /contacts, the same public endpoint the "Get rated" form on verdict.finance posts to.

The API base is https://api.verdict.finance/api/v1 and can be overridden with the VERDICT_API_BASE environment variable (used for testing). Set VERDICT_API_KEY to authenticate; leave it unset to stay keyless. The full API surface is documented at api.verdict.finance/openapi.json.

Rate limits and outages are handled gracefully. Tools return a friendly text message, never a crash.

Attribution and trademark

Ratings and methodology are © Verdict. This tool surfaces the public ratings and the published methodology; the deeper analysis lives at verdict.finance. The code is Apache-2.0; the Verdict name and branding are not licensed by it.

Wherever you show a rating, name Verdict as the source, for example "Rating by Verdict" with a link, or show the Verdict badge. The terms are at verdict.finance/legal/terms.

Development

npm install
npm run build     # tsc -> dist/
npm test          # vitest (unit tests, HTTP client mocked)

# optional live smoke against the real API:
VERDICT_LIVE_SMOKE=1 npx vitest run test/live.smoke.test.ts

# the smoke's one keyed case (get_rating_breakdown) skips unless a key is set:
VERDICT_LIVE_SMOKE=1 VERDICT_API_KEY=... npx vitest run test/live.smoke.test.ts

License

Apache-2.0. Copyright 2026 Verdict Capital.

Available Tools

3 tools
get_ratingGet a Verdict ratingA

Get the full free-tier Verdict rating for one DeFi entity (letter grade + composite score 0-100 + public metadata). Identify it by slug (e.g. 'aave') or UUID. Example: get_rating({ entity_type: 'protocol', identifier: 'aave' }).

Inputs: identifier (required), entity_type (required).

list_ratingsList / browse Verdict ratingsA

Browse Verdict's DeFi ratings for one entity type, optionally filtered by category or chain. Returns entities with their letter grade + composite score, best-rated first. Example: list_ratings({ entity_type: 'protocol', category: 'lending' }).

Inputs: entity_type (required), chain, limit, category.

search_ratingsSearch Verdict ratingsA

Search Verdict's DeFi ratings by name or keyword across all 7 entity types (protocol, chain, token, oracle, vault, organisation, bridge). Pass entity_type to narrow the search. Returns matching entities with their letter grade + composite score. Example: search_ratings({ query: 'aave' }).

Inputs: query (required), entity_type.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.1/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct purpose: search across types, get a specific entity, and list by type/filters. No overlap.

    Naming Consistency5/5

    All three tools follow a consistent 'verb_noun' pattern: search_ratings, get_rating, list_ratings.

    Tool Count5/5

    Three tools cover the core operations for a DeFi ratings server: search, get, and list. The number feels appropriate.

    Completeness4/5

    Covers search, detail retrieval, and listing. Missing features like rating history filters, but core workflows are complete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      C
      maintenance
      Provides DeFi vault risk analytics for AI agents to search, compare, and perform due diligence on over 700 vaults across major protocols like Morpho and Aave. It enables natural language analysis of risk scores, platform security, and portfolio-level risk assessments.
      9
      5
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables verification of AI agent identity, authority, and integrity at transaction time, returning signed verdicts for allow, step-up, review, or block.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides typed onchain verdicts for EVM tokens with calibrated probabilities, enabling agents to make informed decisions on tokens such as ape, watch, or avoid, along with risk scores.
      4 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to query CoinMarketCap data and receive trust-scored verdicts—ACT, CAUTION, or DO_NOT_ACT—with cross-checked evidence, RWA token assessments, trade preflight depth checks, and explanations of each check.
      MIT