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-25T17:37:03.921556+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://replicate-mcp.sena-labs.dev/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-25T17:37:03.921556+00:00",
"registry_status": null,
"subject": {
"id": "sena-labs/replicate-mcp-server",
"kind": "mcp"
},
"tools": {
"names": [
"replicate_batch_start",
"replicate_batch_status",
"replicate_cancel_prediction",
"replicate_cancel_training",
"replicate_chat",
"replicate_clone_voice",
"replicate_create_training",
"replicate_embed_text",
"replicate_estimate_cost",
"replicate_generate_3d",
"replicate_generate_audio",
"replicate_generate_image",
"replicate_generate_speech",
"replicate_generate_video",
"replicate_get_deployment",
"replicate_get_model_schema",
"replicate_get_prediction",
"replicate_get_training",
"replicate_inpaint",
"replicate_lipsync",
"replicate_list_deployments",
"replicate_list_predictions",
"replicate_list_trainings",
"replicate_pipeline_start",
"replicate_pipeline_status",
"replicate_recommend_model",
"replicate_refresh_models",
"replicate_remove_background",
"replicate_run_deployment",
"replicate_run_model",
"replicate_search_models",
"replicate_segment",
"replicate_transcribe_audio",
"replicate_upload_file",
"replicate_upscale_image",
"replicate_vision"
],
"names_truncated": false,
"sha256": "4ec1243f67a0504a1c662b6a9b9c7d9d2cc280919a46054820c95bbcb3f90040"
},
"tools_complete": true,
"tools_observed_at": "2026-10-25T17:37:03.921556+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