API archive entry · source-reported

InjectScan

Scores text, web pages and MCP tool definitions for prompt injection with deterministic rules

Provider / source website

From the publisher

README & documentation

Source preview

Read the project’s overview, installation instructions and usage examples. The original README is the source of truth.

Prompt-injection detection for AI agents (MCP server + x402 API). Safety check only. InjectScan is a deterministic, documented rule engine. It returns a risk score (0-100), a verdict (safe / suspicious / malicious), the categories that fired, and every finding as a character span in your original text, so you can highlight or strip it. Use it on web pages, emails, documents, tool results and other agents' messages before your agent acts on them. Claude Code: Claude Desktop: Settings > Connectors > Add custom connector with the URL above, or in claudedesktopconfig.json: Cursor (/.cursor/mcp.json), or one click: Add to Cursor Each free result includes an upgrade field with the calls left today. Past the daily limit the tool returns a paymentrequired (402) result with the paid x402 URL. Requires Node.js 20+ (or Docker). The server has no runtime dependencies. No git? Download…

Duffey234/injectscan on GitHub A short preview, not the full document.

Read the full README ↗ · Preview checked 2026-11-04T20:02:08.264Z

Inside the original README — Document outline
  1. InjectScan
  2. Use the hosted server (no install)
  3. Self-host: run from source (no npm registry)
  4. Docker
  5. Test
  6. Full source

Headings are captured from the source. Links open the publisher’s document, not a locally hosted copy.

Documentation belongs to its respective authors. A listing is not a grant of reuse or training rights. Confirm the document’s own terms at the source.

Where these facts came from

AltAPIs imported it from public-apis/public-apis. The source link and dates remain visible for independent inspection.

What is reported

  • Name, category, and short description
  • Authentication label
  • HTTPS and CORS labels
  • Provider/source URL

What is not established

  • Current uptime or availability
  • Pricing, quotas, and rate limits
  • Security, compliance, or licensing posture
  • SDK quality or endpoint completeness

Record checkpoints

  1. First observed: Nov 4, 2026
  2. Last directory-field change: Nov 4, 2026
  3. Current source observation: Nov 4, 2026

Submit a source-backed correction

Source reference

public-apis/public-apis

This page separates source-reported facts from questions that need live provider verification.