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-21T08:05:55.914527+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.mainnet.rubin.trade/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-21T08:05:55.914527+00:00",
"registry_status": null,
"subject": {
"id": "trade.rubin/exchange",
"kind": "mcp"
},
"tools": {
"names": [
"batch_cancel",
"cancel_all_orders",
"cancel_order",
"close_all_positions",
"close_position",
"deposit_to_subaccount",
"get_balance",
"get_block_height",
"get_candles",
"get_candles_multi",
"get_equity",
"get_fee_tier",
"get_fills",
"get_funding_status",
"get_leaderboard",
"get_market",
"get_my_rank",
"get_news",
"get_open_orders",
"get_orderbook",
"get_pnl",
"get_portfolio",
"get_position_risk",
"get_positions",
"get_referral_program",
"list_markets",
"open_position",
"place_limit_order",
"place_market_order",
"place_stop_loss",
"place_take_profit",
"top_up_gas",
"whoami"
],
"names_truncated": false,
"sha256": "d279b5cc46c0afd44dafa527c7220caf9ff56bf6591c5d9c8928410293e7a9e8"
},
"tools_complete": true,
"tools_observed_at": "2026-10-21T08:05:55.914527+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