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-22T15:53:26.768169+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://mart402.dev/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-22T15:53:26.768169+00:00",
"registry_status": null,
"subject": {
"id": "x402/sandbox",
"kind": "mcp"
},
"tools": {
"names": [
"document_pipeline",
"enrich_company",
"extract_url",
"get_catalog",
"get_receipt",
"get_sample",
"jp_bonus_net",
"jp_business_days",
"jp_company_profile",
"jp_consumption_tax",
"jp_crypto_tax",
"jp_dependent_threshold",
"jp_mortgage",
"jp_overtime_wage",
"jp_payroll_net",
"jp_payroll_suite",
"jp_payslip_audit",
"jp_retirement_tax",
"jp_social_insurance",
"meal_vision",
"ocr_image",
"operator_history",
"parse_document",
"pdf_info",
"pdf_merge",
"pdf_pages",
"portrait_analysis",
"portrait_precheck",
"quote_parse",
"report_pack",
"search_x402_services",
"structured_extract",
"style_profile",
"style_report",
"verify_invoice"
],
"names_truncated": false,
"sha256": "7dc2c5ab77768790eff59a70dc22da8891ae27dd5bcdcd95a089e3c30bd8fc27"
},
"tools_complete": true,
"tools_observed_at": "2026-10-22T15:53:26.768169+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