Credda Trust

io.github.Credda-ioPublished by GitHub account Credda-iov0.1.3Updated Oct 24, 2026

Check a counterparty's verifiable Credda trust record; verify or present signed credentials.

VerifiedSTDIODesktop onlySecurity & MonitoringBusiness & Commerce

Overview

AI-generated overview

Lets an assistant look up a counterparty's Credda trust record and verify or present signed credentials.

What you can do
Credda Trust exposes Credda's trust and credential service to an assistant. It provides public read and verify tools for checking a counterparty's verifiable trust record and validating signed credentials, plus platform tools for score reads, monitors and usage when an API key is supplied. It can also mint a trust token and present a credential for a given external user id.
When to use it
Useful when an assistant needs to check whether a counterparty, vendor or user has a verifiable trust record before a transaction or onboarding step, or when signed credentials must be verified or presented as part of a workflow.
Requirements
Runs locally over stdio, typically via npx from the npm package @credda/mcp-server, so Node.js is needed. Optional environment variables: CREDDA_API_KEY enables the platform tools, CREDDA_USER_ID is needed only by the token-minting and credential-presenting tools, and CREDDA_API_BASE overrides the API base URL. Network access to the Credda API is required.
Before you install
The public read and verify tools work without credentials, but CREDDA_API_KEY unlocks score reads, monitors and usage data and should be treated as a secret. The token-minting and credential-presenting tools act on behalf of the external id in CREDDA_USER_ID, so confirm which identity is being presented. Trust lookups and credential checks send identifiers to the Credda API, a third party.

Installation

In SourceWeft

  1. Open Credda Trust in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.3LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.