Back to search
edpay-mcp-server
MCP serverGitHub
Standalone hosted EDPay MCP server and integration tools.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Checked today
Badge for your README
Markdown
[](/listings/edutecka--edpay-mcp-server)HTML
<a href="/listings/edutecka--edpay-mcp-server"><img src="/api/listings/edutecka--edpay-mcp-server/badge.svg" alt="findsafeskills safety rating" /></a>Install
i
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
README.md · README · 39 lines
- # EDPay MCP Server
- This repository contains the EDPay Streamable HTTP MCP server. It reads the public, versioned API contract bundled with the source and calls EDPay over HTTPS for its limited invoice actions.
- ## Hosted endpoint
- When deployed behind the API ingress, the endpoint will be `https://api-pay.edutecka.com/mcp`, with public key-setup instructions at `https://api-pay.edutecka.com/mcp/setup`. The setup response requires no authentication and explains where a customer creates their own EDPay keys. It never returns or retrieves credential values.
- Read-only MCP tools work without customer keys. Invoice tools use the caller's matching EDPay key pair in `X-EDPay-Public-Key` and `X-EDPay-Private-Key` request headers and require the `invoices:write` scope. Store those values in the MCP client's secure secret store. Never put them in tool arguments, prompts, URLs, browser code, repositories, or logs.
- `pk_test_` with `sk_test_` selects Sandbox. `pk_live_` with `sk_live_` selects Production. Mixed pairs are rejected; the EDPay API validates credentials and account environment.
- ## Run the HTTP service
- Build and run the container with the deployment's approved container workflow. It listens on port `23883` and expects a trusted reverse proxy to publish `/mcp` and `/mcp/setup` on the API HTTPS origin. The application binds only inside its container in non-container local mode; set `EDPAY_MCP_BIND_HOST=0.0.0.0` only when the container network and ingress rules are configured for it.
- The deployment must set `EDPAY_MCP_ALLOWED_HOSTS` and `EDPAY_MCP_ALLOWED_ORIGINS` to the exact customer-facing API host and browser origin. The defaults are `api-pay.edutecka.com` and `https://api-pay.edutecka.com`. Do not enable wildcard origins or access logging for credential headers.
- ## Environment
- - `EDPAY_MCP_PORT`: internal HTTP port (default `23883`).
- - `EDPAY_MCP_BIND_HOST`: listener address (default `127.0.0.1`).
- - `EDPAY_MCP_ALLOWED_HOSTS`: comma-separated allowed Host names.
- - `EDPAY_MCP_ALLOWED_ORIGINS`: comma-separated allowed browser Origin values; requests without Origin are allowed for server-side MCP clients.
- Customer credentials are never configured in server environment variables. Each HTTP request gets an isolated MCP server instance whose invoice actions use only that request's key headers.
- ## Tools
- - `edpay_get_key_setup`: unauthenticated key-creation and secure-storage instructions; never returns key values.
- - `edpay_list_operations`: list/filter operations from the versioned OpenAPI contract.
- - `edpay_get_operation`: inspect parameters, authentication, request bodies, and responses.
- - `edpay_generate_snippet`: generate server-side request examples.
- - `edpay_list_integration_guides`: list maintained SDK and plugin guides.
- - `edpay_create_invoice`: create a draft invoice only when explicitly requested.
- - `edpay_create_payment_link`: create/finalize an invoice into an active hosted payment link only when explicitly requested.
- - `edpay://openapi/v1`: expose the bundled OpenAPI document as an MCP resource.
- The MCP does not expose arbitrary HTTP calls or provider credentials. A draft invoice does not email or charge anyone. A payment link can accept payment after it is shared, but creating it does not charge a customer or send email.
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.