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-22T13:15:10.796482+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://www.blixtworks.com/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-22T13:15:10.796482+00:00",
"registry_status": null,
"subject": {
"id": "com.blixtworks.www/tools",
"kind": "mcp"
},
"tools": {
"names": [
"address_validate",
"base64",
"caption",
"case_convert",
"categorize",
"check_credit",
"color_convert",
"cron_parse",
"csv_to_json",
"currency_convert",
"date_diff",
"diff",
"distance",
"dns",
"email_validate",
"embed",
"ens_resolve",
"exif",
"gas_price",
"hash",
"hmac",
"how_to_pay",
"http_headers",
"iban_validate",
"image_crop",
"image_info",
"image_palette",
"image_placeholder",
"image_resize",
"image_transform",
"ip_lookup",
"json_format",
"json_query",
"json_to_csv",
"jwt_decode",
"language_detect",
"list_tools",
"lorem",
"luhn_validate",
"markdown_to_html",
"md",
"metadata",
"number_base",
"ocr",
"pdf",
"percentage",
"phone_parse",
"qr",
"redeem_payment",
"regex",
"robots_check",
"rss_parse",
"sitemap_parse",
"slugify",
"ssl_check",
"text_stats",
"timestamp",
"token_info",
"try_sample",
"tx_lookup",
"unit_convert",
"url_expand",
"uuid",
"wallet_balance",
"whois",
"word_frequency",
"xml_to_json",
"yaml_convert"
],
"names_truncated": false,
"sha256": "aa8ee84ec0297e6a6c8224ec202db9e12cdd336010e3b80eb5581e9960bb28aa"
},
"tools_complete": true,
"tools_observed_at": "2026-10-22T13:15:10.796482+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