rest_api_mcp
A Model Context Protocol (MCP) server for authenticated REST APIs. Drop it into any project, point it at your API, and let AI agents call endpoints — with auto-login, 2FA support, Swagger spec fetch, and fuzzy endpoint search — all without writing a single line of auth code.
Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.
How we verified
Verified is a snapshot. Live keeps it current, and builds your track record.
⚡ Connect GitHub → continuous verification on every pushwhy connect →Who stands behind it
Muhammed-AbdelGhany
Source: Glama
Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →
Install from
The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.
Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.
axios Vulnerable to Full Man-in-the-Middle via Prototype Pollution Gadget in `config.proxy`
axios Vulnerable to Credential Theft and Response Hijacking via Prototype Pollution Gadget in Config Merge
Axios: Header Injection via Prototype Pollution
Allocation of Resources Without Limits or Throttling in Axios
Axios: Regular Expression Denial of Service (ReDoS) via Cookie Name Injection
API_EMAILLogin emailAPI_LOGIN_CREDENTIALSSet to a JSON object string containing any extra fields you need. They are merged into the login POST body alongside email and password:API_LOGIN_ENDPOINTOverride login path, e.g. /auth/sign-inAPI_OTPThe OTP value to submit. For staging environments this is usually a fixed test code provided by the API team. For production you'd need to retrieve the live code from your email and set it here.API_PASSWORDLogin passwordAPI_SWAGGER_URLOpenAPI/Swagger JSON URL — enables fetch_spec, search_endpoints, and auto-login-endpoint discoveryAPI_TOKEN_PATHDot-path to token in login/verify response, e.g. data.access_tokenAPI_VERIFY_CREDENTIALSIf your verify endpoint requires extra fields that aren't session identifiers or the OTP, add them here:API_VERIFY_ENDPOINTThe path of the second step. When this is set, the server automatically performs both steps before attaching a token to your request.REST_BASE_URLBase URL of the API (no trailing slash)REST_ENABLE_SSL_VERIFYSet false to skip TLS cert validation (dev/staging only)REST_RESPONSE_SIZE_LIMITReturns the raw OpenAPI JSON (truncated to if large).Tool annotations
No tools have read-only/destructive annotations
Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.
All four hints declared on every tool
5/5 tools missing one or more hints — fetch_spec (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); search_endpoints (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); describe_endpoint (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +2 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.
For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.
Tests exist
No test files found
Add tests that exercise each declared tool.
Secrets stay with their owner
2 secrets sent to a request target we could not resolve (API_PASSWORD → dynamic, API_PASSWORD → dynamic) — often a configured endpoint, not necessarily third-party
Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.
Production dependencies are patched
0 critical, 10 high severity in production deps — axios@1.14.0 (high), axios@1.14.0 (high)
Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.
Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.
[](https://m8ven.ai/mcp/muhammed-abdelghany/rest_api_mcp)?variant=verified from the URL.Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.
https://m8ven.ai/api/mcp/tool-check