Contextlattice

Created By
Shea Winkler3 months ago
ContextLattice provides HTTP-first, MCP-compatible memory write/search APIs with multi-sink fanout, retrieval orchestration, and high-throughput telemetry ingestion. Try it locally with Start local-first in minutes with `gmake quickstart`. Docs: https://contextlattice.io/installation.html
Overview

ContextLattice is an HTTP-first, MCP-compatible memory/context/task orchestrator built for long-horizon agent work.

Why this exists:

  • In long-horizon workflows, agents that forget prior decisions repeat avoidable mistakes; the result is brittle output and operator fatigue.
  • Finite context windows are unavoidable; without a durable memory/context system, retrieval quality decays toward zero as horizon length increases.
  • ContextLattice also serves as a telemetry database backend for app stacks that generate sustained high write volume.

What ships:

  • one ingress write path + durable outbox fanout
  • federated retrieval egress + context-quality feedback prompting + learning rerank loop
  • local-first security defaults
  • telemetry-grade throughput with queue controls and backpressure

Start in minutes: https://contextlattice.io/installation.html

Project Info
Created At
3 months ago
Updated At
3 months ago
Author Name
Shea Winkler
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Gpt Scrambler

2 days ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

2 hours ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago