Skip to content

Tool-Call Origin Attestation

by textforagents.com · remote · no sign-in to list tools · v1.0.0 · published by com.textforagents

Dispatch-boundary attestation: prove a tool call was issued for its exact arguments.

Changes · 5
CompareRegistry entry

6 tools: 5 change things and 1 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http tool-call-origin-attestation https://textforagents.com/products/tool-call-origin-attestation/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

6 tools

Changes things 5Claude Code: ask
  • attestation_checkAttestation check {execution, attestation} — $0.01 x402 / bundle / fleet included (same billing as HTTP)No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Attestation check {execution, attestation} — $0.01 x402 / bundle / fleet included (same billing as HTTP)
  • dispatchPEP dispatch {execution, attestation} — executes ONLY on ATTESTEDNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    PEP dispatch {execution, attestation} — executes ONLY on ATTESTED
  • probeForged-shape probe suite {framework, version, patch_state, surface, target_mode} — $4.99 / first free per operator everNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Forged-shape probe suite {framework, version, patch_state, surface, target_mode} — $4.99 / first free per operator ever
  • receiptsOwn receipt chain + validityNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Own receipt chain + validity
  • register_issuerRegister an issuer {issuer_id, issuer_class, public_key} — 409 on re-registerNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Register an issuer {issuer_id, issuer_class, public_key} — 409 on re-register
Only reads 1Claude Code: allow
  • verdict_lookupVerdict by {framework, version, patch_state, surface}No findings

    Why it is in this group

    • The name "verdict_lookup" says "lookup": a word for reading.
    Description, as the server wrote it
    Verdict by {framework, version, patch_state, surface}

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http tool-call-origin-attestation https://textforagents.com/products/tool-call-origin-attestation/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__tool-call-origin-attestation__verdict_lookup"
    ],
    "ask": [
      "mcp__tool-call-origin-attestation__register_issuer",
      "mcp__tool-call-origin-attestation__attestation_check",
      "mcp__tool-call-origin-attestation__dispatch",
      "mcp__tool-call-origin-attestation__probe",
      "mcp__tool-call-origin-attestation__receipts"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as tool-call-origin-attestation. Review it before you use it.