For teams using external agents and MCP servers: inspect measured evidence, watch changes, and keep a record of what your team accepted. Unknown evidence stays explicit.
Have a client configuration? Extract and check its public endpoints locally. Maintaining integrations for clients? Explore the agency pilot.
Runtime observation: 2026-10-22T11:36:27.024079+00:00 · State: live
Watch availability, tools and parameter schemas, authentication access, endpoint changes and lifecycle notices. Only complete observed schemas are compared. OAuth scope and consent-screen changes are not currently measured.
Sign in to watch this MCP serverSign-in required. Agent and MCP watches share the existing Free / Pro / Enterprise budget. Manage watches.
{
"auth": "anonymous",
"availability": "live",
"endpoint": "https://api.tamgara.com/api/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-22T11:36:27.024079+00:00",
"registry_status": null,
"subject": {
"id": "com.tamgara/tamgara",
"kind": "mcp"
},
"tools": {
"names": [
"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"
],
"names_truncated": false,
"sha256": "1c96cb27ad54ccdc8ef022861cffa0bae0a9f3b1cfcf17c09342e43aea931997"
},
"tools_complete": true,
"tools_observed_at": "2026-10-22T11:36:27.024079+00:00",
"version": null
}Keep an accepted snapshot in agents.lock.json. CI compares it with current evidence and returns allow, review or block with reasons, before/after data and policy hashes.
Default gaps require review. Configure stricter handling explicitly. A lock records your acceptance; it is not a supplier attestation.
API referenceVerified domain owners can publish up to five exact-match sandbox fixtures and opt in to a test run. Results include fixture version, latency, output hashes and comparable regressions. Cost remains unknown when unobserved.
Run with POST /api/v1/dependencies/task-checks?domain=… while signed in. Read the schema and example in the integration guide.
Domain control, a declared business identifier and an active name-matched company record are separate evidence. Zero verified records means zero recorded proof.
Current coverage and measurement date · Verify your domainVerify issuer signatures, subject and credential freshness using the public key document. Keep its task evidence categories separate from Agenstry measurements.
A valid SEAL does not establish domain ownership, legal identity, key possession or execution permission.
Credential verification API · Issuer documentationSmithery endpoint migration · Agent monitoring · Methodology