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-30T11:17:29.772446+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.timzinin.com/mcp/us-brand-intelligence",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-30T11:17:29.772446+00:00",
"registry_status": null,
"subject": {
"id": "com.timzinin.api/us-brand-intelligence",
"kind": "mcp"
},
"tools": {
"names": [
"pricing_info",
"us-brand-action-queue",
"us-brand-evidence-chronology-builder",
"us-brand-evidence-citation-table",
"us-brand-evidence-snapshot-diff",
"us-brand-federal-award-snapshot",
"us-brand-offer-evidence-normalizer",
"us-brand-signal-batch-splitter",
"us-brand-signal-brand-summary",
"us-brand-signal-brief-composer",
"us-brand-signal-confidence-gate",
"us-brand-signal-cooccurrence-analyzer",
"us-brand-signal-crm-field-mapper",
"us-brand-signal-cross-tabulator",
"us-brand-signal-merge-report",
"us-brand-signal-metrics-aggregator",
"us-brand-signal-policy-simulator",
"us-brand-signal-rule-router",
"us-brand-signal-sequence-transition-analyzer",
"us-brand-signal-sla-checker",
"us-brand-signal-webhook-payload-builder"
],
"names_truncated": false,
"sha256": "35f35372b7fad0593467559f537128e6baec04429b6076ef114053f37753159b"
},
"tools_complete": true,
"tools_observed_at": "2026-10-30T11:17:29.772446+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