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-22T17:00:36.279676+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://afterlaunch.io/api/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-22T17:00:36.279676+00:00",
"registry_status": null,
"subject": {
"id": "io.afterlaunch/agentic-growth-marketing",
"kind": "mcp"
},
"tools": {
"names": [
"accept_move",
"add_competitor",
"adopt_move_result",
"archive_move",
"correct_move_publication",
"create_checkout",
"create_topup",
"disconnect_connection",
"dismiss_gap",
"get_activity",
"get_business_context",
"get_claims",
"get_competitors",
"get_content_calendar",
"get_enrollment",
"get_experiments",
"get_kb_page",
"get_loop_status",
"get_move",
"get_outcomes",
"get_output",
"get_scoreboard",
"get_seo",
"get_setup_snippet",
"get_snapshot",
"get_standup",
"get_visibility",
"get_voice_profile",
"list_connections",
"list_feed",
"list_kb_pages",
"list_outputs",
"list_queue",
"list_tracked_prompts",
"pick_up_job",
"poll_connection",
"propose_move",
"record_claim",
"record_content",
"record_insight",
"record_profile",
"record_voice_rule",
"redraft_output",
"refresh_scan",
"replenish_feed",
"report_job",
"revise_move",
"set_output_status",
"set_voice_axes",
"ship_move",
"skip_move",
"start_connection",
"track_prompt",
"undo_move",
"untrack_prompt",
"update_draft",
"whoami",
"withdraw_move"
],
"names_truncated": false,
"sha256": "3a205679e87fdc7d81006068563eb30682630f1bb7d765587bc98e8bf8d4b3cf"
},
"tools_complete": true,
"tools_observed_at": "2026-10-22T17:00:36.279676+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