mcpField
G
GrindFree Agent Security

GrindFree Agent Security

Local
github.com/ronin93Other0Updated today

About GrindFree Agent Security

GrindFree Agent Security is an MCP server and client-snippet collection for paid agent-security APIs on Base. Its rule-based services screen prompts, documents, memory, tool calls, commands, URLs and outbound content; callers must enforce advisory decisions.

Key features

  1. 01Prompt-injection screening and text cleaning
  2. 02URL crawl-policy checks
  3. 03Pre-call tool policy decisions
  4. 04Shell command and SQL checks
  5. 05Memory and outbound-content screening
  6. 06Hidden-instruction document scanning

Use cases

  1. 01Screen prompts before agent processing
  2. 02Review commands and SQL before execution
  3. 03Check content before saving to agent memory
  4. 04Inspect documents or output for hidden instructions and leaks

MCP support

Exposes GrindFree security API operations as MCP tools, including screening, policy checks, document scans and an unpaid discovery probe. Calls are paid in USDC on Base via x402 v2.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"ronin93-grindfree-agent-security": {
"command": "npx",
"args": [
"-y",
"@grindfree/agent-security-mcp"
],
"env": {
"X402_PRIVATE_KEY": "<X402_PRIVATE_KEY>"
}
}
}
}
Run commandnpx -y @grindfree/agent-security-mcp
Environment variables to set
X402_PRIVATE_KEYSecretCaller's own Base USDC EVM private key (0x…). Used only by the local MCP host to settle x402 payments. Never a GrindFree key; never commit this value.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@grindfree/agent-security-mcp0.2.0

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

GrindFree Agent Security

MCP server + client snippets for GrindFree’s pay-per-call agent security APIs on Base:

ServiceEndpointPriceWhat it does
PromptShieldPOST https://promptshield.grindfree.net/v1/screen · /v1/clean$0.002Prompt-injection screen + HTML→LLM clean text
CrawlSafePOST https://crawlsafe.grindfree.net/v1/check$0.002robots.txt / X-Robots-Tag crawl gate (SSRF-guarded; not malware scanning)
ToolGuardPOST https://toolguard.grindfree.net/v1/evaluate$0.002Pre-tool-call allow | review | deny policy gate
CommandGuardPOST https://commandguard.grindfree.net/v1/command · /v1/sql$0.001Shell command + SQL check before execution: allow | warn | block
MemoryGuardPOST https://memoryguard.grindfree.net/v1/screen$0.002Screen content before it is written to agent memory (planted instructions, persistence, secrets/PII)
WireShieldPOST https://wireshield.grindfree.net/v1/scan$0.002Outbound leak check on agent output (zero-click image exfil, URL smuggling, canaries, prompt leakage)
DocShieldPOST https://docshield.grindfree.net/v1/scan$0.004Hidden instructions in PDF / DOCX / XLSX / PPTX / HTML / Markdown before the agent reads them

Price: per call in USDC (table above) on Base (eip155:8453) via x402 v2.
Wallet: the caller’s Base USDC wallet pays. This repo never ships GrindFree keys.

Contact: [email protected] · @grindfreelabs


Install / run the MCP server (stdio)

git clone https://github.com/ronin93/grindfree-agent-security.git
cd grindfree-agent-security/mcp-server
npm install

Set the caller’s funded Base USDC key in the MCP host env (never commit it):

export X402_PRIVATE_KEY=0xYOUR_BASE_USDC_PRIVATE_KEY
# PRIVATE_KEY is also accepted
node src/index.js

Claude Desktop / Cursor-style config:

{
  "mcpServers": {
    "grindfree-agent-security": {
      "command": "node",
      "args": ["/absolute/path/to/grindfree-agent-security/mcp-server/src/index.js"],
      "env": {
        "X402_PRIVATE_KEY": "0xYOUR_KEY"
      }
    }
  }
}
MCP tools
  • promptshield_screen / promptshield_clean
  • crawlsafe_check
  • toolguard_evaluate — your agent must enforce allow/review/deny before executing the tool; this API cannot stop a bypass
  • commandguard_command / commandguard_sql — check shell commands and SQL before running them
  • memoryguard_screen — check content before saving it to long-term memory
  • wireshield_scan — check agent output before rendering/sending it
  • docshield_scan — check a local file (path), base64 bytes, or HTML/Markdown for hidden instructions (max 3 MB)
  • grindfree_discovery — unpaid 402 / discovery probe (no spend)

HTTP snippets (no MCP)

  • examples/typescript-x402-fetch.ts — official @x402/fetch + @x402/evm
  • examples/python-x402.py — unpaid probes + paid hook
  • examples/langchain-tool.py — LangChain-style wrappers

Unpaid challenge (no wallet):

curl -sS -D - -o /tmp/ps402.json -X POST https://promptshield.grindfree.net/v1/screen \
  -H 'content-type: application/json' \
  -d '{"content":"hi","format":"text"}'
# Expect HTTP 402 + PAYMENT-REQUIRED

Honest limits

  • Heuristic / policy layers — not a full security program.
  • CrawlSafe is not malware, phishing, or legal/ToS advice.
  • All guards are deterministic rule packs (no LLM), so they are fast and cheap but can miss novel phrasing; decisions are advisory and your code must enforce block/deny.
  • DocShield parses structure and text; it does not OCR images or render pages, and legacy .doc/.xls/.ppt return 415 (not charged).
  • ToolGuard returns a decision; the caller/adapter must enforce it before tool execution. Missing policy → review. Not an exfiltration guarantee.
  • ToolGuard: always enforce allow|review|deny in your adapter before tool execution (the API cannot stop a bypass). GrindFree has confirmed funded settlement + HTTP 200 delivery on /v1/evaluate via a self-funded Base USDC test; still verify with your own wallet in production.

License

MIT — see LICENSE.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.