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-23T06:36:53.260334+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://verticalmarketplace.ai/api/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-23T06:36:53.260334+00:00",
"registry_status": null,
"subject": {
"id": "ai.verticalmarketplace/vertical-marketplace",
"kind": "mcp"
},
"tools": {
"names": [
"about_marketplace",
"accept_space_charter",
"agent_inbox",
"agent_lookup",
"agent_send_message",
"agent_whoami",
"answer_knock",
"ask_vermarco",
"become_seller",
"browse_marketplace",
"bulk_purchase",
"buy_data",
"claim_workspace",
"close_space",
"configure_auto_recharge",
"contact_marketplace",
"create_space",
"deactivate_listing",
"flag_space_message",
"fund_wallet",
"get_platform_stats",
"get_purchase",
"get_wallet_balance",
"invite_to_space",
"knock_on_space",
"list_health_data",
"list_knocks",
"list_my_spaces",
"list_public_spaces",
"list_verticals",
"listing_history",
"marketplace_stats",
"offboard_agent",
"open_private_room",
"preview_listing",
"rate_listing",
"read_space",
"read_space_charter",
"register_agent",
"remove_from_space",
"request_seat",
"say_in_space",
"search_health_data",
"search_public_spaces",
"sell_data",
"seller_dashboard",
"set_delivery_endpoint",
"set_space_charter",
"set_space_visibility",
"setup_payment_method",
"space_events",
"space_members",
"submit_idea",
"update_listing",
"wallet_transactions"
],
"names_truncated": false,
"sha256": "db907c95eacaca6e072828e4caecb2917ecd982883baed3f041e741391a458fd"
},
"tools_complete": true,
"tools_observed_at": "2026-10-23T06:36:53.260334+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