mcpField
V
VAAS-X Cognitive Memory

VAAS-X Cognitive Memory

Remote
github.com/VAAS-XMemory & Knowledge0Updated 9w ago
Repository

About VAAS-X Cognitive Memory

VAAS-X Cognitive Memory provides persistent, queryable episodic memory for AI agents and connected devices, linking states, actions, and outcomes. It can profile structured data streams automatically and retrieve similar episodes on CPU without requiring a self-hosted vector database.

Key features

  1. 01Automatically profile structured data streams
  2. 02Record episodes as state, action, and outcome
  3. 03Retrieve matching past episodes
  4. 04Run on CPU without a GPU
  5. 05Support edge devices and standard servers

Use cases

  1. 01Store agent actions and their outcomes
  2. 02Retrieve relevant episodes from sensor streams
  3. 03Use past outcomes to inform later decisions
  4. 04Keep queryable memory on an edge device

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://mcp.vaasx.com/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

vaas-x

PyPI Python License

Persistent, outcome-grounded memory for AI agents and connected devices.

pip install vaas-x gives any device or agent a persistent, queryable record of what it's seen — what happened, what it did, what the outcome was — and retrieves the closest matching past episode in milliseconds, on CPU, with no GPU and no vector database to stand up yourself.

Install

pip install vaas-x

Get a free-tier API key at vaasx.com — no card required.

Quickstart

from vaasx import Bootstrap

brain = Bootstrap(api_key="...", device_id="my_device")

# Point it at a structured data stream (sensor readings, agent actions,
# API events -- anything JSON-shaped) and it profiles the stream
# automatically, no schema design required.
brain.connect("https://your-data-stream.com/events")

# Query for the most similar past episodes, ranked by what actually
# worked, not just what's nearest in vector space.
hits = brain.query("engine running hot", k=5, prefer_success=True)

An agent that already knows its own outcome the moment it acts can log a full state/action/outcome episode in one call instead of a separate ingest-then-tag-later round trip:

resp = brain.ingest([{
    "state": {"observation": observation},
        "action": {"taken": action},
            "outcome": {"success": result.success},
            }])
            episode_id = resp["episode_ids"][0]

            # Report back on a retrieved episode once you know how it went
            brain.outcome(hits[0]["id"], success=True, delta=0.12)
            ```

            Three calls — `ingest`, `query`, `outcome` — cover the whole loop. No
            schema to design, no vector DB to host, no embedding model to serve
            yourself.

            ## What it does

            - Profiles a raw data stream automatically — statistical profiling,
              schema classification, and anomaly detection all run locally before
                anything touches the network.
                - Stores episodes as (state, action, outcome) triples, so retrieval can be
                  weighted toward what worked last time in a similar situation, not just
                    nearest by embedding distance.
                    - Runs on both a small edge device and a standard server — same codebase,
                      no domain-specific build. Verified live on a £30 ESP32 microcontroller
                        and on a standard EC2 instance.

                        ## Numbers, not adjectives

                        - 14ms mean retrieval across 1.18M stored episodes on a standard AWS
                          m7i-flex.large CPU instance — no GPU, no AVX-512.
                          - Blind-tested on NASA's CMAPSS FD001 predictive-maintenance benchmark:
                            given 24 sensor channels with every identifier stripped, correctly
                              classified all 24 with zero prior domain knowledge.
                              - Consistent zero-config classification result across 8 independent
                                subjects on a real wearable IMU dataset (UCI Daily and Sports
                                  Activities).

                                  Every number above is independently reproducible — see below.

                                  ## Reproduce the benchmarks yourself

                                  Every result this SDK's marketing points to has a step-by-step guide
                                  against a real public dataset or environment, with your own API key, plus
                                  an independent local cross-check that doesn't depend on the SDK at all:

                                  - [CMAPSS predictive maintenance](https://vaasx.com/guides/cmapss.html)
                                  - [Room-occupancy detection](https://vaasx.com/guides/occupancy.html)
                                  - [Memory-augmented CartPole](https://vaasx.com/guides/cartpole.html) (zero download)
                                  - [Wearable activity classification](https://vaasx.com/guides/sports_wearable.html)
                                  - [Physics simulations](https://vaasx.com/guides/scientific_computing.html) (QEC, lattice field theory, Ising model)
                                  - [Live drone control loop](https://vaasx.com/guides/drone_control.html)

                                  Full guide index: [vaasx.com/guides](https://vaasx.com/guides)

                                  ## Tiers

                                  Free gets you an API key instantly. Developer (£19/mo) and Professional
                                  (£99/mo) are self-serve paid tiers with higher episode limits and
                                  additional capabilities. Enterprise is contract-based, for teams wanting
                                  on-prem or air-gapped deployment. See
                                  [vaasx.com/pricing](https://vaasx.com/pricing) for current details.

                                  ## The honest caveat

                                  This package ships as a compiled wheel, not source-available — the
                                  retrieval and indexing internals are proprietary and protected as a trade
                                  secret. What *is* open: full API documentation, working examples, and the
                                  wire format, so you can see exactly what goes in and comes back even
                                  without reading the internals.

                                  Multimodal support (vision/audio/depth/thermal, via the optional `ac`
                                  extra) is real but still early — encoder models are in active training
                                  and not yet production-tuned; treat it as a preview, not a finished
                                  feature.

                                  ## Issues & questions

                                  This repo doesn't carry the source (see above), but it's the right place
                                  to file bugs against the published package, ask integration questions, or
                                  request a reproduction guide for a dataset/environment not covered above.

                                  ## Links

                                  - [Documentation](https://vaasx.com/docs)
                                  - [Whitepapers](https://vaasx.com/whitepapers) — technical deep dives, one per use case
                                  - [Homepage](https://vaasx.com)

                                  ## License

                                  Proprietary — see [LICENSE](LICENSE).

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.