Secure HTTP
A secure HTTP request executor built with NestJS that enforces security through configurable JavaScript middleware files rather than client-side restrictions. The server uses a whitelist-based approach where no requests are allowed by default - only URLs matching configured middleware patterns can be executed. Middlewares can validate request methods, modify headers (such as adding authentication tokens), transform request bodies, and implement custom authorization logic. This architecture enables safe delegation of HTTP operations to AI assistants while maintaining granular control over which APIs can be accessed and how requests are processed, making it ideal for enterprise environments requiring secure API access with centralized policy enforcement.
Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-28.
Scan details: Circle-IR · 2026-09-28 · Appeal
View full trust & usage report →Metadata
- Version
- 1.0.0
- Skill type
- atomic
- Execution layer
- mcp-remote
- Category
- security
- Source
- PulseMCP
- Repository
- github.com/teppichseite/secure-http-mcp
- Author type
- human
- Last scanned
- 2026-09-28
- Updated
- 2026-09-28
Use via MCP
Resolve Secure HTTP from your agent
Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.
One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.
claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp--scope user for --scope project to commit it to .mcp.json.