Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Trustscoreagent MCP

by trustscoreagentversion 0.2.7i★ –iRuns on your computer
Registry nameio.github.trustscoreagent/mcp-server

Install

Overview

Description from the maker (original English)

Check the reputation of AI microservices and public APIs from an open trust registry.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: TRUSTSCORE_API_URL, TRUSTSCORE_AGENT_DID

You need

  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "trustscoreagent": {
      "command": "npx",
      "args": [
        "-y",
        "@trustscoreagent/mcp-server"
      ],
      "env": {
        "TRUSTSCORE_API_URL": "your-value",
        "TRUSTSCORE_AGENT_DID": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add trustscoreagent --env TRUSTSCORE_API_URL=your-value --env TRUSTSCORE_AGENT_DID=your-value -- npx -y @trustscoreagent/mcp-server

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "trustscoreagent": {
      "command": "npx",
      "args": [
        "-y",
        "@trustscoreagent/mcp-server"
      ],
      "env": {
        "TRUSTSCORE_API_URL": "your-value",
        "TRUSTSCORE_AGENT_DID": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "trustscoreagent": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@trustscoreagent/mcp-server"
      ],
      "env": {
        "TRUSTSCORE_API_URL": "your-value",
        "TRUSTSCORE_AGENT_DID": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • TRUSTSCORE_API_URL env
    Base URL of the TrustScore registry. Defaults to the public production API; override only for a self-hosted or staging instance.
  • TRUSTSCORE_AGENT_DID env
    Leave empty (recommended): the server generates an Ed25519 key in ~/.trustscoreagent and signs its ratings with the matching did:key. Setting a DID here overrides that key, so ratings are sent unsign…

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account trustscoreagent, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

  • More stars than 0% of the other 32461 servers in this category
  • Published to the registry more recently than 66% of the other 32461 servers in this category
  • Basic checks equal to or better than 100% of the other 32461 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Trustscoreagent MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.2.7) reached the registry 19 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, dotnet-mcp

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday
Install

dotnet-mcp

by Skymly

MCP server for .NET symbols, XAML, source generators, and restricted workspace edit

Runs on your computerUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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 x402 endpoints), and parts of the design

(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.

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

# 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

# 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)
EndpointDescription
GET /v1/score?service=Trust score for a service (0.5 neutral for unknown)
POST /v1/rateSubmit a rating after calling a service
GET /v1/servicesList rated services (pagination, sorting, filtering)
GET /v1/agent/trust?did=Check your agent's trust score
GET /v1/audit/rootLatest Merkle tree root
GET /v1/audit/proof/{id}Inclusion proof for a rating, with the fields it commits to
GET /v1/audit/anchorsHistory of anchored roots
GET /v1/audit/consistency?from=&to=Proof that a later root extends an earlier one
GET /v1/audit/anchors/{id}/otsOpenTimestamps proof that the root is committed in Bitcoin
GET /v1/stats?days=How much the registry is used (aggregate counts)
Premium (free for now, x402 micropayments later)
EndpointDescription
GET /v1/score/history?service=Daily aggregated score history
GET /v1/score/detailed?service=Latency percentiles, quality distribution
POST /v1/scores/bulkUp 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.

# Add to Claude Code

claude mcp add trustscoreagent -- npx -y @trustscoreagent/mcp-server

Before paying an x402 endpoint, check_reputation with the pay_to of the 402 you received says whether that payee is the one the registry has seen there. See docs/mcp.md for full setup instructions. Also listed on the official MCP Registry (io.github.trustscoreagent/mcp-server), npm, Smithery and Glama; each GitHub release attaches an .mcpb bundle for Claude Desktop.

x402 plugin

@trustscoreagent/x402 plugs into the x402 client SDK (@x402/core, used by @x402/fetch and @x402/axios). Before each payment it checks the payee against the one the registry saw on that endpoint and stops the payment on a mismatch, before anything is signed.

const guard = trustScoreGuard();

guard.attach(client, http); const fetchWithPayment = wrapFetchWithPayment(guard.wrapFetch(fetch), http);

The score alone never blocks unless you set minScore, an unreachable registry never blocks unless you set failClosed, and rating after payment is opt-in (rate: true). It runs in your agent: requests never go through TrustScoreAgent. See x402-plugin/README.md.

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/.

Documentation

  • API Reference
  • Examples & Recipes
  • Receipt Standard
  • MCP Server Setup: Claude, Cursor, Windsurf
  • x402 plugin: check the payee before paying
  • Why Trust Matters for Agents
  • Privacy & Data Handling
  • Audit Log Specification, with an independent verifier in tools/verify-proof

Contributing

Contributions are welcome: see CONTRIBUTING.md and our Code of Conduct. To report a vulnerability, follow 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, and of the x402 endpoints agents pay the most (picked daily from the public Bazaar catalog and probed without paying, see docs/x402-probe.md): real, Merkle-audited measurements, not fabricated numbers. For those x402 endpoints the score also says which payee address and price they ask for, and when either last changed. 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.

See SECURITY.md for the full trust model and how to report vulnerabilities.

License

Apache-2.0. See LICENSE.

Ask PopNx