anonym-community-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANONYM_MCP_TTL_MS | No | Time-to-live in milliseconds for cached data fetching. Default is 1800000 (30 minutes) | 1800000 |
| ANONYM_MCP_BASE_URL | No | Base URL of the anonym.community site. Default is https://anonym.community | https://anonym.community |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_pain_pointsA | Search 1,478 documented PII/privacy pain points. Each is a concrete, evidenced problem (e.g. re-identification via quasi-identifiers, opt-out futility with data brokers), tagged with research track, category and severity. Use for "what goes wrong with X" questions. |
| list_structural_driversA | List or search the 98 structural drivers — the irreducible root causes that generate the pain points. Breaking one driver weakens many pain points at once, so these are the right unit for "why does this keep happening" and "what should we actually fix" questions. |
| lookup_jurisdictionA | Look up privacy-law status for a country or region across 240 jurisdictions: whether it has a data protection authority, what legislation applies, and links. Use for "is there a privacy law in X" and cross-border transfer questions. |
| search_faqA | Search 134 evidence-backed privacy questions and answers, each with root cause, real-world example and supporting data points. Use for direct practitioner questions. |
| search_research_papersA | Search 1,600+ real academic papers underpinning the research (title, authors, abstract, DOI). Use when a claim needs a citable primary source. |
| get_corpus_statsA | Return counts, available filter values (tracks, regions), and data freshness for this corpus. Call this first to discover valid track and region values for the other tools. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct content type: FAQ entries, pain points, structural drivers, jurisdiction statuses, research papers, and corpus metadata. The search tools are differentiated by their object type, and the descriptions explicitly state when to use each, so there is no overlap.
All tool names follow a consistent verb_noun pattern (e.g., search_faq, search_pain_points, list_structural_drivers, lookup_jurisdiction, search_research_papers, get_corpus_stats). Verbs are action-appropriate and nouns clearly indicate the resource.
With 6 tools, the server is well-scoped for its purpose of accessing a privacy research corpus. Each tool covers a distinct content type or metadata function, and none are redundant.
The server covers discovery and search across all major corpus components (FAQ, pain points, structural drivers, jurisdictions, research papers) plus a stats/metadata tool for valid filters. There are no obvious dead ends, as every tool returns the information needed for its use case.