de en es ja ko ru zh

tradallo-reputation

Name: tradallo-reputation
Author: tradallo

Official

by tradallo

Overview Schema Source Related Servers Discussions(1)Admin

TypeScript

Remote

@tradallo/reputation

npm version license MCP

Servidor MCP + cliente TypeScript + CLI para el Protocolo de Registro Verificado de Tradallo. Tres formas de consultar registros de trading de humanos y agentes verificados criptográficamente:

# CLI — pretty terminal cards, no install required
npx @tradallo/reputation card alpha-momentum-v3 --agent

# MCP — drop into Claude Desktop / Cursor / any MCP client (config below)

# Programmatic — typed TS/JS client
import { TradalloClient } from "@tradallo/reputation";

Cada respuesta es canonizada mediante JCS + verificada con ed25519 contra la clave pública publicada por Tradallo en tradallo.com/.well-known/tradallo-pubkeys.json antes de ser mostrada. La firma reside en el sobre; este cliente obtiene el registro de claves públicas, resuelve el key_id, verifica la firma y solo entonces devuelve los datos. Protección contra reproducción mediante served_at + max_age_seconds.

Instalación

Claude Desktop

Añade esto a tu claude_desktop_config.json (Ajustes → Desarrollador → Editar configuración):

{
  "mcpServers": {
    "tradallo-reputation": {
      "command": "npx",
      "args": ["-y", "@tradallo/reputation"]
    }
  }
}

Reinicia Claude Desktop. Las herramientas de Tradallo deberían aparecer en la paleta de herramientas.

Cursor

Añade esto a ~/.cursor/mcp.json (o a través de Ajustes de Cursor → MCP):

{
  "mcpServers": {
    "tradallo-reputation": {
      "command": "npx",
      "args": ["-y", "@tradallo/reputation"]
    }
  }
}

Cliente MCP genérico

npx @tradallo/reputation

Habla MCP sobre stdio.

Desarrollo local / staging

Apunta a tu propio despliegue configurando TRADALLO_BASE_URL:

{
  "mcpServers": {
    "tradallo-reputation": {
      "command": "npx",
      "args": ["-y", "@tradallo/reputation"],
      "env": { "TRADALLO_BASE_URL": "http://localhost:3000" }
    }
  }
}

Related MCP server: aip-identity

CLI

El mismo binario funciona como una CLI de terminal cuando se invoca con un subcomando:

# Pretty card with verification status, stats, version metadata
npx @tradallo/reputation card alpha-momentum-v3 --agent

# Raw verified JSON (for piping into jq, etc.)
npx @tradallo/reputation track-record alpha-momentum-v3 --agent

# Discovery
npx @tradallo/reputation search --min-sharpe 1.5 --min-trades 200 --sort-by sharpe

# Agent version history
npx @tradallo/reputation versions alpha-momentum-v3

# Paginated UTRs
npx @tradallo/reputation utrs alpha-momentum-v3 --limit 50

# Look up a specific UTR by hash
npx @tradallo/reputation verify <sha256-hex> alpha-momentum-v3

# Help
npx @tradallo/reputation help

NO_COLOR=1 deshabilita ANSI. TRADALLO_BASE_URL sobrescribe la base de la API.

Cliente programático

Integra el cliente de verificación en tu propio código TS/JS:

import { TradalloClient } from "@tradallo/reputation";

const client = new TradalloClient(); // defaults to https://tradallo.com

// Throws if signature invalid, replay window expired, or pubkey unknown.
// Returns the verified `data` payload (not the envelope wrapper).
const record = await client.getSigned<{ stats: { all_time: { sharpe_ratio: number | null } } }>(
  "/api/v1/agents/alpha-momentum-v3/track-record",
);

if ((record.stats.all_time.sharpe_ratio ?? 0) >= 1.5) {
  // ... delegate capital, copy trades, etc.
}

El flujo de verificación ocurre DENTRO de getSigned. Si algo falla (firma incorrecta, sobre expirado, clave desconocida, discrepancia de esquema), la llamada lanza un error. Nunca verás datos no verificados.

Herramientas

`get_track_record(handle, principal_type?)`

Obtén un historial verificado para un perfil o agente de Tradallo.

Entradas:

handle (cadena, requerido) — el identificador de Tradallo (ej. aaronjordan, alpha-momentum-v3)
principal_type ("human" | "agent", opcional, por defecto "agent") — en qué espacio de nombres buscar

Retorna: el payload firmado completo (nivel de verificación, estadísticas históricas + móviles de 30/90/365 días incluyendo Sharpe, drawdown máximo, tasa de victorias, PnL, esperanza).

Ejemplo de uso:

"Muéstrame el historial de trading verificado de Aaron Jordan en Tradallo."

`search_records(filters)`

Descubre registros verificados que coincidan con criterios de rendimiento.

Entradas (todas opcionales): min_sharpe, min_trades, max_drawdown, venue, principal_type, sort_by, limit.

Retorna: lista ordenada de resúmenes de humanos/agentes con sus estadísticas. Verificado por firma.

`verify_utr(utr_hash)`

Busca un Recibo de Operación Universal (UTR) por hash. Devuelve si Tradallo ha anclado ese hash en la cadena mediante un memo de Solana, y en caso afirmativo, la cadena, firma, slot, posted_at, URL del explorador de Solana y la clave pública del notario para que el llamador pueda verificarlo independientemente en la cadena.

Retorna: { found, anchored_on_chain, chain?, signature?, slot?, posted_at?, explorer_url?, notarizer_pubkey? }.

`get_versions(agent_handle)`

Obtén el historial completo de versiones de un agente (etiquetas semver, version_hash, policy_hash, cuándo se desplegó y reemplazó cada versión). Verificado por firma.

`get_utrs(agent_handle, since?, limit?)`

Obtén Recibos de Operación Universales crudos para un agente, paginados al estilo cursor en closed_at. Cada recibo incluye su hash SHA-256 recalculado por Tradallo para que los consumidores puedan verificar registros individuales.

Cómo funciona la verificación

Cada respuesta firmada de la API de Tradallo envuelve los datos en un sobre canonizado mediante JCS (RFC 8785) con una firma ed25519:

{
  "data": { ... },
  "schema_version": "1",
  "served_at": "2026-04-30T22:29:52.776Z",
  "max_age_seconds": 60,
  "signature": {
    "alg": "ed25519",
    "key_id": "tradallo-prod-2026-04",
    "sig": "<base64>"
  }
}

Este servidor MCP:

Obtiene /.well-known/tradallo-pubkeys.json (caché de 5 min)
Resuelve signature.key_id → clave pública ed25519
Canoniza mediante JCS {data, schema_version, served_at, max_age_seconds}
Verifica la firma contra la clave pública
Rechaza respuestas donde now > served_at + max_age_seconds (protección contra reproducción)

Si alguna comprobación falla, la llamada a la herramienta devuelve un error en lugar de los datos. Se le informa al agente el motivo.

Por qué es importante

La identidad (quién es el agente) y los pagos (cómo paga) se resuelven en 2026 mediante x402, MPP, Coinbase Agentic Wallets y ERC-8004. La reputación no. Cuando un agente decide si delegar capital, copiar operaciones o suscribirse a señales de otra parte, necesita una forma de preguntar: "¿es real su historial?"

Este servidor MCP es la forma de menor fricción para hacer esa pregunta.

x402 — lo que viene

Hoy en día, la API pública es anónima y tiene límite de tasa por IP (60 req/min). Estamos implementando acceso por niveles mediante x402, el estándar HTTP 402 de pago requerido, para que los agentes puedan pagar microtransacciones en USDC en Base para evitar límites de tasa y desbloquear niveles de mayor rendimiento sin necesidad de registro o gestión de claves API.

Expectativas compatibles hacia adelante:

Anónimo: 60 req/min/IP (hoy, gratis)
Suscriptor activo: 600 req/min mediante clave API (en desarrollo — Fase 4.4)
Micropago x402: pago en USDC por llamada para consultas pesadas de una sola vez; no se requiere cuenta (planificado para Fase 4.5)
Niveles de Operador / Flota: suscripciones a webhooks, subdominios personalizados, indexación prioritaria

La respuesta de límite de tasa obtendrá un bloque de opciones de pago x402 una vez que la tubería del facilitador esté conectada. Este servidor MCP comenzará a pagar automáticamente cuando vea un 402 con metadatos x402. Hasta entonces, todas las consultas son gratuitas y verificables.

Agente de referencia

Un ejemplo de agente funcional que consulta a Tradallo antes de delegar capital: github.com/tradallo/agent.

Especificaciones y documentos

Resumen del protocolo: docs/PROTOCOL.md
Especificación: docs/SPEC _V1.1.md
API pública: https://tradallo.com/api/v1/
Registro de claves públicas: https://tradallo.com/.well-known/tradallo-pubkeys.json

Registro de cambios

Ver CHANGELOG.md.

Licencia

MIT

Available Tools

5 tools

get_track_recordAInspect

Fetch a verified trading track record for a Tradallo profile (human) or agent. Returns cryptographically-verified statistics (Sharpe, win rate, max drawdown, PnL, trade count) computed from on-chain or in-house-sim trade history. The signature is ed25519-verified against Tradallo's published pubkey before this tool returns.

ParametersJSON Schema

Name	Required	Description	Default
`handle`	Yes	The Tradallo handle to look up (e.g. 'aaronjordan' for a human, 'alpha-momentum-v3' for an agent).
`principal_type`	No	Whether the handle is a human profile or an agent. Defaults to 'agent' (the more common reputation-query use case).

TDQS

A4.2/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden. It discloses that statistics are cryptographically-verified and signature-verified before return, and mentions computation from on-chain or in-house-sim history. Does not cover potential errors or permissions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no wasted words, front-loaded with purpose and key details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, but description lists return values (Sharpe, win rate, etc.) and explains verification process. Missing pagination or rate limits, but adequate for a simple fetch tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema coverage is 100%, with clear descriptions for both parameters. The description adds no extra meaning beyond the schema, so baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool fetches a verified trading track record for a Tradallo profile (human or agent) and lists the statistics returned. It distinguishes from siblings like get_utrs and verify_utr by focusing on track record data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool should be used when a verified track record is needed, but does not explicitly exclude alternatives or provide when-not scenarios. Sibling tools have different purposes, so context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_utrsAInspect

Fetch raw Universal Trade Receipts for an agent. Each UTR is a v2 canonical receipt with its SHA-256 hash recomputed by Tradallo so consumers can spot-check individual receipts. Paginated cursor-style on closed_at.

ParametersJSON Schema

Name	Required	Description
`agent_handle`	Yes	The agent's handle.
`since`	No	ISO timestamp; only return UTRs closed at or after this. Defaults to the agent's anchor.
`limit`	No	Page size (default 100, max 500).

TDQS

A3.9/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden. It discloses that each UTR's SHA-256 hash is recomputed for spot-checking, and pagination is cursor-style on closed_at. This reveals behavioral traits beyond a simple fetch, though auth requirements and side effects are not mentioned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three sentences, front-loaded with purpose, followed by relevant detail and pagination. No redundant information, every sentence serves a purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description does not fully explain return format or pagination details like cursor handling. It mentions 'v2 canonical receipt' and hash, but an agent might need more clarity on response structure. Adequate but with gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. The description adds minimal extra meaning beyond the schema, only implicitly relating closed_at to the 'since' parameter via pagination mention. No further parameter details are provided.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool fetches raw Universal Trade Receipts for an agent, specifies the resource and action, and distinguishes from siblings by mentioning it provides v2 canonical receipts with recomputed SHA-256 hashes. It also notes pagination, setting it apart from other tools like verify_utr.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by describing the tool's function but lacks explicit guidance on when to use this tool versus its siblings (e.g., get_track_record, verify_utr). No when-not-to-use or alternative suggestions are provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_versionsAInspect

Fetch the full version history of an agent (semver tags, version_hash, policy_hash, when each version was deployed and superseded). Useful for understanding which version of an agent's policy produced a given track record. The response is signature-verified.

ParametersJSON Schema

Name	Required	Description	Default
`agent_handle`	Yes	The agent's handle.

TDQS

A4.2/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description covers key behaviors: lists return fields and states response is signature-verified. Lacks explicit mention of idempotency or authentication, but sufficient for a read-only fetch.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two focused sentences, no redundant information, front-loaded with action and resource.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given a single parameter and no output schema, the description covers return fields, verification, and a use case. Could specify if history is limited (e.g., pagination), but 'full version history' implies completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with a clear description for agent_handle. The tool description does not add further information about the parameter beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it fetches full version history with specific fields (semver, hashes, timestamps), distinguishing it from sibling tools that handle track records or UTRs. Includes a use case.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides useful context: 'useful for understanding which version of an agent's policy produced a given track record.' Does not explicitly exclude other uses or name alternatives, but context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

search_recordsAInspect

Search verified trading records by performance filters (Sharpe, max drawdown, trade count, venue, principal type). Returns a list of summary records sorted by the chosen metric. Useful for an agent shopping for strategies that meet specific risk/return criteria. The response is signature-verified against Tradallo's published pubkey before being returned.

ParametersJSON Schema

Name	Required	Description
`min_sharpe`	No	Minimum annualized Sharpe ratio.
`min_trades`	No	Minimum trade count.
`max_drawdown`	No	Maximum drawdown as a fraction (e.g. 0.25 for 25%).
`venue`	No	Restrict to a specific venue (e.g. 'hyperliquid', 'dydx').
`principal_type`	No
`sort_by`	No	Field to sort results by (descending). Default: net_pnl.
`limit`	No	Max results (default 25, max 100).

TDQS

A4.1/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden. It discloses that results are signature-verified, which is a notable behavioral trait. It does not mention authentication, rate limits, or read-only nature, but for a search tool the description is fairly transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences with no wasted words. It front-loads the main action and parameters, then adds usage context and verification detail efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description could have detailed the return fields. 'List of summary records' is vague. However, parameter coverage and sibling context make it adequate but not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is high (86%), so the baseline is 3. The description summarizes the filter parameters but adds no new meaning beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool searches verified trading records with performance filters and returns sorted summary records. It distinguishes from sibling get/verify tools by focusing on search and filtering.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says it is useful when shopping for strategies meeting risk/return criteria, providing clear usage context. It does not mention when not to use it or compare to siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

verify_utrAInspect

Look up a Universal Trade Receipt by hash. Returns whether Tradallo has anchored that hash on-chain via a Solana memo transaction, and if so, returns the chain, signature, slot, posted_at, explorer URL, and notarizer pubkey so the caller can independently verify the anchor on Solana Explorer. The signed-envelope response is ed25519-verified before this tool returns.

ParametersJSON Schema

Name	Required	Description	Default
`utr_hash`	Yes	The 64-char hex SHA-256 UTR hash to look up.

TDQS

A4.2/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, description fully carries the burden and discloses that the response indicates anchoring status, returns detailed verification fields, and involves ed25519 verification before returning. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences with front-loaded purpose statement and no redundant information; every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequately explains return fields for a lookup tool with one parameter, though could mention error handling or format of the boolean result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Single parameter utr_hash; schema already has a complete description (100% coverage). The description adds no further meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the tool looks up a Universal Trade Receipt by hash and explains the output structure, distinguishing it from siblings like get_utrs and search_records.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies use when you have a UTR hash to verify on-chain anchoring; lacks explicit when-not-to-use or alternatives, but context from sibling names provides some guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

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

5 tool updatesv0.3.2May 2, 2026
- First observedget_track_record
- First observedget_utrs
- First observedget_versions
- First observedsearch_records
- First observedverify_utr

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.3/5.0

Scored 2026-05-02 13:00 across 5 tools

Disambiguation5/5

Each tool serves a clear, distinct purpose: fetching a track record, fetching raw receipts, retrieving version history, searching records by filters, and verifying a receipt's on-chain anchor. No two tools overlap in functionality, and descriptions clearly differentiate them.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (get_track_record, get_utrs, get_versions, search_records, verify_utr), using lowercase with underscores. The naming is predictable and easy to parse.

Tool Count5/5

Five tools is ideal for this domain: they cover the core operations (fetching individual records, listing receipts, version history, search, and verification) without unnecessary bloat. The scope is well-defined and each tool earns its place.

Completeness5/5

The tool set provides a complete surface for querying and verifying trading reputation data: individual track records, raw receipts, version history, search by filters, and cryptographic verification. No obvious gaps exist for a read-only verification service.

Maintenance

ActivityInactive

ResponsivenessUnresponsive

Resources

Need Help?

Related Servers

Related MCP Connectors

HODLXXI Read-Only A
io.github.hodlxxi
Public read-only MCP server for HODLXXI agent identity, trust, receipts, and verification.
Blockchain Cryptocurrency
262
saagarpatel.dev Portfolio A
io.github.saagpatel
Agent-native MCP server over the public saagarpatel.dev corpus. Read-only, stateless.
Search Documentation Access
82
tenzro
xyz.tenzro
Tenzro Network MCP server: wallet, identity, payments, inference, staking, bridges, verification.
Blockchain Cryptocurrency Payments & Billing
2
wallet-verifier-mcp B
com.wallet-connectors
MCP server for verifying EUDI/Talao wallet data via OIDC4VP (pull) for AI agents.
Security Blockchain Web3 & Decentralized Tech
12

Related MCP Servers

agentfolio-mcp-server
Agent Orchestration Blockchain Web3 & Decentralized Tech
0xbrainkid
A
license
A
quality
F
maintenance
MCP server for AgentFolio — the identity and reputation layer for AI agents. Query agent profiles, trust scores, verification status, and marketplace listings through 8 MCP tools.
Updated 6 months ago (2026-03-25 09:09 UTC)
9
89 npm
1
MIT
aip-identity
Autonomous Agents Security
The-Nexus-Guard
A
license
A
quality
D
maintenance
MCP server for AI agent identity — verify agents with Ed25519 signatures, check trust scores, sign and verify content, exchange encrypted messages. Built on the Agent Identity Protocol (AIP).
Updated 7 months ago (2026-03-09 12:03 UTC)
8
MIT
AgentTrust
Security Autonomous Agents
raditotev
F
license
A
quality
C
maintenance
Reputation and trust scoring service for AI agents, exposed as an MCP server. Evaluate counterparties, report interactions, issue portable trust certificates, and detect Sybil attacks.
Updated 10 days ago (2026-09-27 15:49 UTC)
23
53 PyPI
-
web3-agents-mcp
Blockchain Web3 & Decentralized Tech
hanjoonchoe
A
license
A
quality
B
maintenance
An MCP server that bridges ERC-8004 agent identity, reputation, and validation registries into tool calls, enabling discovery, inspection, and verification of on-chain AI agents from any MCP client.
Updated 3 months ago (2026-07-13 08:36 UTC)
8
MIT