Developer · Remote MCP server
Edgehound
Writes adversarial test suites for AI-built code. Your agent's test engineer.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.Energixe/edgehound-mcp- Version
- 1.1.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-17
- Updated
- 2026-09-17
- Publisher
- Energixe (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/Energixe) · how
- Website
- mcpize.com/mcp/gauntlet
- Repository
- github.com/Energixe/edgehound-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://gauntlet.mcpize.run/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 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Edgehound
Edgehound is a remote MCP server: there is nothing to install. Its endpoint is https://gauntlet.mcpize.run/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 developer servers
| Server | Runs |
|---|---|
| EdgarToolsOpen-source SEC EDGAR toolkit - 11 tools, 7 prompts, every filing type. No API key required. | Local · stdio |
| Edge NetworkDeploy and manage Edge Network cloud: sites, VMs, storage, DNS, Shield, Assist. Agent self-signup. | Remote · HTTPLive check: ✓ handshake |
| EdgegapDeploy and operate multiplayer game servers on Edgegap's global edge network. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| Edgegate MCPRegression-test AI models on real Snapdragon and Jetson hardware, with signed evidence for CI. | Local · stdio |
| EdictAI-agent programming language. JSON AST in, WASM out. Typed, effect-tracked, Z3-verified. | Local · stdio |
| edumints SCORM MCPCompiles structured specs into SCORM 1.2/2004 e-learning packages. 30 tools, quality gate, no LLM. | Remote · HTTPLive check: sign-in required |
| Efficient GitlabToken-efficient GitLab MCP: 167 tools via 3 meta-tools, field projection, keyset pagination. | Local · stdio |
| Ejentum MCPReasoning, code, anti-deception, memory harness MCP tools. Stdio or HTTPS api.ejentum.com/mcp. | Remote & Local · HTTP, stdioLive check: ✗ no handshake |