pyresec
Provides a GitHub Action for CI/CD integration, allowing PYRESEC security scans to be run automatically in GitHub workflows with configurable code path and scan tier.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@pyresecquick scan this for SQL injection: db.query(f"SELECT * FROM users WHERE id={uid}")"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
PYRESEC — AI Code Security Engine
Autonomous SAST/SCA security auditing via x402 USDC micropayments on Base. No subscriptions. No accounts. Just code in, findings out.
Live Instance
Endpoint | URL |
Landing | |
Swagger UI | |
Health | |
MCP Manifest | |
OpenAPI Spec |
Related MCP server: agentguard
Quick Start
Option 1: x402 Python Client (Recommended)
pip install x402import x402
client = x402.Client(wallet_key="your-base-private-key")
response = client.post(
"https://pyresec-agent-519576377065.us-central1.run.app/v1/audit/quick-scan",
json={"code": "def login(u,p): return db.query(f\"SELECT * FROM users WHERE name={u} AND pass={p}\")"}
)
print(response.json())Option 2: curl (Manual x402 Flow)
# Step 1: Send request (returns 402 with payment requirements)
curl -X POST https://pyresec-agent-519576377065.us-central1.run.app/v1/audit/quick-scan \
-H "Content-Type: application/json" \
-d '{"code": "def login(u,p): return db.query(f\"SELECT * FROM users WHERE name={u} AND pass={p}\")"}'
# Step 2: Pay $0.01 USDC on Base using x402 protocol
# Step 3: Resubmit with X-PAYMENT header
curl -X POST https://pyresec-agent-519576377065.us-central1.run.app/v1/audit/quick-scan \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <payment-proof>" \
-d '{"code": "..."}'Option 3: GitHub Action (CI/CD)
- name: PYRESEC Security Scan
uses: nanoclone-ltd/pyresec-scan-action@main
with:
code-path: ./src
tier: quick-scan
x402-wallet-key: ${{ secrets.X402_WALLET_KEY }}Option 4: MCP-Compatible Agent (Claude, Cursor, etc.)
PYRESEC is a registered MCP tool. Any MCP-compatible client discovers it automatically:
{
"mcpServers": {
"pyresec": {
"url": "https://pyresec-agent-519576377065.us-central1.run.app/mcp"
}
}
}Service Tiers
Tier | Price | Endpoint | Description | Model |
Quick Scan | $0.01 |
| Top 3 findings by severity, CWE IDs, line numbers | qwen3.6-27b |
Deep Audit | $0.50 |
| OWASP Top 10, SCA dependency scanning, logic flaws, gas optimization | qwen3.8-27b |
Remediation | $5.00 |
| Full patched code with change explanations and security notes | qwen3.8-27b |
x402 Payment Flow
PYRESEC uses the x402 protocol for permissionless micropayments on Base. No accounts, no API keys, no subscriptions.
┌──────────┐ POST /v1/audit/quick-scan ┌──────────┐
│ Client │ ───────────────────────────────▶ │ PYRESEC │
│ (x402) │ ◀──── 402 Payment Required ───── │ Agent │
│ │ { amount, network, to } │ │
│ │ │ │
│ │ ──── X-PAYMENT (proof) ─────────▶ │ │
│ │ ◀──── 200 + Scan Results ──────── │ │
└──────────┘ └──────────┘How it works:
Client sends a POST request to any audit endpoint
PYRESEC returns
402 Payment Requiredwith payment details (amount, recipient address, network)Client signs and submits a USDC transfer on Base mainnet
Client resubmits the original request with the
X-PAYMENTheader containing the payment proofPYRESEC verifies the payment on-chain and returns the scan results
No wallet? Use the x402 Python SDK or any x402-compatible client.
Architecture
┌─────────────────────────────────┐
│ Client Layer │
│ x402 SDK / curl / MCP Client │
└──────────────┬──────────────────┘
│
┌─────────▼─────────┐
│ FastAPI Server │
│ (Cloud Run) │
│ │
│ ┌──────────────┐ │
│ │ x402 Payment │ │
│ │ Middleware │ │
│ └──────┬───────┘ │
└─────────┼──────────┘
│
┌───────────────────┼───────────────────┐
│ │ │
┌─────────▼─────────┐ ┌───────▼───────┐ ┌───────▼───────┐
│ Agent Controller │ │ Population │ │ Wallet │
│ (SAST + LLM) │ │ Controller │ │ Interface │
└─────────┬─────────┘ └───────────────┘ └───────────────┘
│
┌─────────▼─────────┐
│ Groq LLM │
│ (qwen models) │
└─────────┬─────────┘
│
┌─────────▼─────────┐
│ Security Findings │
│ JSON Response │
└───────────────────┘Supported Vulnerability Types
# | Type | CWE | Severity |
1 | SQL Injection | CWE-89 | HIGH |
2 | Cross-Site Scripting (XSS) | CWE-79 | HIGH |
3 | Command Injection | CWE-78 | CRITICAL |
4 | Path Traversal | CWE-22 | MEDIUM |
5 | Hardcoded Secrets | CWE-798 | CRITICAL |
6 | Weak Cryptography | CWE-327 | MEDIUM |
7 | SSRF | CWE-918 | HIGH |
8 | Insecure Deserialization | CWE-502 | HIGH |
9 | Authentication Bypass | CWE-287 | CRITICAL |
10 | Improper Input Validation | CWE-20 | MEDIUM |
For AI Agents (MCP Integration)
PYRESEC is discoverable by any MCP-compatible agent. When an agent needs to audit code, it can find PYRESEC automatically through:
MCP Registry:
registry.modelcontextprotocol.ioSmithery.ai:
smithery.ai/server/@renaat-s/pyresec-agentDirect manifest:
/mcp/manifest.json
Tool Definitions
Tool | Description | Cost |
| Fast SAST scan, top 3 findings by severity with CWE IDs | $0.01 USDC |
| Full OWASP Top 10, SCA, logic flaws, gas optimization | $0.50 USDC |
| Auto-patched code with change explanations, ready for PR | $5.00 USDC |
Agent Discovery Flow
1. Agent queries MCP Registry for "security audit" tools
2. PYRESEC appears in results with tool schemas
3. Agent calls quick_scan with source code
4. PYRESEC returns 402 with x402 payment requirements
5. Agent's x402 wallet pays USDC on Base
6. Agent resubmits with payment proof
7. PYRESEC returns findings as structured JSONSelf-Sustaining Agent
PYRESEC runs as an autonomous agent on Base Mainnet:
Heartbeat every 30 min — checks balance, reports health
Death — shuts down if balance < $0.05
Replication — sends 50% surplus to dev wallet when balance > $20
Kill switch — admin can halt all instances remotely
Deployment
Docker
docker build -t pyresec-agent .
docker run -p 8080:8080 --env-file .env pyresec-agentGoogle Cloud Run
gcloud run deploy pyresec-agent \
--source . \
--platform managed \
--region us-central1 \
--allow-unauthenticated \
--set-env-vars "CDP_WALLET_SECRET=$CDP_WALLET_SECRET,GROQ_API_KEY=$GROQ_API_KEY"Company
NanoClone Life Sciences Ltd. (UK) Website: nanoclonesystems.com
License
Proprietary. See LICENSE for details.
This server cannot be deployed
Maintenance
Related MCP Connectors
Paid OpenAPI audit and API change detection for agents. $0.10 USDC per analysis via x402 on Base.
Paid MCP tools behind one endpoint. Agents pay per call in USDC on Base via x402.
15 paid AI agent primitives via x402 (USDC on Base). Pay-per-call MCP server.
AI/LLM agent output audit MCP: policy eval, tamper-evident chain, AI safety, x402 USDC on Base.
Related MCP Servers
- AlicenseAqualityCmaintenanceAgent-native "safe to ship?" security gate for AI-generated code. Uses real parsers and inter-rocedural taint analysis (JS/TS, Python, Go) to flag the classes AI coding agents get wrong — secrets, SQL injection, SS, SSRF, path traversal, command injection, weak JWT/CORS — and ranks findings by confidence. Exposes a scan tool over MCP.14 npm2MIT
- AlicenseNot gradedqualityAmaintenanceEnables scanning of AI agent code for security vulnerabilities such as prompt injection, tool abuse, and data exfiltration, directly from MCP-compatible clients like Claude Code.2LGPL 3.0
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to scan code for security and quality issues and receive machine-readable reports with suggested fixes and verification criteria.48 npm2MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to scan code for security vulnerabilities before execution, supporting Python and JavaScript/TypeScript with deterministic AST-based analysis and optional Solana micropayments.-