Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

PYRESEC - AI Code Security Auditing

by renaat-sversion 2.0.1i★ –iRuns in the cloud
Registry nameio.github.renaat-s/pyresec-agent

Install

Overview

Description from the maker (original English)

AI code security audits via x402 USDC: $0.01 scans, $0.50 audits, $5 auto-fixes. SAST/SCA.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs in the cloud
  • Transport: Streamable HTTP
  • Category: Cybersecurity

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on the maker’s server: what you ask it goes through their server.
  • The registry lists no key to fill in.

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

  1. Open Settings → Connectors
  2. Press Add custom connector
  3. Paste the address below and press Add
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Add2https://…3
https://pyresec-agent-519576377065.us-central1.run.app/mcp

Run this in your terminal

claude mcp add --transport http pyresec-agent https://pyresec-agent-519576377065.us-central1.run.app/mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "pyresec-agent": {
      "url": "https://pyresec-agent-519576377065.us-central1.run.app/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "pyresec-agent": {
      "type": "http",
      "url": "https://pyresec-agent-519576377065.us-central1.run.app/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

  1. Open ChatGPT on the web → Settings → Connectors (Apps)
  2. Press Create or Add (some plans need Developer mode under Advanced first)
  3. Paste the address below, give it a name and save
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Create2https://…3
https://pyresec-agent-519576377065.us-central1.run.app/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account renaat-s, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • … Not checked yet

    Endpoint responds

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    Sign-in with OAuth

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

Compared with others in Cybersecurityi

  • More stars than 0% of the other 993 servers in this category
  • Published to the registry more recently than 52% of the other 993 servers in this category
  • Basic checks equal to or better than 100% of the other 993 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is PYRESEC - AI Code Security Auditing safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (2.0.1) reached the registry 41 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: ipdata MCP by usefulapi, MaxMind minFraud MCP by usefulapi, Lambda Labs MCP by usefulapi

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Look up location, network, company and threat data for IP addresses and ASNs in ipdata.

Runs in the cloudUpdated today
Install

Read GPU instances, types, images, filesystems and firewall rules; launch and terminate instances.

Runs in the cloudUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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


Quick Start

Option 1: x402 Python Client (Recommended)
pip install x402
import 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: " \ -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

TierPriceEndpointDescriptionModel
Quick Scan$0.01POST /v1/audit/quick-scanTop 3 findings by severity, CWE IDs, line numbersqwen3.8-27b
Deep Audit$0.50POST /v1/audit/deep-repoOWASP Top 10, SCA dependency scanning, logic flaws, gas optimizationqwen3.8-27b
Remediation$5.00POST /v1/audit/remediateFull patched code with change explanations and security notesqwen3.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:

  1. Client sends a POST request to any audit endpoint
  2. PYRESEC returns 402 Payment Required with payment details (amount, recipient address, network)
  3. Client signs and submits a USDC transfer on Base mainnet
  4. Client resubmits the original request with the X-PAYMENT header containing the payment proof
  5. PYRESEC 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

#TypeCWESeverity
1SQL InjectionCWE-89HIGH
2Cross-Site Scripting (XSS)CWE-79HIGH
3Command InjectionCWE-78CRITICAL
4Path TraversalCWE-22MEDIUM
5Hardcoded SecretsCWE-798CRITICAL
6Weak CryptographyCWE-327MEDIUM
7SSRFCWE-918HIGH
8Insecure DeserializationCWE-502HIGH
9Authentication BypassCWE-287CRITICAL
10Improper Input ValidationCWE-20MEDIUM

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.io
  • Smithery.ai: smithery.ai/server/@renaat-s/pyresec-agent
  • Direct manifest: /mcp/manifest.json
Tool Definitions
ToolDescriptionCost
quick_scanFast SAST scan, top 3 findings by severity with CWE IDs$0.01 USDC
deep_auditFull OWASP Top 10, SCA, logic flaws, gas optimization$0.50 USDC
remediate_codeAuto-patched code with change explanations, ready for PR$5.00 USDC
Agent Discovery Flow
1. Agent queries MCP Registry for "security audit" tools
  1. PYRESEC appears in results with tool schemas
  2. Agent calls quick_scan with source code
  3. PYRESEC returns 402 with x402 payment requirements
  4. Agent's x402 wallet pays USDC on Base
  5. Agent resubmits with payment proof
  6. PYRESEC returns findings as structured JSON

Self-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-agent

Google 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.

Ask PopNx