{"id":"allenmaxi-contextgraph","name":"ContextGraph","homepage":null,"repo_url":"https://github.com/AllenMaxi/ContextGraph","category":"ai-ml","subcategories":[],"tags":["ai-agents","agent-memory","mcp","knowledge-graph","neo4j","python","governance","retrieval","rag","context-compilation"],"what_it_does":"ContextGraph is a governed shared-memory layer for multi-agent systems. It stores agent claims with provenance/freshness/trust metadata, enforces access control at retrieval time, and compiles token-budgeted “context packs” (optionally explainable) for each agent’s permissions. It provides a Python SDK, CLI/dashboard, an HTTP REST API, and an MCP server/tool integration, with optional Anthropic Claude Memory Tool adapter support and a Neo4j-backed self-hosted beta path.","use_cases":["Multi-agent teams needing reusable operational/research context without prompt glue","Governed retrieval with provenance, freshness/trust signals, and explainable inclusion/exclusion","Cross-agent/agent-to-agent workflows (support, incident ops, research handoffs) that require policy enforcement","Building governed RAG where memory is filtered by ACL/payment/quality gates","Operator workflows for sentinel-based claim validation and auditable verdicts","Claude/Anthropic-compatible memory operations backed by ContextGraph revisions and archival semantics"],"not_for":["Personal single-chatbot memory with no governance/policy needs","Teams requiring a hosted enterprise IAM-first deployment (README emphasizes self-hosted/beta components)","Simple vector-database-only RAG pipelines without provenance or policy-controlled retrieval"],"best_when":"You run multiple agents (and/or organizations) that must share knowledge safely, with auditable provenance, freshness/trust controls, and token-budgeted context assembly per caller permissions.","avoid_when":"You only need lightweight retrieval and cannot justify governance overhead (provenance, reviews, sentinel verdicts, explainability, persistence of context packs).","alternatives":["Vector databases with application-layer access control and provenance (custom RAG pipelines)","Other agent memory/knowledge graph solutions (e.g., generic graph stores + custom governance)","Hosted agent memory services with built-in IAM (where available)"],"af_score":51.0,"security_score":54.8,"reliability_score":27.5,"package_type":"mcp_server","discovery_source":["github"],"priority":"high","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-03-30T15:38:33.611372+00:00","interface":{"has_rest_api":true,"has_graphql":false,"has_grpc":false,"has_mcp_server":true,"mcp_server_url":null,"has_sdk":true,"sdk_languages":["python"],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":["Authentication/authorization details not explicitly provided in README content provided"],"oauth":false,"scopes":false,"notes":"README describes ACL enforcement and agent permissions (e.g., org/partner/published visibility, freshness/trust gates) and governance endpoints, but does not document the concrete auth mechanism (API keys/JWT/OAuth) or whether scopes/roles map to API authentication."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"No pricing/subscription/tier information was present in the provided README/manifest content. Mentions 'optional payments' and 'paid claims' gating, but not pricing for the service itself."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":51.0,"security_score":54.8,"reliability_score":27.5,"mcp_server_quality":45.0,"documentation_accuracy":70.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":55.0,"rate_limit_clarity":10.0,"tls_enforcement":70.0,"auth_strength":45.0,"scope_granularity":60.0,"dependency_hygiene":50.0,"secret_handling":50.0,"security_notes":"Strengths indicated: policy-controlled retrieval (ACL/visibility), explainable filtering traces, provenance/freshness/trust/quality gates, and paid-claim locking to avoid content leakage across org boundaries. Unclear/undocumented: concrete authentication mechanism, TLS requirements for REST/MCP, key management/secret handling practices, scope model granularity at the API level, rate limiting, and detailed security posture (auditing details are referenced but not shown).","uptime_documented":0.0,"version_stability":45.0,"breaking_changes_history":35.0,"error_recovery":30.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["Governed retrieval behavior depends on permissions (agent/org visibility) and claim gates (freshness/trust/sentinels/payment locks); agents may see empty/locked claims if authorization or gates don’t allow access.","Compiled context packs are persisted and retrievable; agents should use pack_id correctly rather than assuming recall/compile are stateless.","No explicit retry/idempotency semantics were documented in provided README content; agents may need to implement conservative retries for POST operations."]}}