"namespace:91.174.133.8" matching MCP servers:

Enables MCP clients to store, recall, correct, and forget knowledge with per-sentence source bindings and a replayable retrieval traceId, so every answer can be traced to a specific document passage. Adds document-level version chains that retire superseded content from default retrieval, tombstone-based forgetting, three-layer user/namespace/scope isolation with full operation auditing, and deterministic calculator/date tools.

Enables LLM and AI-agent clients to operate a Nacos 3.0 control plane through MCP tools, resources, and prompts—covering configuration publishing, rollback, history and drift checks, namespace management, service discovery, instance registration/weighting, and cluster health probing. It supports stdio and SSE transports with Docker deployment, self-healing authentication, and syntax guardrails suited to asymmetric NAT environments.

Enables access to Yuque (语雀) documentation through cookie-based authentication, supporting document retrieval, search, TOC navigation, and content management from knowledge bases via URL or namespace.

A temporary placeholder MCP server that reserves the @bikefuchs namespace and exposes an informational tool about the upcoming Bikefuchs production server for bike price comparison.

MCP server providing Celestia network intelligence, including daily briefs, anomaly signals, staking and DA metrics, and live namespace and validator drill-downs, with each figure linked to its source.

Ships only the MCP server, not the recorder. Recording works by wrapping a process on the host — a local proxy, a PATH shim, a shadow git index. None of that survives a container boundary, so orca record inside here would watch an empty namespace. What does travel is the read side: the six MCP tools serve runs that already exist on disk, so a client mounts its .orca directory and r

Provides evidence-first product naming tools for agents and founders, including domain registry checks, namespace searches, and finalist research with sources and timestamps.

Fronts many downstream MCP servers through one session, presenting a unified tool namespace with collision resolution, fleet-wide allow/deny/hide policy, per-tool rate limits, centralized audit logging, Prometheus metrics, and bearer-key auth at the edge. Supports both stdio drop-in and Streamable HTTP deployment so agents point at a single endpoint instead of N servers.

A Cloudflare-native MCP server for a consolidated knowledge base, enabling CRUD operations, search, and namespace management with versioning and audit logs.

Enables connecting multiple remote HTTP MCP servers through a single local stdio endpoint, handling OAuth authentication, token refresh, and namespace-scoped tools.

Enables multiple AI agents to share a self-hosted, namespace-scoped cloud memory via a local stdio MCP server that caches valid results locally in SQLite and syncs to a remote MySQL backend. Exposes tools for searching, retrieving, timeline browsing, remembering, forgetting, and syncing memories with versioning, conflict handling, and redaction.