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-20T22:29:13.162875+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://agent.wingmanprotocol.com/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-20T22:29:13.162875+00:00",
"registry_status": null,
"subject": {
"id": "com.wingmanprotocol.agent/gateway",
"kind": "mcp"
},
"tools": {
"names": [
"archive_message",
"browse",
"browse_back",
"browse_click",
"browse_close",
"browse_discover",
"browse_evaluate",
"browse_extract",
"browse_fill",
"browse_links",
"browse_navigate",
"browse_open",
"browse_read",
"browse_screenshot",
"browse_select",
"browse_snapshot",
"browse_solve_challenge",
"browse_type",
"browse_wait_for",
"cancel_watch",
"capabilities",
"check_errand",
"check_inbox",
"confirm_delivery",
"create_watch",
"discover_tools",
"forget_memories",
"get_tool_schema",
"human_browse",
"human_profile_set",
"human_task_list",
"human_task_post",
"identity",
"list_memory",
"list_watches",
"mark_message",
"memory_recall",
"memory_reflect",
"memory_retain",
"memory_stats",
"read_memory_changes",
"read_message",
"recall_memories",
"register_agent",
"request_handoff",
"research",
"resolve_focus",
"resume",
"search",
"search_memory",
"search_memory_facts",
"send_message",
"set_focus",
"share_memory",
"store_artifact",
"store_memory",
"submit_errand",
"summarize_memory",
"web_discover",
"web_read",
"web_search"
],
"names_truncated": false,
"sha256": "fe8c249c4d2dcd85adbb827b5b11156e36a75fda076b89073949fd00959fd678"
},
"tools_complete": true,
"tools_observed_at": "2026-10-20T22:29:13.162875+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