Fisheye Crucible

{
  "service_type": "platform",
  "base_url": "https://fecru.local",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "subscription",
    "details": {
      "note": "Atlassian Fisheye/Crucible is a commercial, self-hosted product historically licensed as a perpetual or subscription server license. Pricing is not retrievable from fecru.local; refer to Atlassian's official pricing for current details."
    }
  },
  "rate_limits": {},
  "capabilities": [
    "Source code repository browsing and search",
    "Subversion, Git, Mercurial, Perforce, CVS, ClearCase repository hosting/integration",
    "Code review workflows (Crucible)",
    "Inline commenting and review discussion",
    "Workflow-driven review states and approvals",
    "LDAP/Active Directory and internal authentication",
    "JIRA and Confluence integrations",
    "Pre-commit and post-commit review support",
    "Web-based administration interface",
    "REST API and plugin/extension support",
    "Self-hosted/on-premise deployment"
  ],
  "raw_analysis": "Fisheye and Crucible are two related Atlassian server products: Fisheye is a repository browser and search tool for source control systems, while Crucible is a peer code review tool. They are commonly deployed together as a single server instance, which matches the 'Fisheye Crucible' combined naming and the host fecru.local (a typical internal hostname). This indicates an on-premise/self-hosted enterprise deployment rather than a SaaS endpoint.\n\nTarget users: software development teams, particularly enterprises using centralized VCS like Subversion or Perforce plus Git, that need visibility across repositories, code search, and structured code review. Crucible is often paired with JIRA for issue tracking and with Bamboo/HIPChat in legacy Atlassian toolchains.\n\nMaturity: Fisheye/Crucible is a mature product with a long history (formerly Cenqua, acquired by Atlassian in 2008). However, Atlassian has been sunsetting its server products; new sales and support windows for server products have ended or are restricted, so long-term support is a consideration. The platform is stable but not the center of Atlassian's current strategy (Bitbucket, Jira, etc.).\n\nIntegrations: Atlassian ecosystem (JIRA, Confluence, Bamboo), LDAP/AD, common VCS systems, and a REST API plus plugin framework for custom extensions.\n\nAPI and auth: The provided description labels this as an 'API provider', but no concrete endpoints or base API paths are given beyond the placeholder host. Without access to the instance, I cannot confirm auth schemes. In practice, Fisheye/Crucible REST APIs typically require authentication (often basic auth, token, or session-based) and may support anonymous browsing if configured. I have conservatively set auth_method to 'none' because no credentials or auth details were supplied, but this should be treated as unknown/undetermined rather than a statement that the API is open.\n\nPricing model: Enterprise self-hosted subscription/perpetual server licensing, not freemium or free. Exact numbers are not available from this local endpoint and should be verified with Atlassian.\n\nLimitations: The URL https://fecru.local is a private/on-prem hostname, not a public API, so no external capability probing was possible. Endpoints and rate limits are left empty because none could be verified."
}

0/3 tests passed

{
  "overall": 38,
  "dimensions": {
    "token_efficiency": 4.0,
    "first_try_success": 2.0,
    "response_parseability": 5.0,
    "error_clarity": 3.0,
    "doc_quality": 6.0,
    "auth_simplicity": 2.0,
    "latency": 0.0,
    "consistency": 1.0
  },
  "pricing_normalized": {
    "type": "commercial self-hosted subscription/perpetual",
    "note": "Pricing not retrievable; requires Atlassian sales/support engagement",
    "agent_friendly": false
  },
  "issues": [
    "All three checks failed with DNS resolution errors ('Name or service not known') against fecru.local — the platform is unreachable, implying no public/agent-accessible endpoint",
    "No public API hostname resolvable; cannot be programmatically probed or evaluated",
    "Pricing is opaque and requires contacting Atlassian or checking official channels; not machine-readable",
    "Auth is enterprise server LDAP/AD or internal — no magic link, no simple signup, no self-service onboarding",
    "Legacy, self-hosted Atlassian product (Fisheye/Crucible) — deprecated product line, higher friction and maintenance burden",
    "No robots.txt, llms.txt, or security headers available (unreachable), no agent-discovery affordances",
    "Onboarding likely identical to historical enterprise install: license key, server setup, admin configuration — not minutes-to-productive"
  ],
  "recommendations": [
    "Expose a public, resolvable endpoint (e.g., a hosted demo or docs site) if agents are expected to evaluate or interact with the platform",
    "Publish machine-readable pricing and licensing details (JSON/YAML) to reduce discovery friction",
    "Provide a public REST API sandbox with key-based or OAuth2 auth to enable agent testing without a human in the loop",
    "Add llms.txt and a structured capabilities/OpenAPI spec to improve agent parseability",
    "Document setup time and prerequisites clearly so agents can set accurate user expectations",
    "If targeting modern agent workflows, consider a cloud/API-first counterpart to the self-hosted model"
  ]
}