One command to verify MCP trust
curl -s https://marketnow.site/api/atc?action=verify&card_id=ATC-2026-7777670 | jq
Returns:
{
"valid": true,
"sentinel_review_score": 10,
"decision_authority": "consumer",
"risk_level": "low"
}
What is this?
Agent Trust Cards (ATC) — Ed25519-signed identity cards for MCP servers. RFC 8032 + RFC 8785 JCS. Schema v1.1.0.
The ATC answers 4 questions:
- Identity (Ed25519 public key)
- Issuer (which CA vouches)
- Validity (valid/revoked)
- Review evidence (Sentinel score 0-10)
It does NOT answer should you trust it? — that is YOUR decision.
Also: verify Vibe receipts (mutual hop)
curl -s https://marketnow.site/api/atc?action=verify-vibe-receipt | jq .valid
# -> true (bidirectional Ed25519 verification)
Submit your MCP server for free audit
curl -X POST https://marketnow.site/api/submit-skill -H "Content-Type: application/json" -d x27{"repo_url": "https://github.com/you/your-mcp-server"}x27
10-layer audit. Ed25519 ATC. Catalog listing. All free.
Links: https://marketnow.site/submit | https://github.com/edgarfloresguerra2011-a11y/marketnow
Top comments (1)
I found the use of Ed25519 signatures for Agent Trust Cards (ATC) to be particularly interesting, as it provides a robust and compact way to verify the identity and validity of MCP servers. The fact that the
curlcommand can verify the trust in a single step is quite convenient, and the JSON output provides a clear and machine-readable format for the verification results. I'm curious to know more about the Sentinel review score and how it's calculated, as it seems to play a key role in determining the risk level of an MCP server. Does the Sentinel score take into account any external factors, such as the server's reputation or user feedback?