Developer · Remote MCP server

Shadowgate MCP

Security firewall for AI agents - scans MCP calls for injection, secrets, and risks.

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
io.github.josephibra/shadowgate-mcp
Version
1.0.0
Status
Active
Category
developer
Transport
Streamable HTTP
Published
2026-05-14
Updated
2026-05-14
Publisher
josephibra (GitHub) · 2 servers with pages here
Namespace
Namespace verified by the MCP Registry via GitHub (github.com/josephibra) · how
Repository
github.com/josephibra/shadowgate-mcp
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://shadowgate-mcp.mcp.xpay.sh/mcpNone

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
Checked on
2026-10-05

How the live check works

How to connect Shadowgate MCP

Shadowgate MCP is a remote MCP server: there is nothing to install. Its endpoint is https://shadowgate-mcp.mcp.xpay.sh/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 josephibra (GitHub)

All 2 →
ServerRunsEndpoint or package
Handoff MCP ServerDurable agent-to-agent handoffs and shared scratchpad for multi-agent workflows.Remote · HTTPLive check: sign-in requiredhandoff-mcp-server-production.mcp.xpay.sh

More developer servers

All 5,152 →
ServerRunsEndpoint or package
Setup DoctorScore and improve your AI coding agent setup. Local-only, open source.Local · stdionpm: setup-doctor
SeturosShared work memory for Claude Code, Codex, Cursor and chat, scoped to each repository.Remote · HTTPLive check: sign-in requiredapp.seturos.com
Sexai MCPThe network where AI agents breed - publish, import a GitHub repo as an agent, cross them.Local · stdionpm: sexai-mcp
Sfcc Dev MCPMCP server for Salesforce B2C Commerce Cloud development assistance.Local · stdionpm: sfcc-dev-mcp
shaft-mcpSHAFT browser automation, capture, and offline deterministic failure diagnosis.Local · stdioOCI image (Docker): ghcr.io/shafthq/shaft-engine-mcp:10.3.20260930
ShardfluxPersistent cloud workspaces for AI agents: run commands, edit files, use git and a browser.Local · stdionpm: @shardflux/mcp
Share HTMLCreate sandboxed public-unlisted or access-key-protected HTML previews through a remote MCP server.Remote · HTTPLive check: ✓ handshakeshare-html.zhenjiazhou0127.workers.dev
SharebenchSharebench - search & pull AI skills, agents, prompts & playbooks (SKILL.md) into any MCP client.Remote · HTTPLive check: ✓ handshakemcp-public.sharebench.ai