MCP.Market

Trust Layer MCP server

by Ernesmar·io.github.Ernesmar/trust-layer·v0.1.0
No reviews yet

Notario verificable de agentes de IA: registra identidad y acciones en un log inmutable y firmado.

B70/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B70/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Trust Layer yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Trust Layer tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualityno auth information5/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 70/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Trust Layer compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
70/100
higher than 35% of 48,255 servers

Install Trust Layer in Claude Code, Cursor or VS Code

The registry entry has no remote endpoint or installable package.

What the publisher says

From the Trust Layer repository's README, as published. We do not edit it. Read it on GitHub

Registro de Confianza para Agentes

Servidor MCP que actúa como notario verificable de agentes de IA: registra su identidad y cada acción relevante en un log inmutable y criptográficamente verificable — sin certificar ni juzgar si esas acciones cumplen ninguna normativa.

Ver la especificación completa (arquitectura, modelo de datos, plan de validación) en el documento de diseño del proyecto.

Estructura

src/
  domain/            # lógica de negocio pura, sin dependencias externas
    models.py        # AgenteIA, RegistroAuditable
    hash_chain.py     # integridad criptográfica: hash-chain + firma
    ports.py          # interfaces que la infraestructura implementa
    servicios.py       # casos de uso: VerificarIdentidadAgente, RegistrarAccionAuditable
  infrastructure/
    adaptadores_memoria.py   # implementación en memoria (tests, Fase 1)
    postgres_schema.sql      # esquema para cuando se conecte Postgres real
  mcp_server/
    servidor.py        # expone los casos de uso como herramientas MCP
tests/
  unit/          # dominio puro, sin DB
  integration/   # (pendiente: contra Postgres real)
  contract/      # garantiza el schema que ve cualquier cliente MCP
docs/adr/        # decisiones de arquitectura, con su razonamiento

Uso

pip install -e ".[dev]"
pytest                          # corre toda la suite
python -m src.mcp_server.servidor   # levanta el servidor MCP

Estado

Fase 1, primera versión: verificaridentidadagente + registraraccionauditable + verificar_historial, con adaptadores en memoria. Sin pagos, sin certificación normativa — ver ADR 0001 y el documento de diseño para el porqué de cada decisión.

Listado en el MCP Registry oficial como io.github.Ernesmar/trust-layer.

Nothing above is checked by us. What we check is on the safety report.

Trust Layer: common questions

Is Trust Layer MCP server safe?
Mostly: it is graded B (70/100). Read the Trust Layer safety report
Does Trust Layer need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Trust Layer maintained?
The last commit was 41 days ago (2026-09-23). The latest release is v0.1.0.