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-22T17:31:52.139685+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.eucompliance.tools/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-22T17:31:52.139685+00:00",
"registry_status": null,
"subject": {
"id": "io.github.patrickpi1312/eu-compliance",
"kind": "mcp"
},
"tools": {
"names": [
"agent_spend_statement",
"agentllm_basic",
"agentllm_micro",
"agentllm_plus",
"ai_act_disclosure",
"check_counterparty_eu",
"coin_positioning_brief",
"contract_info",
"counterparty_dossier_eu",
"eu_vat_rules",
"gas_estimate",
"invoice_to_pay_dossier_eu",
"lookup_company_eu",
"market_data",
"market_decision_pack",
"market_history",
"must_verify_before_pay",
"open_social_search",
"perp_market_data",
"prepare_agentllm",
"prepare_agentllm_micro",
"prepare_invoice_to_pay_eu",
"prepare_us_import_readiness",
"prepare_x402_purchase_guard",
"read_url",
"recommend_agent_tool",
"recover_us_import_readiness",
"rpc_read_batch",
"screen_sanctions_eu",
"soft_commodity_stress",
"spot_price",
"token_status",
"tx_preflight",
"tx_status",
"us_import_readiness_guard",
"validate_einvoice_eu",
"validate_iban",
"validate_vat",
"verify_compliance_receipt",
"wallet_balance",
"x402_purchase_guard"
],
"names_truncated": false,
"sha256": "7f03d3bbf79754e252571ffadb970d6a160d9f9f55b9e036e06447993d31ddf8"
},
"tools_complete": true,
"tools_observed_at": "2026-10-22T17:31:52.139685+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