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-30T15:34:41.123605+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://api.misar.io/mail/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-30T15:34:41.123605+00:00",
"registry_status": null,
"subject": {
"id": "io.github.misar-ai/misarmail-mcp",
"kind": "mcp"
},
"tools": {
"names": [
"add_domain",
"archive_email",
"categorize_inbox_emails",
"check_dmarc",
"clear_sandbox",
"configure_inbound_domain",
"create_ab_test",
"create_automation",
"create_campaign",
"create_contact",
"create_landing_page",
"create_template",
"generate_report",
"generate_subject_lines",
"get_analytics",
"get_analytics_timeline",
"get_automation",
"get_campaign",
"get_contact_score",
"get_deliverability_score",
"get_email",
"get_form",
"get_form_submissions",
"get_inbox_conversation_messages",
"get_integration",
"get_marketplace_item",
"get_monetization_stats",
"get_revenue_attribution",
"get_warmup_status",
"import_contacts",
"list_ab_tests",
"list_api_keys",
"list_automations",
"list_campaigns",
"list_contacts",
"list_domains",
"list_emails",
"list_forms",
"list_inbox_conversations",
"list_integrations",
"list_marketplace_items",
"list_sandbox_sends",
"list_templates",
"render_template",
"reply_to_email",
"run_deliverability_audit",
"select_ab_test_winner",
"send_campaign",
"send_email",
"toggle_automation",
"toggle_integration",
"update_contact",
"upgrade",
"validate_email",
"verify_domain"
],
"names_truncated": false,
"sha256": "b5cd51ff9dd00bf714452b9ba95f1aa47a9534511eb2d1293464126cc34291b0"
},
"tools_complete": true,
"tools_observed_at": "2026-10-30T15:34:41.123605+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