A
licenseA
qualityD
maintenanceProvides secure OAuth2-based credential management for MCP servers, allowing agents to obtain short-lived token references without exposing raw secrets.
7
3 npm
MIT
ForgeFuzz Cloud MCP Demo
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ForgeFuzz Cloud MCP Democall the GET /users endpoint and show the response"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
ForgeFuzz Cloud MCP Demo
Capabilities
2 tools
1 resource
2 prompts
Related MCP server: mcp-gateway
Transport
streamable-http
Base URL: http://localhost:3500/mcp
Authentication
bearer
Set MCP_AUTH_TOKEN in the environment. The server will require Authorization: Bearer <token> on every request.
Run and verify
Copy .env.example to .env and fill the token and upstream values. HTTP tool calls use the OpenAPI server URL, or UPSTREAM_BASE_URL when set; UPSTREAM_AUTHORIZATION supplies upstream credentials.
For HTTP, set MCP_SERVER_URL and run node tests/contract/run.mjs. Integration calls require MCP_TEST_ARGUMENTS (a JSON object mapping tool names to test arguments) and node tests/integration/run.mjs. Use a test upstream because tool calls execute real operations. For stdio, use MCP_STDIO_COMMAND containing a JSON array such as ["node","dist/index.js"] instead of an HTTP URL. All protocol runners require Node.js 20+. Native unit tests use npm test, pytest or mvn test.
License
MIT
Generated by ForgeQ MCP Generation.
Run locally
npm install
npm run build
export MCP_AUTH_TOKEN=
npm start # listens on http://localhost:3500/mcpRelated MCP Connectors
Governed MCP gateway: one endpoint for your tools, with credential custody and audit log.
Browser MCP for logged-in tasks. Uses your Chrome — credentials stay local. Zero-token replay.
Remote MCP for A2A caller identity, scope policy, verdict receipts, and audit history.
One OAuth connector for your team's remote MCP servers, with Tool Packs, guardrails and logs.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables clients to access multiple backend MCP servers through a single endpoint, with OAuth 2.1 authorization, namespaced tools, and secure credential management.2MIT
- AlicenseNot gradedqualityBmaintenanceEnables end-to-end testing of OAuth authorization for an MCP server, exposing scoped tools like whoami and echo over streamable HTTP.ISC
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to exchange an MCP-audience token for a Microsoft Graph token and call Graph as the signed-in user, with tools for identity verification and recent mail access.MIT