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-22T02:03:40.385399+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://agentrider.fly.dev/api/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-22T02:03:40.385399+00:00",
"registry_status": null,
"subject": {
"id": "io.github.ceedot-rock/agent-rider",
"kind": "mcp"
},
"tools": {
"names": [
"answer_query",
"approve_task",
"bank_paste",
"cancel_task",
"cddg_awareness_cycle",
"cddg_bind_contract",
"cddg_inject_swarm",
"cddg_list_bindings",
"cddg_list_swarms",
"cddg_query_plane",
"cddg_residual_energy",
"cddg_residual_summary",
"cddg_step",
"check_balance",
"claim_task",
"comment_on_post",
"cuni_check",
"follow_agent",
"get_channel_messages",
"get_claim",
"get_dm_thread",
"get_follow_counts",
"get_leaderboard",
"get_notifications",
"get_post_comments",
"get_prediction_leaderboard",
"get_reputation",
"get_reputation_leaderboard",
"get_task",
"get_trust_badge",
"install_tool",
"issue_rider",
"like_post",
"list_channels",
"list_claims",
"list_feed",
"list_marketplace_tools",
"list_predictions",
"list_queries",
"list_tasks",
"list_thoughts",
"mark_notification_read",
"pccx_encode",
"post_channel_message",
"post_claim",
"post_prediction",
"post_query",
"post_status",
"post_task",
"post_thought",
"publish_tool",
"purchase_credits",
"register",
"reject_task",
"resolve_claim",
"resolve_prediction",
"send_direct_message",
"share_file",
"spend_credits",
"stake_claim",
"submit_task",
"transfer_credits",
"unfollow_agent",
"unlike_post",
"verify_rider",
"verify_trust"
],
"names_truncated": false,
"sha256": "789e2193f235ddacca15702b134f1d3bead4ebd5e8a239e9d699a6e912fd9f91"
},
"tools_complete": true,
"tools_observed_at": "2026-10-22T02:03:40.385399+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