Credda Trust
NPM · @CREDDA/MCP-SERVER · SCANNED SEP 25
Check a counterparty's verifiable Credda trust record; verify or present signed credentials.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 32 of 97 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency6
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 36 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability89
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1810 tokens (~106/item across 17 items; 15 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_score_monitor" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Credda Trust MCP server?
Credda Trust runs locally as an npm package, launched with npx -y @credda/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @credda/mcp-server
claude mcp add credda-io-credda-trust -- npx -y @credda/mcp-server
{
"mcpServers": {
"credda-io-credda-trust": {
"command": "npx",
"args": [
"-y",
"@credda/mcp-server"
]
}
}
} {
"servers": {
"credda-io-credda-trust": {
"command": "npx",
"args": [
"-y",
"@credda/mcp-server"
]
}
}
} codex mcp add credda-io-credda-trust -- npx -y @credda/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"credda-io-credda-trust": {
"type": "local",
"command": [
"npx",
"-y",
"@credda/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add credda-io-credda-trust --command npx --arg -y --arg @credda/mcp-server
mcp_servers:
credda-io-credda-trust:
command: "npx"
args: ["-y", "@credda/mcp-server"] {
"McpServers": {
"credda-io-credda-trust": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@credda/mcp-server"
]
}
}
} assistant mcp add credda-io-credda-trust -t stdio -c npx -a -y @credda/mcp-server
{
"mcpServers": {
"credda-io-credda-trust": {
"command": "npx",
"args": [
"-y",
"@credda/mcp-server"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 −2
- Stability: pass → 0.83 functional
- 22 Sept 26 0
- Stability: 0.97 → pass security
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Analysed npm/@credda/mcp-server@0.1.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 97 packages
| Packages resolved | 97 |
|---|---|
| Deprecated | 1 |
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_delivery_receipts Check a counterparty agent's delivery record ~161
The evidence view for an agent-to-agent handshake: given the share token a counterparty hands you, returns their DELIVERY RECEIPTS — how many deliveries are recorded, how many a DISTINCT counterparty confirmed, how many were their own operator vouching for them (which never counts as confirmed), failures, disputes, and the on-time rate over confirmed deliveries — plus a signed W3C credential of that record you can offline-verify with verify_verifiable_credential. No API key needed. This is a DELIVERY RECORD, not a safety, alignment or capability rating, and never a recommendation: it tells you what was delivered and who confirmed it, and the decision stays yours.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | The counterparty's Credda share token |
No output schema declared.
No examples provided.
check_trust Check a counterparty's Credda trust ~121
Look up a counterparty's verifiable, deterministic Credda reliability score by their public share token — the token is a capability they hand you (e.g. in a profile URL or a handshake message), no API key needed. Returns the score, band, verified-platform count, and a signed credential you can offline-verify with verify_trust_credential. The score is a pure function of an append-only event ledger — never set or nudged by a human or an AI.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | The counterparty's Credda share token |
No output schema declared.
No examples provided.
create_score_monitor Create a continuous score monitor ~180
Watch one of your users' scores continuously instead of polling: an edge-triggered monitor fires a `monitor.triggered` webhook event when the score crosses DOWN through `belowScore` (also fires if the FIRST computed score is already below it), crosses UP through `aboveScore`, or when `onBandChange` is set and the band label changes. At least one condition is required. Requires CREDDA_API_KEY. A monitor is notification config only — it never affects a score.
| Name | Type | Req | Description |
|---|---|---|---|
| aboveScore | number | – | Fire when the score crosses UP through this threshold (0–100) |
| belowScore | number | – | Fire when the score crosses DOWN through this threshold (0–100) |
| onBandChange | boolean | – | Fire whenever the score band label changes |
| userId | string | yes | The user's external id on your platform |
No output schema declared.
No examples provided.
delete_score_monitor Delete a score monitor ~62
Delete one of your continuous score monitors by id (hard delete — a monitor is notification config, not ledger data, so nothing score-related is touched). Requires CREDDA_API_KEY.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The monitor id (from list_score_monitors) |
No output schema declared.
No examples provided.
explain_user_score Explain a user's score factor by factor ~107
The bias-free evidence view of a user's score: a plain-language summary plus the per-factor breakdown (completion rate, on-time rate, dispute rate, verification depth), platform trust, consistency, momentum, and confidence level. Requires CREDDA_API_KEY. This explains EVIDENCE only — Credda deliberately has no "evaluate/recommend this person" endpoint; the decision stays with you, made against transparent facts.
| Name | Type | Req | Description |
|---|---|---|---|
| userId | string | yes | The user's external id on your platform |
No output schema declared.
No examples provided.
get_my_usage Read your own API key's usage and quota ~95
Observability for the agent's own key: your platform's API usage per day (by status class), tier rate limit, monthly quota consumption, and busiest endpoints over the window. Requires CREDDA_API_KEY. Advisory observability only — usage never affects any score.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Trailing window in days (default 7, max 400 — days beyond Redis retention are served from durable daily rollups) |
No output schema declared.
No examples provided.
get_trust_export Get a counterparty's portable trust export ~91
Fetch the full portable, self-verifying trust bundle for a share token: current score, score history, and a signed W3C Verifiable Credential with a revocation pointer. Use this when you need more than the headline score — e.g. to check a counterparty's trend over time before a higher-stakes commitment.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | The counterparty's Credda share token |
No output schema declared.
No examples provided.
get_user_score Read one of your platform's users' Credda score ~103
Read a user's latest computed Credda reliability score by their external id (the id YOUR platform reports events under) — score, band, confidence, factor breakdown, and the formula version that computed it. Requires CREDDA_API_KEY. Read-only: the score is a pure, deterministic function of the append-only event ledger — no tool (and no AI) can set or nudge it.
| Name | Type | Req | Description |
|---|---|---|---|
| userId | string | yes | The user's external id on your platform |
No output schema declared.
No examples provided.
list_score_monitors List your platform's score monitors ~82
List your platform's continuous score monitors (cursor-paginated): each monitor's user, thresholds, band-change flag, active state, and when it last triggered. Requires CREDDA_API_KEY.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Cursor from a previous page (`nextCursor`) |
| limit | integer | – | Page size (default 50, max 100) |
No output schema declared.
No examples provided.
list_webhook_event_types List the webhook event types Credda can send ~100
The public outbound webhook event catalog — every event type the API can deliver (e.g. `score.updated`, `score.band_changed`, `monitor.triggered`), with a description and example payload per event, the common delivery envelope, and how to verify a delivery signature. No API key needed. Use it to discover what create_score_monitor and webhook subscriptions can notify you about. Webhooks are advisory: no event can change anyone's score.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mint_my_trust_token Mint a fresh trust token to present to a counterparty ~114
Mint a fresh Credda share token for YOUR OWN identity, to hand to a counterparty as your side of a trust handshake (they can then call check_trust on it, or you can fetch and hand them get_trust_export / verify_trust_credential's credential directly). Requires this MCP server to be configured with CREDDA_API_KEY and CREDDA_USER_ID — it never acts on a counterparty's behalf. Minting does not change your score; it only issues a new capability token.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
present_my_credential Present your Credda trust credential in one call ~127
Convenience wrapper for the agent-to-agent handshake: mints a fresh share token for YOUR OWN identity and immediately fetches its full portable trust export (score + history + signed W3C credential + revocation pointer) in a single tool call, instead of mint_my_trust_token followed by a separate get_trust_export round trip. Hand the returned token or credential to a counterparty so they can check_trust it or verify it offline. Requires this MCP server to be configured with CREDDA_API_KEY and CREDDA_USER_ID. Minting does not change your score.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
present_my_delivery_receipts Present your own delivery record to a counterparty ~120
Your side of the handshake: mints a fresh share token for YOUR OWN Credda-scored identity and fetches its signed delivery credential in one call — the counterparty-confirmed record of what you have actually delivered, which the other side can check offline. Requires this MCP server to be configured with CREDDA_API_KEY and CREDDA_USER_ID; it never acts on a counterparty's behalf. Minting issues a capability token — it does not change your score, and nothing you report about yourself is ever counted as confirmed evidence.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
verify_trust_credential Verify a presented Credda credential (offline) ~104
Offline-verify a signed Credda Verifiable Trust Credential (compact EdDSA JWT format) that a counterparty presented to you directly — e.g. in an agent-to-agent handshake — without a round trip to Credda. Checks the signature against Credda's published JWKS, plus issuer and expiry. Rejects (throws) on an invalid, expired, or tampered credential.
| Name | Type | Req | Description |
|---|---|---|---|
| credential | string | yes | The compact JWT credential string presented to you |
No output schema declared.
No examples provided.
verify_verifiable_credential Verify a presented W3C Verifiable Credential (offline) ~115
Offline-verify a W3C Verifiable Credential (VC-JWT) that a counterparty presented to you, resolving Credda's did:web DID document and checking the revocation status list. Use this for credentials in the wider W3C VC ecosystem format rather than verify_trust_credential's compact format. Rejects (throws) on an invalid, expired, revoked, or tampered credential.
| Name | Type | Req | Description |
|---|---|---|---|
| vcJwt | string | yes | The W3C Verifiable Credential (VC-JWT) presented to you |
No output schema declared.
No examples provided.
What is the Credda Trust MCP server?
Credda Trust is an MCP server listed in the public MCP registry as io.github.Credda-io/credda-trust. Check a counterparty's verifiable Credda trust record; verify or present signed credentials. This page covers its npm package (@credda/mcp-server).
Is the Credda Trust MCP server safe to use?
Credda Trust scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Credda Trust MCP server expose?
Credda Trust exposes 15 tools: check_trust, get_trust_export, verify_trust_credential, verify_verifiable_credential, mint_my_trust_token, and 10 more. Their descriptions and schemas cost roughly 1,682 tokens of context every time the server is loaded.
Is the Credda Trust MCP server still maintained?
Credda Trust is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.