Credda Trust

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/credda-io-credda-trust

About

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools

10 read · 2 write · 1 delete · 2 not yet classified

Secrets

1 (API keys, tokens or passwords)

Install scripts

Not scanned yet

Runs as

Node.js package

Tools (15)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

• check_delivery_receiptsCheck a counterparty agent's delivery record

  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…

• check_trustCheck a counterparty's Credda trust

  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.

• create_score_monitorCreate a continuous score monitor

  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.

• delete_score_monitorDelete a score monitor

  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.

• explain_user_scoreExplain a user's score factor by factor

  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.

• get_my_usageRead your own API key's usage and quota

  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.

• get_trust_exportGet a counterparty's portable trust export

  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.

• get_user_scoreRead one of your platform's users' Credda score

  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.

• list_score_monitorsList your platform's score monitors

  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.

• list_webhook_event_typesList the webhook event types Credda can send

  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.

• mint_my_trust_tokenMint a fresh trust token to present to a counterparty

  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.

• present_my_credentialPresent your Credda trust credential in one call

  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.

• present_my_delivery_receiptsPresent your own delivery record to a counterparty

  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.

• verify_trust_credentialVerify a presented Credda credential (offline)

  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.

• verify_verifiable_credentialVerify a presented W3C Verifiable Credential (offline)

  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.

Signals

Weekly downloads

21

Last release

Jul 24, 2026 (3 months ago)

Last package publish

Aug 19, 2026 (2 months ago)

From the package registry.

Details

Registry name

io.github.Credda-io/credda-trust

Version

0.1.3

Auth

API key

Packages

npm @credda/mcp-server

License

License unknown

Website

api.credda.io

First seen

Oct 24, 2026

Last checked

Oct 25, 2026

Source

Official MCP Registry