All servers · Documents & retrieval · AI models & agents · Research & knowledge
ai·rete·rag
com.ai-rete-rag/ai-rete-rag-mcp · v0.11.0
New (7 days)Has write/delete tools
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-06-18 |
| Rank score | — |
| Declared risk | Has destructive tools (destructiveHint) |
| Capabilities declared | prompts, resources, tools |
| Tool definitions | 9 tools · with description 100% · input schema is an object 100% · read/destructive hints 100% |
Description written by the publisher, not verified
Author rules from policy docs, then decide: a Rete engine gives the verdict, an LLM explains why.
Connect
streamable-http · https://ai-rete-rag.com/mcp
claude mcp add --transport http ai-rete-rag-mcp https://ai-rete-rag.com/mcp{
"mcpServers": {
"ai-rete-rag-mcp": {
"url": "https://ai-rete-rag.com/mcp"
}
}
}streamable-http · https://ai-rete-rag.com/mcp/auth
claude mcp add --transport http ai-rete-rag-mcp https://ai-rete-rag.com/mcp/auth{
"mcpServers": {
"ai-rete-rag-mcp": {
"url": "https://ai-rete-rag.com/mcp/auth"
}
}
}Tools as reported by the server
decideMake a deterministic, auditable decision in a domain. The verdict comes from the domain's rule set (Rete engine, never the LLM), so it is reproducible and compliant. The explanation is generated from the domain's ingested policy documents. Without an API key only the shared demo domains are availabllist_rulesList the decision rules for one domain (or all domains). Returns each rule's conditions — either a flat AND list (field / operator / value) or a `when` condition tree (nested all/any/not) — plus its verdict, salience, and any asserted facts (`action.assert`, the facts a rule produces for other rulesget_parametersList the input parameters a domain's rules decide on — the facts to collect before calling `decide`. Derived from your account's own copy of the rules, so it covers your custom domains too. Each parameter has its `field` name (the key to use in `facts`), `kind` (number / boolean / string), the `testingest_textAdd policy/reference text to a domain's knowledge base. The text is chunked and embedded; explanations for future decisions in this domain will cite it. Creating a new domain claims it for your account (plan limits apply). Ingesting into a built-in demo domain gives your account its own copy of thatlist_documentsList the documents ingested into a domain's knowledge base.get_rule_sourceFetch a domain's rule set as editable YAML (plus the parsed rules and whether you may edit it). Use this before `put_rules` to see the current rules. For a built-in demo domain you get your own copy's rules once you have edited it, otherwise the shared demo's.put_ruleswrite/deleteCreate or replace a domain's rule set from YAML (self-serve rule authoring). The first save to a new domain claims it for your account (plan limits apply). Saving to a built-in demo domain saves your own copy of it, seeded from the demo; the shared demo others see is unchanged. Rules are validated bimport_policy_rulesConvert a written policy document into DRAFT decision rules (LLM-assisted). Returns validated draft rules (when/action, including chained asserts where the policy stages its determinations), derived rule→rule edges, and overlap warnings. Each returned rule carries a `citation` field holding the poliget_usageShow this account's decision usage, plan, and remaining monthly quota.
Repository · Website · JSON · Text for agents · Registry updated 2026-10-17