Should my agent depend on the MCP server com.tamgara/tamgara?

Verdict: allow — rich-slow-solo — safe to depend on As of 2026-08-15T11:28:18Z: a dated observation with receipts, not a warranty.

Tamgara

com.tamgara/tamgara

Fill in 1,000+ legal PDF templates in many languages, get a signed PDF back. Free, no API key.

— the operator's own registry description reported

Publisher com.tamgara · first seen 2026-08-12 · endpoint https://api.tamgara.com/api/mcp

allow

verdict

rich-slow-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — rich-slow-solo — safe to depend on

Cluster rich-slow-solo · distinctiveness 0.417 (moderate). Every figure is a percentile or class within the 11,094-server census — see the whole spectrum.

Reach — can an agent get to it?

answersalive_tools

latency513 ms

vs populationslow

protocolcurrent

authopen

Use — can it use it?

tools33

vs populationhigh

capabilities1

harnessA

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_44b91451329d4d01a0c4474a · 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.

Tools last seen

account_balance account_topup add_cover_page apply_scan_answers brief_cancel brief_confirm brief_create_checkout brief_ping brief_quote brief_status envelope_create envelope_send_invite envelope_status envelope_upload_final envelope_void fax_confirm fax_countries fax_create_checkout fax_ping fax_quote fax_status fill_pdf fill_template get_provider get_template info inspect_pdf list_categories list_languages list_locales list_providers pdf_from_images search_templates

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 check	tools passing	ok
name is clear & specific	33/33	✓
has a description	33/33	✓
description is substantive	32/33	32/33
parameters are typed	33/33	✓
parameters are described	31/33	31/33

33 of 33 tools graded · 33 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

1.0.0

server version tamgara

Capabilities: 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)

date	type	what changed
2026-08-12	outcome	first probe: ok_tools

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T19:58:33Z	ok_tools	200	513	2025-06-18
2026-08-12T05:33:47Z	ok_tools	200	535	2025-06-18

Watch or embed this verdict

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/com.tamgara/tamgara.svg)](https://robinsaige.com/s/com.tamgara/tamgara)

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