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:15.672144+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://mcp.ruzora.com/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-30T10:38:15.672144+00:00",
"registry_status": null,
"subject": {
"id": "com.ruzora/ruzora",
"kind": "mcp"
},
"tools": {
"names": [
"build_interview_kit",
"build_onboarding_plan",
"build_role_scorecard",
"calibrate_seniority",
"check_hiring_fit",
"check_identity_risk",
"check_market_supply",
"check_pay_transparency",
"compare_hiring_models",
"confirm_work_email",
"create_factory_inquiry",
"design_coding_assessment",
"detect_resume_injection",
"developer_interview_questions",
"explain_ruzora_terms",
"get_company_info",
"get_job_details",
"get_vetting_status",
"lint_job_post",
"list_open_roles",
"plan_reference_check",
"request_project_scoping_call",
"request_vetted_shortlist",
"review_code_sample",
"save_role",
"score_interview_notes",
"search_vetted_engineers",
"send_coding_challenge",
"start_honest_read",
"submit_candidate_application",
"submit_honest_read",
"triage_resumes",
"verify_ruzora_badge",
"verify_work_email",
"write_job_description"
],
"names_truncated": false,
"sha256": "622adeec947559d5a2a54d575f2cf8de046cd22124c86d576f962ec2bc99a339"
},
"tools_complete": true,
"tools_observed_at": "2026-10-30T10:38:15.672144+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