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-25T16:22:16.016076+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://mcp.wearewarp.com/api/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-25T16:22:16.016076+00:00",
"registry_status": null,
"subject": {
"id": "io.github.warpfreight/warp-agent-mcp",
"kind": "mcp"
},
"tools": {
"names": [
"analytics",
"automate_lane",
"automation_receipts",
"batch_book",
"batch_quote",
"book",
"box_truck_quote",
"compare_freight_costs",
"compare_modes",
"consolidate",
"delete_load_template",
"events",
"freight_workflow",
"ftl_quote",
"get_documents",
"get_invoice",
"lane_history",
"list_bookings",
"load_templates",
"locations",
"login",
"ltl_market_options",
"ltl_quote",
"manage_automation",
"multistop_book",
"multistop_quote",
"parcel_book",
"parcel_quote",
"payment_status",
"price_check",
"quote_history",
"report_issue",
"save_load_template",
"shipper_profile",
"status",
"track",
"van_quote"
],
"names_truncated": false,
"sha256": "f31aca066038f22d8eb900b5459e8832cf8ec34fe3329706e0f628f9114d07c9"
},
"tools_complete": true,
"tools_observed_at": "2026-10-25T16:22:16.016076+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