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-20T23:36:46.452755+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://v12dfs-production.up.railway.app/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-20T23:36:46.452755+00:00",
"registry_status": null,
"subject": {
"id": "io.github.jorgeperez0825/v12-dfs",
"kind": "mcp"
},
"tools": {
"names": [
"admin_issue_key",
"agent_guide",
"betting_agent_guide",
"betting_analyze_prop",
"betting_best_bets",
"betting_build_parlay",
"betting_cross_book",
"betting_game_lines",
"betting_game_model",
"betting_log_bet",
"betting_market",
"betting_market_movers",
"betting_matchup",
"betting_my_bets",
"betting_player_form",
"betting_scan_edges",
"betting_settle_bet",
"betting_sharp",
"contest_advice",
"contest_semaforo",
"fill_template",
"generate_lineups",
"get_slate_players",
"health_check",
"health_v12",
"list_contests",
"list_live_contests",
"list_presets",
"list_slates",
"run_mlb_postmortem",
"scout_field",
"slate_diff",
"slate_health",
"slate_refresh"
],
"names_truncated": false,
"sha256": "e8c52d58aefb0919f7ca9a17dcb504e908b58f0468401670229e4e3603ede4fe"
},
"tools_complete": true,
"tools_observed_at": "2026-10-20T23:36:46.452755+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