Skip to main content
ClaudeWave

Free, open reputation registry for AI microservices. Agents check trust scores before calling any service.

MCP ServersOfficial Registry0 stars0 forks● C#Apache-2.0Updated today
ClaudeWave Trust Score
95/100
✓ Verified
Passed
  • ✓Open-source license (Apache-2.0)
  • ✓Actively maintained (<30d)
  • ✓Clear description
  • ✓Topics declared
  • ✓Documented (README)
Last scanned: 9/28/2026
Install in Claude Code / Claude Desktop
Method: NPX · @trustscoreagent/mcp-server
Claude Code CLI
claude mcp add trustscoreagent -- npx -y @trustscoreagent/mcp-server
claude_desktop_config.json (Claude Desktop)
{
  "mcpServers": {
    "trustscoreagent": {
      "command": "npx",
      "args": ["-y", "@trustscoreagent/mcp-server"]
    }
  }
}
1. Run the command above in your terminal (Claude Code), or paste the JSON config into claude_desktop_config.json (Claude Desktop).
2. Replace any <placeholder> values with your API keys or paths.
3. Restart Claude. The MCP server and its tools appear automatically.
Use cases

MCP Servers overview

# TrustScoreAgent

Free, open reputation registry for AI microservices. Agents check trust scores before calling any service.

> **Status: Phase 1 (early).** The API, scoring (Beta + EigenTrust), receipt verification,
> Merkle audit trail and MCP server are implemented and tested, but the public dataset is
> still small (seeded by a transparent probe of public APIs), and parts of the design
> (on-chain anchoring, x402 payments, *mandatory* agent signatures) are Phase 2. We publish
> early and openly on purpose: the trust layer for the agentic economy should exist, be
> auditable, and be adoptable *before* it becomes critical. See the trust model in
> [SECURITY.md](SECURITY.md).

## What is this?

AI agents increasingly rely on paid microservices. TrustScoreAgent lets any agent:
- **Check** the reputation of a service before calling it
- **Rate** a service after calling it
- **Discover** which services are reliable

No account needed. No API key. Identify services by URL, domain, or DID.

## Quick start

```bash
# Check a service's trust score (any format works)
curl "https://api.trustscoreagent.com/v1/score?service=api.example.com"
curl "https://api.trustscoreagent.com/v1/score?service=https://api.example.com/v1/translate"

# Unknown services return a neutral score (0.5), no errors
curl "https://api.trustscoreagent.com/v1/score?service=never-seen-before.com"

# Rate a service after calling it
curl -X POST "https://api.trustscoreagent.com/v1/rate" \
  -H "Content-Type: application/json" \
  -H "X-Agent-DID: my-agent.example.com" \
  -d '{
    "service": "api.example.com",
    "metrics": {
      "status_code": 200,
      "latency_ms": 143,
      "schema_valid": true
    }
  }'

# List top-rated services
curl "https://api.trustscoreagent.com/v1/services?sort_by=score&min_ratings=10"
```

## Local development

```bash
# Start PostgreSQL and Redis
docker compose up -d

# Run the API
dotnet run --project src/TrustScore.Api

# Run tests
dotnet test

# Swagger UI
open http://localhost:5000/swagger
```

## Architecture

- **C# / .NET 8**: ASP.NET Core Minimal API
- **PostgreSQL**: Ratings and service scores
- **Redis**: Score caching, rate limiting, nonce tracking
- **Beta Reputation System**: Bayesian scoring (per-dimension: availability, latency, conformity)
- **EigenTrust**: Anti-Sybil agent trust scoring
- **Merkle Tree**: Audit log with inclusion and consistency proofs (RFC 6962 tree; each leaf commits to what the rating reported)
- **Ed25519 Receipt Verification**: Cryptographic proof of service interaction
- **MCP Server**: Integration with Claude, Cursor, and MCP-compatible agents

## API Reference

### Core (free, always)

| Endpoint | Description |
|----------|-------------|
| `GET /v1/score?service=` | Trust score for a service (0.5 neutral for unknown) |
| `POST /v1/rate` | Submit a rating after calling a service |
| `GET /v1/services` | List rated services (pagination, sorting, filtering) |
| `GET /v1/agent/trust?did=` | Check your agent's trust score |
| `GET /v1/audit/root` | Latest Merkle tree root |
| `GET /v1/audit/proof/{id}` | Inclusion proof for a rating, with the fields it commits to |
| `GET /v1/audit/anchors` | History of anchored roots |
| `GET /v1/audit/consistency?from=&to=` | Proof that a later root extends an earlier one |

### Premium (free for now, x402 micropayments later)

| Endpoint | Description |
|----------|-------------|
| `GET /v1/score/history?service=` | Daily aggregated score history |
| `GET /v1/score/detailed?service=` | Latency percentiles, quality distribution |
| `POST /v1/scores/bulk` | Up to 100 scores in one request |

### Service identification

All endpoints accept services in any format (they are normalized internally):
- `api.example.com` (domain)
- `https://api.example.com/v1/translate` (URL)
- `did:web:api.example.com` (DID)

All three resolve to the same service.

## MCP Server

TrustScoreAgent is available as an MCP server for Claude, Cursor, and other agents.

```bash
# Add to Claude Code
claude mcp add trustscoreagent -- npx -y @trustscoreagent/mcp-server
```

See [docs/mcp.md](docs/mcp.md) for full setup instructions. Also listed on the
[official MCP Registry](https://registry.modelcontextprotocol.io/v0/servers?search=trustscoreagent)
(`io.github.trustscoreagent/mcp-server`), [npm](https://www.npmjs.com/package/@trustscoreagent/mcp-server),
[Smithery](https://smithery.ai/servers/trustscoreagent/trustscoreagent) and
[Glama](https://glama.ai/mcp/servers/trustscoreagent/trustscoreagent); each GitHub release attaches an
`.mcpb` bundle for Claude Desktop.

## Framework integrations

Drop-in tools for agent frameworks (no account or API key needed):

- **LangChain**: `from trustscoreagent_langchain import get_trustscoreagent_tools`
- **CrewAI**: `from trustscoreagent_crewai import get_trustscoreagent_tools`

Each exposes `trustscore_check_reputation`, `trustscore_submit_rating`, and
`trustscore_list_services`. See [`integrations/`](integrations/).

## Documentation

- [API Reference](docs/api.md)
- [Examples & Recipes](docs/examples.md)
- [Receipt Standard](docs/receipts.md)
- [MCP Server Setup](docs/mcp.md): Claude, Cursor, Windsurf
- [Why Trust Matters for Agents](docs/why.md)
- [Privacy & Data Handling](docs/privacy.md)
- [Audit Log Specification](docs/MERKLE-SPEC.md), with an independent verifier in
  [`tools/verify-proof`](tools/verify-proof/verify-proof.mjs)

## Contributing

Contributions are welcome: see [CONTRIBUTING.md](CONTRIBUTING.md) and our
[Code of Conduct](CODE_OF_CONDUCT.md). To report a vulnerability, follow
[SECURITY.md](SECURITY.md).

## Project status & trust model

TrustScoreAgent is **Phase 1 (early)**. What that means in practice:

- **Baseline data is real and auditable.** Initial scores come from a transparent operated
  probe (`did:web:trustscoreagent.com:probe`) that measures the availability, latency and
  conformity of a curated list of public, free APIs: real, Merkle-audited measurements, not
  fabricated numbers. Community and receipt-verified ratings accumulate on top. (The earlier
  fictitious `*.example.com` seeds have been removed.)
- **Single operator.** Neutrality currently rests on open-source scoring code and a
  verifiable Merkle audit trail, not on decentralization. Federation is a later phase.
- **Agent identity can be proven, but is not yet mandatory.** Agents identified by a
  `did:key` sign each rating with their Ed25519 key (`X-Agent-Signature`), which binds the
  rating to the holder of that key. Unsigned ratings still count at half weight so existing
  clients keep working, which means a rating is only as attributable as its signature.
  Verified service **receipts** remain the strongest signal, and on-chain Merkle anchoring
  is still Phase 2.

See [SECURITY.md](SECURITY.md) for the full trust model and how to report vulnerabilities.

## License

Apache-2.0. See [LICENSE](LICENSE).
ai-agentsdided25519eigentrustmcpmcp-servermerkle-treemodel-context-protocolreputationtrust

What people ask about trustscoreagent

What is trustscoreagent/trustscoreagent?

+

trustscoreagent/trustscoreagent is mcp servers for the Claude AI ecosystem. Free, open reputation registry for AI microservices. Agents check trust scores before calling any service. It has 0 GitHub stars and its last recorded update is dated 2026-09-27.

How do I install trustscoreagent?

+

You can install trustscoreagent by cloning the repository (https://github.com/trustscoreagent/trustscoreagent) or following the README instructions on GitHub. ClaudeWave also provides quick install blocks on this page.

Is trustscoreagent/trustscoreagent safe to use?

+

Our security agent has analyzed trustscoreagent/trustscoreagent and assigned a Trust Score of 95/100 (tier: Verified). See the full breakdown of passed checks and flags on this page.

Who maintains trustscoreagent/trustscoreagent?

+

trustscoreagent/trustscoreagent is maintained by trustscoreagent. The last recorded GitHub activity is dated 2026-09-27, with 0 open issues.

Are there alternatives to trustscoreagent?

+

Yes. On ClaudeWave you can browse similar mcp servers at /categories/mcp, sorted by popularity or recent activity.

Deploy trustscoreagent to your cloud

Ship this repo to production in minutes. Each platform spins up its own environment with editable env vars.

Maintain this repo? Add a badge to your README

Drop the badge into your GitHub README to show it's tracked on ClaudeWave. Each badge links back to this page and reflects the live Trust Score.

Featured on ClaudeWave: trustscoreagent/trustscoreagent
[![Featured on ClaudeWave](https://claudewave.com/api/badge/trustscoreagent-trustscoreagent)](https://claudewave.com/repo/trustscoreagent-trustscoreagent)
<a href="https://claudewave.com/repo/trustscoreagent-trustscoreagent"><img src="https://claudewave.com/api/badge/trustscoreagent-trustscoreagent" alt="Featured on ClaudeWave: trustscoreagent/trustscoreagent" width="320" height="64" /></a>

More MCP Servers

trustscoreagent alternatives