mcpward is a gateway designed for MCP servers, addressing authentication, audit logging, and endpoint reliability challenges. It is positioned for solo developers and small teams who require a production-grade solution for managing access and monitoring activity across multiple MCP servers.
The platform provides a reverse proxy that aggregates tools from various MCP servers, allowing users to centralize access and control. Authentication options include simple API key authentication as well as OAuth with transparent token refresh. mcpward supports per-tool role-based access control, enabling fine-grained permissions over which agents can access specific tools. Rate limiting and daily quotas are built in to help manage usage and prevent abuse. Audit logs are signed using Ed25519, providing tamper-proof records of activity, and health checks are included to monitor the status of upstream MCP endpoints.
mcpward is accessible via an API endpoint, with setup involving obtaining an API key and configuring MCP clients to connect through the service. Pricing includes a free tier that supports one MCP server, up to 5,000 calls per day, API key authentication, and basic audit logs. Paid plans offer additional features such as support for unlimited servers, OAuth and RBAC, signed logs, tool aggregation, single sign-on, audit export, and email support. There is also a pay-per-call option using micropayments, and a self-hosted deployment is available upon request.
fr and distinguishes itself as an independent project not affiliated with other MCP gateway solutions. It is designed to improve security, observability, and reliability for teams operating MCP infrastructure.
mcpward-verify is a Security & compliance platforms project. Enabling developers to verify the authenticity of audit log records from mcpward gateway using Ed25519 signatures. mcpward-verify is an open-source project aimed at developers needing audit log verification. The project is open source (MIT). It runs on the web and the command line.
Behind mcpward-verify is dbe006, and it first shipped in 2026. The project is developed in the open on GitHub with 2 commits in the last 90 days. Among its 4 catalogued features are audit log verification, ed25519 signature check, and Standalone CLI. It exposes integrations via an MCP server.
Summary written by a language model from the project’s public pages.
What PulseGate has recorded for this listing
Closest matches by what these projects do