Security & Testing
vulny.app
Provides tools for vulnerability scanning and API key management for security testing.
ENDPOINT 1
https://agent-api.vulny.app/mcp
MCP server metadata
- Name
- vulny-agent-scan
- Version
- 1.0.0
Known tools 10
recover_keyRecover access: emails a one-time link to your on-file address to issue a NEW API key.
Inferred read-onlyget_balanceShow your scan allowance: prepaid credits + verified domains (credit accounts), or subscription plan + target limit (subscription tokens).
Inferred read-onlyexport_dataExport all data Vulny holds for this account (profile, scans, payments) as JSON — GDPR data access.
Inferred read-onlydelete_dataPermanently delete this account and ALL its data (scans, findings, payments, API keys) — GDPR erasure.
Potential side effectsmanage_billingGet a secure Stripe billing portal link where the user can view payments and invoices and add, change or REMOVE their saved card.
Potential side effectsCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.vulny-agent-scan]
url = "https://agent-api.vulny.app/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"vulny-agent-scan": {
"type": "http",
"url": "https://agent-api.vulny.app/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: vulny-agent-scan
Remote MCP URL: https://agent-api.vulny.app/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"vulny-agent-scan": {
"url": "https://agent-api.vulny.app/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"vulny-agent-scan": {
"type": "http",
"url": "https://agent-api.vulny.app/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "vulny-agent-scan",
"transport": "streamable-http",
"url": "https://agent-api.vulny.app/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.