com.craftedtrust/mcp-shield

MCPcommunitylive
v2.0.0com.craftedtrustUnknownUpdated 6mo agoGitHub

Trust verification for MCP servers. Check scores, scan for security issues, search 4,200+ servers.

Reference implementations showing how to make AI agents check CraftedTrust before connecting to any MCP server. If a server scores D or F, the agent refuses to connect. This is the "SSL certificate check for AI agents" pattern. Add CraftedTrust to your agent's MCP config: Your agent now has access to 6 tools: | Look up trust score by URL or npm name | | Trigger a live security scan | | Search…

Endpoint healthlive
checked 11 days ago · 291ms
100% of the last 5 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
6mo agoLast update
Package
Authorcom.craftedtrust
LicenseUnknown
Version2.0.0
Sourcemcp-registry
GitHubcybercraftsolutionsllc/trust-gated-agent-example
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface—
Security scan✓ CleanvHEAD · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

No tool declarations found in the source3mo ago

Forge read 1 source file from the repository archive and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

Reference implementations showing how to make AI agents check CraftedTrust before connecting to any MCP server. If a server scores D or F, the agent refuses to connect. This is the "SSL certificate check for AI agents" pattern. Add CraftedTrust to your agent's MCP config: Your agent now has access to 6 tools: | Look up trust score by URL or npm name | | Trigger a live security scan | | Search 4,200+ indexed MCP servers | | Ecosystem statistics | | Initiate USDC certification payment | | Verify…

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.