get_attestation
Retrieve a stored validation attestation by its ID. Returns the full attestation record including schema hash, payload hash, validation result, and cryptographic signature.
LABSCO SUMMARY
Signing the validation result is the whole idea — a pass from an agent is a claim, and a signed attestation is evidence.
Schema validation itself is a solved problem available in every language for free. What is not free is proving afterwards that a payload was valid at a point in time, when the party who needs convincing is not the party who ran the check. That is the case this serves: an agent asserting it validated something is worth little, and a signed attestation that a third party can verify independently is worth something. Whether you need that depends entirely on whether anyone downstream has reason to doubt the caller — inside your own pipeline, a library does the job.
What it is
A JSON Schema validator that issues cryptographic attestations: validate produces a signed record of the result, verify checks the signature, and get_attestation retrieves a stored one by id.
What you get
- validate checks a payload against a JSON Schema and returns a signed attestation rather than a bare pass or fail.
- verify confirms the signature on an attestation, so the result can be checked by someone who was not there when it ran.
- get_attestation retrieves a stored attestation in full by its id.
Requirements
RAPIDTOOLS_API_KEY.
Setup effort
One command plus a key — npx -y @tailoredtools/mcp-server, then supply credentials
USE CASES
01
Proving a payload was valid when it was accepted
Validate against the schema and keep the signed attestation, so the check can be demonstrated later rather than asserted.
02
Checking someone else's claim
Verify the signature on an attestation you were handed, confirming it without trusting whoever produced it.
3 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
validate
Validate a JSON payload against a JSON Schema. Returns a signed attestation proving validation occurred. Deterministic: same inputs always produce the same result.
verify
Verify the cryptographic signature of a validation attestation. Confirm that a previous validation result has not been tampered with.
BEFORE YOU INSTALL
What to know first
Tools you get
3 tools when we connected. The API key comes from a subscription checkout, with no free tier.
Requires
- npx on PATH
- RAPIDTOOLS_API_KEY in your environment
Where it runs
All 3 documented clients run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 3 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @tailoredtools/mcp-serverMCP Clients
Claude Code, Cursor
JSON
{
"mcpServers": {
"rapidtools": {
"command": "npx",
"args": [
"-y",
"@tailoredtools/mcp-server"
],
"env": {
"RAPIDTOOLS_API_KEY": "<YOUR_RAPIDTOOLS_API_KEY>"
}
}
}
}VS Code
VS CODE · JSON
{
"servers": {
"rapidtools": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@tailoredtools/mcp-server"
],
"env": {
"RAPIDTOOLS_API_KEY": "<YOUR_RAPIDTOOLS_API_KEY>"
}
}
}
}
