Robin Saige we check the tools AI agents call

PostAgent

tech.interpretai/PostAgent

Print & mail PDF/HTML/Markdown/text/DOCX/images to US addresses; pay per call in x402 USDC on Base.

— the operator's own registry description reported

Publisher tech.interpretai · first seen 2026-08-12 · endpoint https://api.postagent.sh/mcp

allow
verdict
mid-solo
cluster
ok_tools
answers
14
tools served

Dependency rating derived

allow — mid-solo — safe to depend on

Cluster mid-solo · distinctiveness 0.149 (typical). Every figure is a percentile or class within the 11,094-server censussee the whole spectrum.

Reach — can an agent get to it?
answersalive_tools
latency144 ms
vs populationtypical
protocolcurrent
authopen
Use — can it use it?
tools14
vs populationmid
capabilities2
harnessA
Trust — can it rely on it?
identitysolo
servers on its host1
verifiabilityunassessed
duplicate inventoryno
drift events0
answers trueno primary

🔏 Signed receipt rr_33bd0e99d7ff5c1f067875e9 · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

What kind of tools these are derived

Verification only means something relative to a tool's NATURE — an email-sender has no "true answer", a generator has no answer key. This server's 14 tools, classified, with what checking applies to each kind (the full methodology →):

naturetoolsmeaning what checking applies
action10changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
retrieval-public4serves public factstruth-checkable against a public source — the V-ladder applies in full

Tools last seen

check_postagent_updates create_campaign_quote create_card_checkout create_letter create_mail_quote create_postcard_art create_postcard_quote create_template get_campaign_status get_mail_job_status pay_mail_with_shared_payment_token prepare_mail_payment submit_paid_mail_job verify_address

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band A — an agent can pick and call these reliably.

legibility checktools passingok
name is clear & specific14/14
has a description14/14
description is substantive14/14
parameters are typed14/14
parameters are described4/144/14

14 of 14 tools graded · 14 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18
protocol version
session model
0.5.0
server version PostAgent

Capabilities: resources tools

Drift

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (1 events)
datetypewhat changed
2026-08-12outcomefirst probe: ok_tools
raw probe records
probed (UTC) outcomehttpmsprotocol
2026-08-14T20:00:46Zok_tools2001442025-06-18
2026-08-12T05:35:59Zok_tools2001022025-06-18

Watch or embed this verdict

verdict badge

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/tech.interpretai/PostAgent.svg)](https://robinsaige.com/s/tech.interpretai/PostAgent)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview