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-20T20:27:18.491091+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://bidda.com/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-20T20:27:18.491091+00:00",
"registry_status": null,
"subject": {
"id": "com.bidda/bidda-compliance",
"kind": "mcp"
},
"tools": {
"names": [
"browse_topics",
"check_action_compliance",
"compare_jurisdictions",
"consult_node",
"create_attestation",
"create_control_attestation",
"drift_check",
"gap_check",
"get_audit_pack",
"get_crosswalk",
"get_dependency_chain",
"get_jurisdiction_bundle",
"get_latest_changes",
"get_mitre_mapping",
"get_node",
"get_run",
"list_pillars",
"obligation_deltas",
"open_run",
"oscal_assessment_results",
"point_in_time",
"record_run_entry",
"seal_run",
"search_nodes",
"watch_changes"
],
"names_truncated": false,
"sha256": "cfec8fe38b5a05fecdacd6f8ae09956c2ac82084044483c10f1f3a9157ab9d9f"
},
"tools_complete": true,
"tools_observed_at": "2026-10-20T20:27:18.491091+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