Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Check the reputation of AI microservices and public APIs from an open trust registry.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
TRUSTSCORE_API_URL, TRUSTSCORE_AGENT_DIDYou need
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-serverFill in the empty values before running it.
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.
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.
TRUSTSCORE_API_URL envTRUSTSCORE_AGENT_DID envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
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
The registry name was verified with the GitHub account trustscoreagent, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
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.
The registry does not list a required key, though some servers ask you to sign in on first use.
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).
The GitHub repo last changed –, and the latest version (0.2.7) reached the registry 19 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, dotnet-mcp
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
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
MCP server for .NET symbols, XAML, source generators, and restricted workspace edit
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.
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.
AI agents increasingly rely on paid microservices. TrustScoreAgent lets any agent:
No account needed. No API key. Identify services by URL, domain, or DID.
# 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"
curl "https://api.trustscoreagent.com/v1/score?service=never-seen-before.com"
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 } }'
curl "https://api.trustscoreagent.com/v1/services?sort_by=score&min_ratings=10"
# Start PostgreSQL and Redis
docker compose up -d
dotnet run --project src/TrustScore.Api
dotnet test
open http://localhost:5000/swagger
| 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 |
GET /v1/audit/anchors/{id}/ots | OpenTimestamps proof that the root is committed in Bitcoin |
GET /v1/stats?days= | How much the registry is used (aggregate counts) |
| 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 |
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.
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.
@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.
Drop-in tools for agent frameworks (no account or API key needed):
from trustscoreagent_langchain import get_trustscoreagent_toolsfrom trustscoreagent_crewai import get_trustscoreagent_toolsEach exposes trustscore_check_reputation, trustscore_submit_rating, and trustscore_list_services. See integrations/.
tools/verify-proofContributions are welcome: see CONTRIBUTING.md and our Code of Conduct. To report a vulnerability, follow SECURITY.md.
TrustScoreAgent is Phase 1 (early). What that means in practice:
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.)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.
Apache-2.0. See LICENSE.