mcp-authprobe
Related Servers
Alternatives to mcp-authprobe
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables AI assistants to perform authorized web security assessments through MCP tools and a guided review prompt, including passive and full scans, WAF detection, remediation fixes, report export, triage, scan comparison, and proof-of-control verification.125MIT
- AlicenseAqualityAmaintenanceA specialized testing harness that enables AI assistants to thoroughly test other MCP servers by connecting to them, discovering their tools/resources/prompts, executing test calls, and performing end-to-end validation with LLM integration.144MIT
- AlicenseBqualityCmaintenanceEnables read-only security assessment of a public MCP endpoint by sending initialize and tools/list requests and returning a 0–100 score covering transport, auth, overly broad tools, injection phrasing, and rug-pull definition changes, plus a 12-probe prompt-injection suite against a bot you own that flags leaked system prompts, tool dumps, secrets, exfiltration channels, and canary obedience.2MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to launch AI persona tests against public web app URLs in a real browser, then retrieve status, findings, screenshots, and combined fix prompts for coding agents.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI clients to drive professional penetration-testing workflows—subdomain enumeration, host probing, content fuzzing, vulnerability scanning, brute-force, traffic capture, and exploitation sweeps—through a single MCP interface with stdio, Streamable HTTP, and legacy SSE transports plus bearer/OIDC auth. It also records engagement artifacts and generates client-ready reports with scope handling, cutting manual pentest administration.298 npmGPL 3.0
- AlicenseNot gradedqualityBmaintenanceLets any MCP client, such as Claude, browse attack suites and probes, run a full assurance assessment with all reports written out, send custom prompts or multi-turn histories and get leak, PII and refusal checks back for adaptive attacks, and read findings from an earlier assessment. This enables agent-driven red-teaming of a chatbot, RAG app or AI agent without leaving the chat client.MIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: listing checks, explaining a check, retrieving an ownership proof, verifying ownership, and running a scan. The two ownership-related tools are complementary rather than overlapping—one returns the proof to publish, the other verifies it.
Most names follow a verb_noun or verb_object pattern (list_checks, explain_check, verify_ownership), but ownership_proof is a noun phrase and scan is a bare verb. The minor deviations are still readable and predictable.
Five tools is well-scoped for an auth-probing MCP server. Each tool earns its place in the workflow: discovery, explanation, proof generation, verification, and scanning.
The surface covers the full ownership-proof and scan lifecycle. Minor gaps exist, such as no explicit tool to retrieve past scan results or filter checks, but core workflows are covered.