Verify artifacts produced by AI agents: schema, emptiness, provenance, authority.
Connect Remote server
claude mcp add --transport http attest https://attest.rta.lat/mcp
{
"mcpServers": {
"attest": {
"url": "https://attest.rta.lat/mcp"
}
}
}
{
"servers": {
"attest": {
"type": "http",
"url": "https://attest.rta.lat/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://attest.rta.lat/mcp
Tools 2 found in our last check
verify_artifactVerify an artifact produced by an AI agent before accepting or paying for it. Four independent layers: schema conformance, whether there is anything inside (uniform lists, stubs, truncations), provenance bound to the artifact hash, and whether a signed mandate permitted the acti…
verify_artifact_batchVerify several artifacts at once — a scan report, a list of findings, a set of tool descriptions. One call, one verdict per artifact, plus a summary of how many were accepted, need review, or were rejected. Use when an agent produced a batch (twenty findings from a security scan…
Details
| Endpoint | https://attest.rta.lat/mcp (Streamable HTTP) |
| First published | 4 Nov 2026 |
| Last updated | 4 Nov 2026 |
| Registry name | io.github.mrpkk/attest |
More ai and media servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
