
AgentTrust
io.github.raditotev由 GitHub 账号 raditotev 发布v0.1.5更新于 Oct 24, 2026
MCP Server for Agent Reputation & Trust Scoring
概览
面向 AI 智能体的信誉与信任评分 MCP 服务器:查询信任分、上报交互结果、发起争议、签发可验证凭证并检测女巫攻击。
- 可以做什么
- 查询与比较智能体:查看信任分、批量查询、并排排名、按分数或能力搜索、读取档案与评分明细。
- 注册智能体并管理身份:注册、生成签名令牌、关联外部认证身份、查看状态。
- 上报并确认交互结果,列出待确认记录并查看交互历史。
- 对上报结果发起争议并处理裁决。
- 签发、列出并验证可移植的签名信任凭证。
- 执行女巫检测,识别互刷好评、集中注册和可疑委托链。
- 适用场景
- 适用于助手本身作为智能体或与其他智能体打交道的场景:在交易前评估对方可信度、记录交互结果,或向第三方出示可验证的信誉证明。
- 运行要求
- 以本地 Python 进程(Python 3.13+、uv)通过 stdio 运行,也可连接托管 HTTP 端点。自建需 PostgreSQL 16(含 TimescaleDB)、Redis 7 和签名密钥文件;必须设置 DATABASE_URL、REDIS_URL、SIGNING_KEY_PATH,可选 AUTH_PROVIDER 与 AGENTAUTH_ACCESS_TOKEN。上报、争议和凭证签发需要访问令牌。
安装
在 SourceWeft 中
- 打开 控制台中的 AgentTrust,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
README
AgentTrust
Reputation and trust scoring service for AI agents, exposed entirely as an MCP server. Evaluate counterparties before transacting, report interaction outcomes, issue portable trust certificates, and detect Sybil attacks.
Table of Contents
- Quickstart
- Connecting to the MCP Server
- Authentication
- Tools Reference
- Resources
- Prompts
- Score Types
- Rate Limits
- Self-Hosting
Quickstart
1. Connect to the MCP server
Add AgentTrust to your MCP client configuration:
Or for local development via stdio:
2. Register your agent
Response:
Store the private_key_hex immediately -- it is shown only once.
3. Generate an access token
Response:
4. Check trust before transacting
5. Report interaction outcomes
Both parties should report for mutual confirmation (higher credibility).
Connecting to the MCP Server
AgentTrust supports two MCP transports:
Authentication
AgentTrust supports two authentication methods. Many tools work without authentication, but reporting interactions, filing disputes, and issuing attestations require it.
AgentAuth (preferred)
Obtain a bearer token from AgentAuth and pass it as access_token. This provides the full set of scopes:
Standalone (Ed25519)
Register with register_agent and generate tokens with generate_agent_token. Provides trust.read and trust.report scopes. You can upgrade to AgentAuth later via link_agentauth.
No authentication
Tools marked as "Auth: none" work without any token. Useful for checking trust scores and verifying attestations.
Tools Reference
Discovery
discover
Auth: none
Returns the complete service catalog: available tools, auth methods, score types, interaction types, rate limits, and a quickstart guide. Call this first when connecting.
Agent Management
register_agent
Auth: none
Register a new agent in the trust network. Three paths:
- AgentAuth -- pass
access_tokenfrom AgentAuth - Standalone -- pass your own
public_key_hex(hex-encoded Ed25519 public key) - Auto-generate -- omit both to get a keypair generated for you
generate_agent_token
Auth: none (uses private key directly)
Generate a signed JWT access token for standalone agents.
whoami
Auth: required
Check your identity, current trust scores, and scopes.
get_agent_profile
Auth: none (authenticated calls get extra detail)
Retrieve the public profile for any agent.
search_agents
Auth: none
Search agents by trust score, capabilities, and interaction count.
link_agentauth
Auth: required (AgentAuth token)
Link an existing standalone profile to an AgentAuth identity, merging interaction history. The canonical agent_id after linking is always the original standalone UUID — the AgentAuth UUID is stored as agentauth_id in metadata.
Response:
On dry_run=true: returns would_link_agent_id, agentauth_id, current_scores, interaction_count, capabilities, and message — no changes are persisted.
Error codes: invalid_input, proof_sig_invalid, proof_expired, key_not_found, already_linked, authentication_failed.
verify_link_proof
Auth: required (AgentAuth token)
Preflight check: validate a link_agentauth proof without writing to the database. Runs the same validation steps (token authenticity, key lookup, proof signature, expiry, already-linked check) but never persists any changes. Use this before calling link_agentauth to confirm everything is in order.
Response:
agent_status
Auth: required
One-call status snapshot combining identity, trust scores, pending confirmation count, and active attestations. Useful as a dashboard or health check.
Response:
Trust Scoring
check_trust
Auth: none (authenticated calls with trust.read scope get factor_breakdown)
Primary tool for evaluating an agent before a transaction. Returns a score (0.0-1.0), confidence (0.0-1.0), interaction count, and a plain-language explanation.
Response:
A score of 0.5 with confidence 0.05 means "unknown", not "average". Low confidence means few interactions -- treat with caution.
check_trust_batch
Auth: none
Check trust scores for up to 20 agents in a single call.
compare_agents
Auth: none
Rank up to 10 agents side-by-side by score.
get_score_breakdown
Auth: required (trust.read scope)
Detailed Bayesian factors behind a score: raw score, dispute penalty, alpha/beta parameters, interaction weights.
Interaction Reporting
report_interaction
Auth: required (trust.report scope)
Report the outcome of an interaction with another agent. Both parties should report for mutual confirmation -- one-sided reports carry less weight.
Response:
confirm_interaction
Auth: required (trust.report scope)
Confirm a counterparty's interaction report. Creates mutual confirmation, which increases the report's weight in score computation.
list_pending_confirmations
Auth: required
List interactions reported by other agents that await your confirmation.
get_interaction_history
Auth: required
Retrieve interaction history for an agent.
Disputes
file_dispute
Auth: required (trust.dispute.file scope)
Challenge an interaction outcome you believe was reported incorrectly.
Limits: max 10 disputes per day, max 30 open disputes at once. Agents with 5+ dismissed disputes are blocked from filing new ones (24h cooldown after each dismissal).
resolve_dispute
Auth: required (trust.dispute.resolve scope, arbitrators only)
Resolve an open dispute. Requires AgentAuth permission check.
Attestations
issue_attestation
Auth: required (trust.attest.issue scope)
Issue a portable, Ed25519-signed JWT capturing an agent's current trust scores. The agent can present this to third parties who verify the signature without querying AgentTrust.
Response:
list_my_attestations
Auth: required
List your active (non-expired, non-revoked) attestations. Each entry includes the attestation ID, validity window, seconds remaining, and the score snapshot captured at issuance.
Response:
verify_attestation
Auth: none
Verify an attestation JWT's signature, expiry, and revocation status. No authentication needed -- this is designed for third-party verification.
Response:
Sybil Detection
sybil_check
Auth: none
Detect potential Sybil behavior: ring reporting (mutual positive feedback loops), burst registration (many agents in a short window), and suspicious delegation chains.
Response:
When signals are detected:
Resources
MCP resources provide read-only access to trust data via URI templates:
Prompts
Pre-built prompt templates for common evaluation workflows:
Score Types
Scores use a Bayesian Beta distribution with exponential time decay (90-day half-life) and dispute penalties. Scores range from 0.0 to 1.0, paired with a confidence value:
- High score + high confidence = trustworthy, well-established agent
- High score + low confidence = looks good but too few interactions to be sure
- 0.5 score + near-zero confidence = unknown agent (prior), not "average"
Rate Limits
Requests are rate-limited per agent per minute, with higher limits for more trusted agents:
Additional limits on specific operations:
- Interaction reports: max 10 per pair per day, 1 per type per pair per hour
- Disputes filed: max 10 per day, max 30 open at once
- Dispute targets: max 10 open disputes per target
Self-Hosting
Prerequisites
- Python 3.13+
- PostgreSQL 16 with the TimescaleDB extension —
interactionsis a hypertable, so plain PostgreSQL is not enough - Redis 7
- uv package manager
Setup
Environment Variables
Create a .env file:
Running
Docker
Run the development stack with Docker Compose:
This starts PostgreSQL (TimescaleDB, port 5433), Redis (port 6380), the MCP server, and the background worker.
Metrics and dashboards are not part of this stack. The server exposes Prometheus metrics at /metrics; point your own Prometheus and Grafana at it, or see docs/deployment.md for how the hosted instance uses a shared observability stack.
Tests
来源:README.md,提交 18ce010
工具
0版本历史
1- v0.1.5最新Sep 16, 2026
评分
已满足适用检查项的 40%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分
请在仓库或注册中心条目中声明许可证。