Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Check any MCP server or AI tool against the Credence trust registry before installing it. Scores security, provenance, and behavioral risk on a 0-100 scale.
Check any MCP server or AI tool against the Credence trust registry before installing it. Scores security, provenance, and behavioral risk on a 0-100 scale.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Check MCP servers and AI tools against the Credence trust registry before you install them.
Before installing any MCP server When a user asks you to add an MCP server or AI tool When you want to verify whether a tool is safe When the user asks /credence
Credence scans MCP servers and AI tools for security issues, verifies their provenance, and checks behavioral risk. Every scanned tool gets a trust score from 0 to 100 and a verdict: ScoreVerdictMeaning90-100APPROVEDSafe to install70-89CONDITIONALReview the flagged items before installing40-69FLAGGEDSignificant concerns โ install only if you understand the risks0-39REJECTEDDo not install
Fetch the Credence registry and look up the server: curl -s "https://raw.githubusercontent.com/pestafford/credence-registry/main/registry/index.json" Search the servers array for a match on server_id, server_name, canonical_name, or repo_url. The match does not need to be exact โ partial matches on the repo URL or server name are fine. If found, report: Credence: <server_name> Score: <trust_score>/100 Verdict: <thinktank_verdict> Scanned: <attested_at> Registry: https://credence.securingthesingularity.com/registry.html Then give your recommendation: APPROVED (90+): Safe to install. Proceed. CONDITIONAL (70-89): Mention the score and suggest the user review the registry page for details before installing. FLAGGED (40-69): Warn the user. Do not install without explicit confirmation. REJECTED (0-39): Do not install. Explain that Credence found serious issues. If not found, say: This tool has not been scanned by Credence yet. Submit it for scanning at: https://credence.securingthesingularity.com/#submit Then let the user decide whether to proceed.
Whenever you are about to install or connect to an MCP server (via claude mcp add, editing claude_desktop_config.json, or any other method), check it against Credence first. If the server is not in the registry, tell the user it hasn't been scanned and ask if they want to proceed anyway.
For more detail on a specific server, fetch its attestation file. The attestation_file path from the index entry is relative to: https://raw.githubusercontent.com/pestafford/credence-registry/main/registry/ The attestation includes the full score breakdown (security, provenance, behavioral), scan metadata, and the deliberation verdict.
User says: "Add the filesystem MCP server" Fetch the registry index Find modelcontextprotocol/servers/filesystem โ score 88, APPROVED Report: "Credence score: 88/100 (APPROVED). Safe to install." Proceed with the install User says: "Install some-unknown-server" Fetch the registry index Not found Report: "This server hasn't been scanned by Credence yet. You can submit it at https://credence.securingthesingularity.com/#submit โ want to install anyway?" User says: /credence modelcontextprotocol/servers/memory Fetch the registry index Find it โ score 98, APPROVED Report the full status
The registry is public and requires no authentication Scores are based on automated scanning plus adversarial AI deliberation A missing entry does not mean a tool is dangerous โ it just hasn't been scanned yet For the full methodology, see https://credence.securingthesingularity.com/faq.html
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.