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-21T18:02:32.452976+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://mmvdabzadclebfxyzudg.supabase.co/functions/v1/forge-mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-21T18:02:32.452976+00:00",
"registry_status": null,
"subject": {
"id": "app.forgeengine/forge",
"kind": "mcp"
},
"tools": {
"names": [
"add_task",
"dedupe",
"delete_entity",
"design_ui_from_systems",
"get_balance",
"get_briefing",
"get_build_region",
"get_design_document",
"get_help",
"get_history",
"get_impact",
"get_inbox",
"get_milestone",
"get_project_context",
"get_project_meta",
"get_rejections",
"get_screen",
"get_screen_image",
"get_stale",
"get_system",
"get_workflow",
"import_from_code",
"list_activity",
"list_milestones",
"list_projects",
"list_screens",
"list_systems",
"next_task",
"post_log",
"propose_balance_board",
"propose_balance_table",
"propose_context",
"propose_dna",
"propose_element",
"propose_flow_edge",
"propose_milestone",
"propose_screen",
"propose_system",
"rename_screen",
"reorder",
"report_build_status",
"report_drift",
"report_milestone_progress",
"report_screen_status",
"resolve_rejection",
"resync_from_idea",
"search",
"set_design_overview",
"trace_ui_from_image",
"update_element",
"update_milestone",
"update_system",
"update_task",
"withdraw_proposal"
],
"names_truncated": false,
"sha256": "5b6a338b7583c56b08a3c36dad4c8d7dc4a42f37531cf751e463798dd537ce70"
},
"tools_complete": true,
"tools_observed_at": "2026-10-21T18:02:32.452976+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