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-30T10:07:13.446094+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://mentionry.com/api/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-30T10:07:13.446094+00:00",
"registry_status": null,
"subject": {
"id": "com.mentionry/mentionry",
"kind": "mcp"
},
"tools": {
"names": [
"backlink_gap",
"cancel_preparation_job",
"describe_agent",
"discover_competitors",
"dismiss_preparation_action",
"draft_pitch",
"find_prospects",
"list_agents",
"list_brand_workspaces",
"list_connections",
"list_documents",
"list_media",
"prepare_page_changes",
"qualify_domain",
"read_actionable_insights",
"read_agent_capabilities",
"read_brand_overview",
"read_brand_results",
"read_document",
"read_latest_answer_reviews",
"read_live_search_campaign",
"read_page_connections",
"read_page_deployments",
"read_page_insights",
"read_page_keywords",
"read_preparation_action",
"read_preparation_actions",
"read_preparation_job",
"read_prepared_page_changes",
"read_search_console_performance",
"read_search_rank_history",
"read_site",
"read_visibility",
"read_website_pages",
"record_page_deployment",
"restore_answer_evidence",
"restore_preparation_action",
"review_answer_evidence",
"review_preparation_action",
"run_agent",
"verify_links",
"write_email_template",
"write_landing_page"
],
"names_truncated": false,
"sha256": "0190e76308d7e5ac2e77603d32196b53633d2f798fdabff14dde8a7ac21c8100"
},
"tools_complete": true,
"tools_observed_at": "2026-10-30T10:07:13.446094+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