mcpField
C

Credda Trust

Local
api.credda.ioSecurity
Visit website

About Credda Trust

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

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "credda-io-credda-trust": {
      "command": "npx",
      "args": [
        "-y",
        "@credda/mcp-server"
      ],
      "env": {
        "CREDDA_API_KEY": "<CREDDA_API_KEY>",
        "CREDDA_USER_ID": "<CREDDA_USER_ID>",
        "CREDDA_API_BASE": "<CREDDA_API_BASE>"
      }
    }
  }
}
Run commandnpx -y @credda/mcp-server
Environment variables to set
CREDDA_API_KEYSecretOptional Credda platform API key. Without it the public read/verify tools still work; with it the platform tools (score reads, monitors, usage) are enabled.
CREDDA_USER_IDOptional. The external id this server presents credentials for; needed only by mint_my_trust_token and present_my_credential (with CREDDA_API_KEY).
CREDDA_API_BASEOptional override for the Credda API base URL, e.g. for a staging deployment.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@credda/mcp-server0.1.3

Tools

15

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
tokenstringYesThe counterparty's Credda share token

Details

The maintainer has not added details yet. Check the README in the repository.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.