"A tool or software for modeling memory systems or memory management" matching MCP servers:

Enables users to list and inspect household memory-conflict tasks, score answers, run evaluations, and retrieve provenance data through MCP tools.

Enables Playwright QA automation with a custom Memory MCP that provides tiered retention and mortgage compliance audit, allowing AI agents to remember flakiness history and journey maps while adhering to data privacy and audit requirements.

Persistent visual cache for LLM-driven software development. Caches screenshots using perceptual hashing, vector search, and AX trees to prevent token overhead and visual hallucination loops.

Enables deterministic behavioral regression review of pull-request diffs by checking changed code against approved incident-derived contracts. It exposes read-only tools to assess diffs and pull requests, list and fetch contracts, and report outcomes over stdio without mutating repositories.

MCP server enabling Claude Code to capture screenshots of Windows applications through WSL2, allowing AI to diagnose UI errors and verify layouts.

Audits MCP tool descriptions for quality and reliability, scoring them 0-100, detecting smells, and providing rewritten versions for better agent accuracy.

A validation layer for AI coding assistants that enforces explicit LLM evaluations on plans, code diffs, and tests to ensure safer and higher-quality code.

Protects AI agents from bad tool outputs, schema mismatches, and tool poisoning by validating, sanitizing, and scoring reliability of tool responses.

A lightweight multi-provider MCP testing fixture with two providers (eva_air and uk_railway), each exposing 5 tools using in-memory fake data, designed for verifying MCP client tool discovery, tool calls, and multi-provider routing.

This MCP server verifies that an agent’s claimed tool output matches the actual response returned by a tool to prevent invented or distorted results. It flags mismatches, omissions, and invented fields to ensure downstream logic only processes verified tool data.

Enables verification of deployment-scoped model-visible DSH tool surface conformance by checking recorded tool identities and schemas against approved locks, reporting only drift categories and hashes.

Analyzes multi-step AI agent tool chains to compute success probability, identify bottlenecks, and suggest better execution orders, enabling more reliable agents via local pure-math computation.

A throwaway HTTP MCP server that empirically tests whether Cursor invokes tools by exact name or munges them, to inform case normalization decisions.

Enables AI assistants to evaluate task complexity, verify package installation safety, and log complex reasoning processes. Provides structured assessment of multi-step tasks and environment validation for safer code execution workflows.

MCP-first A/B testing server that enables agents to manage experiments (create, update traffic splits, read results, apply winning variants) from tools like Claude Code, with self-hosted Cloudflare backend.

MITM proxy MCP server that intercepts and verifies AI agent tool calls, detecting fabrication, tracking costs, verifying outcomes, and inferring user satisfaction.

An MCP Server that provides access to Google's Cloud Tool Results API, enabling applications to programmatically interact with test results from Firebase Test Lab and mobile app testing through natural language.

Enables reproducible evaluation of AI coding agents by exposing repository inspection, code editing, test running, and deterministic verification through MCP tools.

Enables researchers to present 12 mock file, memory, schedule, and database tools over stdio and collect LLM pre-execution judgments (EXECUTE/CONFIRM/REFUSE) without executing real operations.

Translates a lockfile diff into a human-readable upgrade plan. For every dependency bump (npm or PyPI) returns semver class, breaking changes from GitHub release notes, CVEs fixed in the range, migration guide links, and a clear per-package recommendation. Bulk tool ranks up to 50 package changes in parallel by risk (security > caution > review > likely-safe > safe).