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-21T20:28:52.693454+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://relin.app/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-21T20:28:52.693454+00:00",
"registry_status": null,
"subject": {
"id": "io.github.earonesty/relin",
"kind": "mcp"
},
"tools": {
"names": [
"archive_source",
"cancel_queued_retries",
"check_portal_host",
"create_alert_channel",
"create_api_key",
"create_app",
"create_destination",
"create_endpoint",
"create_portal_host",
"create_portal_session",
"create_source",
"delete_endpoint",
"delete_event_type",
"describe_relin",
"ensure_webhook_setup",
"get_app",
"get_endpoint",
"get_event_detail",
"get_message",
"get_metrics_summary",
"get_portal_settings",
"get_setup_guide",
"get_slack_connect_url",
"get_webhook_setup_status",
"list_alert_channels",
"list_api_keys",
"list_apps",
"list_delivery_attempts",
"list_destinations",
"list_endpoints",
"list_event_types",
"list_message_attempts",
"list_messages",
"list_open_issues",
"list_portal_hosts",
"list_recent_events",
"list_recipients",
"list_retry_jobs",
"list_sources",
"list_supported_webhook_shapes",
"replay_event",
"replay_events",
"replay_message",
"resolve_anomalies",
"retry_failed_deliveries",
"revoke_api_key",
"rotate_endpoint_secret",
"rotate_source_token",
"save_portal_settings",
"send_message",
"update_endpoint",
"upsert_event_type",
"upsert_recipient"
],
"names_truncated": false,
"sha256": "8555e9b672dfd6e25c8530ccaac1b688fe810670015322f939ec89672d2fdab5"
},
"tools_complete": true,
"tools_observed_at": "2026-10-21T20:28:52.693454+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