Developer · Remote MCP server
AgentAegis
Pay-per-call cybersecurity for AI agents: vuln scans, threat intel, compliance, code security.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.astafford8488/agentaegis- Version
- 0.3.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-06-16
- Updated
- 2026-06-16
- Publisher
- astafford8488 (GitHub) · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/astafford8488) · how
- Repository
- github.com/astafford8488/agentaegis-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://agentaegis-mcp-production.up.railway.app/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- agentaegis 0.2.0 · protocol 2025-06-18
- Tools discovered
28 - show names
compliance_framework_check,evidence_collect,control_gap_analysis,audit_report_generate,policy_generate,vuln_scan_network,vuln_scan_web_app,vuln_prioritize,cve_lookup,ssl_tls_audit,sast_scan,secret_scan,dependency_audit,incident_triage,threat_intel_lookup,dns_security_check,email_security_audit,access_review,mfa_audit,credential_check,vet_endpoint,scan_mcp_plugin,scan_skill,account_balance,help,agent_whoami,agent_history,agent_scan_get- Checked on
- 2026-10-05
How to connect AgentAegis
AgentAegis is a remote MCP server: there is nothing to install. Its endpoint is https://agentaegis-mcp-production.up.railway.app/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from astafford8488 (GitHub)
| Server | Runs |
|---|---|
| Pitchiq MCPAgent-native CRM + get-booked platform. Operate over MCP, or pay per call via x402. No login. | Remote · HTTPLive check: ✓ handshake |
More developer servers
| Server | Runs |
|---|---|
| agent-execAccountless pay-per-use sandbox, storage, locks, attestation and handoff. Paid over MCP with x402. | Remote · HTTPLive check: ✓ handshake |
| agent-godmodeSandboxed workspace MCP: file ops, argv-only run_command, list_files; BYO LLM prompts. | Local · stdio |
| agent-manager.dev documentationDocs for agent-manager, the terminal UI that runs AI coding agents as live tmux sessions. | Remote · HTTPLive check: ✓ handshake |
| agent-toolEncoding-aware, indentation-file tools for AI coding agents with SSH, SFTP, and 20+ tools. | Local · stdio |
| AgentBrain HandoffsExact, durable handoffs between AI coding agents: one turn in the right session, never twice. | Local · stdio |
| AgentbuildersDeploy full-stack AI agent apps with database, auth, storage, and Edge AI on one platform. | Local · stdio |
| AgentBuildersDeploy full-stack web apps with database, file storage, auth, and RBAC via a single API call. | Remote · HTTPLive check: sign-in required |
| agentbuiltFree AI-readiness audit of any URL: AI crawler rules, JS-free text, JSON-LD, llms.txt. Tool catalog. | Remote · HTTPLive check: ✓ handshake |