{"id":"shared-context-cache-mcp-server","name":"shared-context-cache-mcp-server","homepage":"https://pypi.org/project/shared-context-cache-mcp-server/","repo_url":"https://github.com/AiAgentKarl/shared-context-cache-mcp-server","category":"devtools","subcategories":[],"tags":["mcp","model-context-protocol","ai-agents","cache","agent-economy","shared-context","trust","python"],"what_it_does":"A Python MCP server that provides a shared cache for AI-agent computed results, including a trust/verification mechanism where agents can store results, confirm accuracy, and retrieve only entries that meet a configurable minimum trust threshold. Cache entries expire via TTL and basic/advanced analytics tools are exposed via MCP tools.","use_cases":["Sharing repeated computations across multiple AI agents to reduce token cost and latency","Caching lookup-like tasks (e.g., weather, price checks) where results can be verified by peers","Maintaining higher-confidence answers via min-trust retrieval (e.g., 3+ confirmations)","Tracking cache effectiveness (hits/misses/cost savings) and trust distribution"],"not_for":["Security-critical or adversarial environments where untrusted agents could intentionally poison the trust layer","Highly regulated workloads requiring strong audit trails, formal compliance guarantees, or strong tenant isolation","Use cases that require strong authenticity/identity verification of confirming agents"],"best_when":"Multiple cooperating agents (or teams) repeatedly compute the same deterministic-ish results and you want lightweight cross-agent sharing with a consensus-style confidence score.","avoid_when":"Confirmations and cache contents are influenced by untrusted or potentially malicious actors, or when you require cryptographic guarantees for provenance/authenticity.","alternatives":["Redis/Memcached-based shared caching with application-level validation and TTL","Vector/semantic caches (e.g., embedding-based) with provenance metadata","LLM orchestration frameworks that implement centralized result memoization with deterministic checks","Other MCP servers or cache services that include signed provenance or stronger identity controls"],"af_score":52.0,"security_score":36.0,"reliability_score":18.8,"package_type":"mcp_server","discovery_source":["pypi"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T21:44:51.222586+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":true,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":[],"oauth":false,"scopes":false,"notes":"No authentication mechanisms are described in the README. The trust layer appears to be based on confirmations and local persistence rather than authenticated agent identities."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"No pricing information provided; appears to be a self-hosted/open-source MCP server via PyPI."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":52.0,"security_score":36.0,"reliability_score":18.8,"mcp_server_quality":70.0,"documentation_accuracy":60.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":95.0,"rate_limit_clarity":10.0,"tls_enforcement":40.0,"auth_strength":15.0,"scope_granularity":10.0,"dependency_hygiene":55.0,"secret_handling":70.0,"security_notes":"No authentication/authorization is documented for cache read/write or confirmations, and the trust mechanism is described without identity verification. This is a potential integrity risk in adversarial settings (cache poisoning / false confirmations). TLS usage for any remote backend is not specified; the README only references a remote cache URL for backend, not how connections are secured. Dependency list is small (mcp, httpx), but no vulnerability/CVE or security posture details are provided.","uptime_documented":0.0,"version_stability":35.0,"breaking_changes_history":20.0,"error_recovery":20.0,"idempotency_support":"false","idempotency_notes":"Store/confirm operations are likely not idempotent by design as described (confirming likely increments trust); no explicit idempotency guidance is provided.","pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["Trust score increases via confirmations; repeated confirmations by the same agent (or duplicate events) could inflate trust unless the server deduplicates (not documented).","get_trusted uses a configurable threshold; ensure consistent min_trust settings across agents for expected behavior.","Cache key conventions are important; inconsistent keying will reduce cache hit rate.","Trust persistence is local to the user (~/.shared_context_cache_trust.json); running multiple deployments/users may not share trust state as expected."]}}