prompt protection API for AI agents
MCP Prompt Protection Server
MCP-compatible agents can discover Parse Agents tools, then call screening functions through the hosted remote MCP endpoint or use the REST API directly.
When to call it
| Trigger | Endpoint | MCP tool |
|---|---|---|
| Untrusted user input, RAG content, browser output, email, documents, webhook bodies, or tool results before an agent acts | POST /v1/parse |
screen_prompt |
| LLM output before showing it to a user, storing it, or sending it to another tool or agent | POST /v1/screen-output |
screen_output |
| A peer agent, plugin, or service asks for delegation or requests sensitive work | POST /v1/agent/trust/verify |
verify_agent_trust |
| An agent has no bearer API key but can pay per request | POST billable endpoints with x402 |
get_pricing |
Primary endpoint
POST /mcp
Claude Desktop and Claude Code
Cursor and Windsurf
Replit agents
Custom MCP clients
Signals Parse Agents checks
The hosted detector checks 9 risk categories with 107 deterministic pattern rules, structural analysis, optional LLM semantic analysis, and optional sandbox execution.
- screen_prompt
- screen_output
- verify_agent_trust
- get_pricing
Agent integration
POST https://www.parsethis.ai/mcp
Authorization: Bearer <key>
Content-Type: application/json
{"prompt":"untrusted text here","metadata":{"source":"tool_output"}}
No key? For billable REST endpoints, call without Authorization, read the 402 payment requirements, sign USDC on Base mainnet, and retry with payment-signature.