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-30T10:38:17.441107+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.scrubmytext.com/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-30T10:38:17.441107+00:00",
"registry_status": null,
"subject": {
"id": "com.scrubmytext/tools",
"kind": "mcp"
},
"tools": {
"names": [
"anchor_context_trace",
"cancel_approval",
"check_action",
"check_agent_readiness",
"check_approval",
"compare_quality_targets",
"compare_text",
"complete_action",
"create_signal",
"delete_signal",
"detect_secrets",
"fingerprint_action",
"get_quality_card",
"get_signal_events",
"inspect_text",
"list_quality_cards",
"lock_action",
"lock_action_intent",
"manage_action_challenge",
"manage_action_compensation",
"manage_action_quorum",
"manage_action_reconciliation",
"manage_agent_escalation",
"manage_agent_stop",
"manage_attention_budget",
"manage_authority_delegation",
"manage_context_rights",
"manage_context_status",
"manage_disclosure_budget",
"manage_resource_lease",
"manage_task_contract",
"manage_task_deadline",
"manage_task_handoff",
"manage_terms_pin",
"match_policy_requirements",
"prepare_for_agent",
"record_action_receipt",
"record_quality_observation",
"redact_sensitive_text",
"release_action",
"request_approval",
"request_quality_correction",
"reserve_action_budget",
"rework_text",
"sanitize_agent_context",
"scan_untrusted_text",
"scrub_text",
"validate_output",
"verify_signed_signal"
],
"names_truncated": false,
"sha256": "286c464f9e095809e05c8f0cadc5e0edd5f1d8fa3bb87e5752b453d3a9ca90ed"
},
"tools_complete": true,
"tools_observed_at": "2026-10-30T10:38:17.441107+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