Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Descripción del creador (original en inglés)
Check the reputation of AI microservices and public APIs from an open trust registry.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
TRUSTSCORE_API_URL, TRUSTSCORE_AGENT_DIDNecesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json
{
"mcpServers": {
"trustscoreagent": {
"command": "npx",
"args": [
"-y",
"@trustscoreagent/mcp-server"
],
"env": {
"TRUSTSCORE_API_URL": "your-value",
"TRUSTSCORE_AGENT_DID": "your-value"
}
}
}
}Ejecuta esto en tu terminal
claude mcp add trustscoreagent --env TRUSTSCORE_API_URL=your-value --env TRUSTSCORE_AGENT_DID=your-value -- npx -y @trustscoreagent/mcp-serverCompleta los valores vacíos antes de ejecutarlo.
Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"trustscoreagent": {
"command": "npx",
"args": [
"-y",
"@trustscoreagent/mcp-server"
],
"env": {
"TRUSTSCORE_API_URL": "your-value",
"TRUSTSCORE_AGENT_DID": "your-value"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"trustscoreagent": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@trustscoreagent/mcp-server"
],
"env": {
"TRUSTSCORE_API_URL": "your-value",
"TRUSTSCORE_AGENT_DID": "your-value"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
TRUSTSCORE_API_URL envTRUSTSCORE_AGENT_DID envEsta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 6 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub trustscoreagent, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (0.2.7) llegó al registro hace 19 días.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Node.js en tu computadora.
En la misma categoría: Spec Driven Development, Remote Desktop Commander, topo^alpin
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
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.
Avalanche bulletins and mountain weather forecasts for any place in the Alps.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
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.