claude mcp add filter-mcp-server -- npx -y filter-mcp-server
A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
Star count
1 ★ · chohyerinn/filter-mcp-server · read from the repository page · (checked 2026-10-16 20:00:20)
Source
collected from the punkpeye/awesome-mcp-servers list · type: MCP server
Harvest history
first seen 2026-10-09 · last seen 2026-10-16 · seen 32× · listed by 7 sources
Score
score 703 · 1 ★ · 7 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository chohyerinn/filter-mcp-server;first catalogued 2026-10-09;last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.
Overview This project compares several approximate filter data structures using MCP servers and LLM tool calls. Approximate filters reduce memory usage by storing compressed summaries instead of full keys. Because of this trade-off, some filters may return false positives or support limited operations. The project compares: - Bloom Filter - Counting Bloom Filter - Cuckoo Filter - SuRF (Simplified Version) An exact hash-set server is also included as a baseline for comparison. Implemented MCP Servers | MCP Server | Data Structure | Description | |---|---|---| | filter-naive | Exact Set / Hash Table | Exact membership baseline | | filter-bloom | Bloom Filter | Memory-efficient approximate membership filter | | filter-counting-bloom | Counting Bloom Filter | Bloom Filter with deletion support | | filter-cuckoo | Cuckoo Filter | Fingerprint-based approximate filter | | filter-surf | Simplified SuRF | Approximate prefix/range filter | Project Goal The goal of this project is to compare how different filter structures behave under the same workload. The comparison focuses on: - membership query accuracy - false positive rate - memory usage - query latency - insertion and deletion support - prefix and range query capability All servers expose the same ADT-style interface through MCP tools so that they can be tested consistently. Scenario Search Keyword Dictionary Management The servers simulate a keyword search system. Examples: - search autocomplete - keyword lookup - blocked-word checking - dictionary membership testing The same keyword dataset and queries are used across all filters to compare performance and behavior. ADT All MCP servers provide the following tools: | Tool | Description | |---|---| | build(items) | Build filter from dataset | | insert(x) | Insert a key | | contains(x) | Membership query | | delete(x) | Delete a key if supported | | range_query(lo, hi) | Range query | | prefix_query(prefix) | Prefix query | | memory_usage() | Return estimated memory usage | | false_positive_rate() | Measure false positive rate | Theoretical / Qualitative Structure Comparison | Structure | False Positives | Delete Support | Prefix/Range Query | Memory Efficiency | |---|---|---|---|---| | Exact Set | No | Yes | Yes | Low | | Bloom Filter | Yes | No | No | Very High | | Counting Bloom Filter | Yes | Yes | No | High | | Cuckoo Filter | Yes | Yes | No | High | | Simplified SuRF | Yes | No | Yes | Medium | This table describes the expected qualitative behavior of each structure. It is not a measured benchmark result. Benchmark Results Measured results are available in docs/benchmark_results.md. The benchmark uses fixed synthetic workloads from src/membership_filters/benchmark.py and compares all filters with the same build items and absent-query probes. It reports estimated memory from memory_usage(), measured false positive rate from false_positive_rate(), and average local contains() latency.