~ / rigs / Parvathy-Raj / hallucination-firewall

Parvathy-Raj/hallucination-firewall

MCP server that checks an AI agent's answer against its tool outputs before you see it: exact checks, NLI and an LLM judge, with block / annotate / rewrite policies

↗ GitHub ★ 0 MIT updated 5d ago project
field: AI / ML
share on X
ARCHETYPE
Pragmatist
A balanced, no-drama setup: some rules, some tools, nothing extreme.
CONTEXT TAX · EVERY TURN
up to ~5.0k tokens
Claude Code loads MCP tools on demand, so the real cost is usually lower.
Moderate · median rig: 2.3k · breakdown
GUARDRAILS
0/5
No committed guardrails · details
Quality 0/100 Guardrails v2

Copy this rig

# review before running: this installs third-party code
$ claude mcp add hfw -e ANTHROPIC_<redacted> -e HFW_LLM_MODEL=YOUR_HFW_LLM_MODEL -e HFW_LLM_PROVIDER=YOUR_HFW_LLM_PROVIDER -- uv run --project /path/to/hallucination-firewall hfw serve --proxy /path/to/hallucination-firewall/examples/claude_code/downstream.json
$ claude mcp add hallucination-firewall -e ANTHROPIC_<redacted> -e HFW_LEDGER=YOUR_HFW_LEDGER -e HFW_LLM_PROVIDER=YOUR_HFW_LLM_PROVIDER -- uv run --project /path/to/hallucination-firewall hfw serve --proxy /path/to/hallucination-firewall/examples/claude_code/downstream.json

MCP servers are added to Claude Code at local scope; env vars are shown as YOUR_… placeholders — we never store values. Files are fetched with degit into a separate folder so you can review before merging.

$ claude mcp add hfw -e ANTHROPIC_<redacted> -e HFW_LLM_MODEL=YOUR_HFW_LLM_MODEL -e HFW_LLM_PROVIDER=YOUR_HFW_LLM_PROVIDER -- uv run --project /path/to/hallucination-firewall hfw serve --proxy /path/to/hallucination-firewall/examples/claude_code/downstream.json
$ claude mcp add hallucination-firewall -e ANTHROPIC_<redacted> -e HFW_LEDGER=YOUR_HFW_LEDGER -e HFW_LLM_PROVIDER=YOUR_HFW_LLM_PROVIDER -- uv run --project /path/to/hallucination-firewall hfw serve --proxy /path/to/hallucination-firewall/examples/claude_code/downstream.json

This rig commits no guardrails. Here is the community baseline instead — the deny/ask rules most often found across all 16.2k rigs:

{
  "permissions": {
    "deny": [
      "Read(./.env)",
      "Read(./.env.*)",
      "Read(**/.env)",
      "Read(~/.ssh/**)",
      "Bash(git push --force:*)",
      "Read(**/*.pem)",
      "Read(.env)",
      "Read(~/.aws/**)",
      "Read(**/*.key)",
      "Read(**/.env.*)",
      "Bash(git push --force*)",
      "Bash(rm -rf:*)",
      "Bash(rm -rf *)",
      "Bash(sudo *)",
      "Bash(sudo:*)",
      "Bash(rm -rf /)",
      "Bash(git push -f:*)",
      "Read(.env.*)",
      "Bash(git reset --hard*)",
      "Bash(rm -rf /*)"
    ],
    "ask": [
      "Bash(git push:*)",
      "Bash(git push *)",
      "Bash(gh pr merge *)",
      "Bash(git commit:*)",
      "Bash(rm *)",
      "Bash(gh pr merge:*)",
      "Bash(gh pr create *)",
      "Bash(git reset --hard:*)",
      "Bash(npm publish:*)",
      "Bash(git rebase *)"
    ]
  }
}

MCP servers (2)

serversourceest. tokens
/path/to/hallucination-firewall · "hfw"
env: ANTHROPIC_API_KEY, HFW_LLM_MODEL, HFW_LLM_PROVIDER
pypi 2.5k
/path/to/hallucination-firewall · "hallucination-firewall"
env: ANTHROPIC_API_KEY, HFW_LEDGER, HFW_LLM_PROVIDER
pypi 2.5k

Similar rigs

copied ✓