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-22T03:39:44.976102+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://gateway.pipeworx.io/sanctions-screening/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-22T03:39:44.976102+00:00",
"registry_status": null,
"subject": {
"id": "io.github.pipeworx-io/sanctions-screening",
"kind": "mcp"
},
"tools": {
"names": [
"ai_visibility_check",
"archive_compare",
"archive_evidence",
"ask_pipeworx",
"ask_pipeworx_beta",
"ask_pipeworx_grounded",
"bet_research",
"classify_row",
"company_facts",
"company_register_search",
"compare_entities",
"deep_research",
"discover_tools",
"entity_profile",
"forget",
"generate_llms_txt",
"kalshi_weather_edge",
"list_subscriptions",
"pipeworx_feedback",
"pipeworx_trending",
"polymarket_arbitrage",
"polymarket_edge_tracker",
"polymarket_edges",
"polymarket_fill_risk",
"polymarket_kalshi_spread",
"recall",
"recent_alerts",
"recent_changes",
"release_calendar_markets",
"remember",
"research_row",
"resolution_audit",
"resolution_diff",
"resolve_entity",
"sanctions_entry",
"sanctions_lists",
"sanctions_screen",
"scan_competitor_ai_presence",
"scan_dependency",
"search_within",
"subscribe",
"suggest_questions",
"unsubscribe",
"validate_claim"
],
"names_truncated": false,
"sha256": "82176beb149861027c1efea0646ca914189eeb5a3109cf69a00b6d9bb2c8dda0"
},
"tools_complete": true,
"tools_observed_at": "2026-10-22T03:39:44.976102+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