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-20T23:03:22.080249+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://agent-guild-5d5r.onrender.com/mcp/",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-20T23:03:22.080249+00:00",
"registry_status": null,
"subject": {
"id": "io.github.agenttanuki/agent-guild",
"kind": "mcp"
},
"tools": {
"names": [
"ag_calc_stats",
"ag_calc_unit_convert",
"ag_capabilities",
"ag_code_semver_compare",
"ag_data_dedupe",
"ag_data_record_link",
"ag_json_canonicalize",
"ag_json_diff",
"ag_json_path_extract",
"ag_json_repair",
"ag_json_schema_infer",
"ag_json_validate",
"ag_table_csv_to_json",
"ag_table_json_to_csv",
"ag_table_markdown_extract",
"ag_text_date_normalize",
"ag_text_regex_extract",
"guild_attest",
"guild_best_agent",
"guild_check",
"guild_coordination_policy",
"guild_envelope_issue",
"guild_envelope_verify",
"guild_escrow_open",
"guild_escrow_release",
"guild_evidence_bundle",
"guild_evidence_verify",
"guild_index",
"guild_paid_operations",
"guild_passport",
"guild_preflight",
"guild_preflight_deep",
"guild_preflight_outcome",
"guild_prove",
"guild_prove_verify",
"guild_record",
"guild_register",
"guild_report",
"guild_risk_score",
"guild_search",
"guild_verify",
"guild_watch",
"guild_watch_feed",
"guild_x402_payment_safety"
],
"names_truncated": false,
"sha256": "40831e3a8881cc5494754e148e32b3b888f68362cb4d4ace50e698c088a5d6ce"
},
"tools_complete": true,
"tools_observed_at": "2026-10-20T23:03:22.080249+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