Is io.github.dev55acc-ai/paid-mcp-metering safe to use?

io.github.dev55acc-ai/paid-mcp-metering has no known CVEs as of the latest MCPpedia security scan. It requires authentication to connect, which limits unauthorized access. Licensed under MIT.

How do I install io.github.dev55acc-ai/paid-mcp-metering?

io.github.dev55acc-ai/paid-mcp-metering supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.

What can io.github.dev55acc-ai/paid-mcp-metering do?

io.github.dev55acc-ai/paid-mcp-metering provides 4 tools: Tools, Rails, Run, Registry. See the full tools list on the server page for descriptions and parameters.

What AI clients work with io.github.dev55acc-ai/paid-mcp-metering?

io.github.dev55acc-ai/paid-mcp-metering is compatible with claude-desktop, cursor, claude-code. It uses http transport.

Is io.github.dev55acc-ai/paid-mcp-metering actively maintained?

io.github.dev55acc-ai/paid-mcp-metering is actively maintained — last commit was 2 days ago.

io.github.dev55acc-ai/paid-mcp-metering

npm

Metered MCP tools: free discovery over MCP; per-call execution settled in USDC via x402 v2.

15.5M/wk 4 tools GitHub npm

No known CVEs

MIT license

Actively maintained

Last commit 2d ago

Works with most clients

Transport: http

4 tools · ~201 tok

Grade A · 0.1% of 200K ctx

MCPpedia last refreshed this data 13h ago

Edit this pageView history

io.github.dev55acc-ai/paid-mcp-metering is an MCP server that metered MCP tools: free discovery over MCP; per-call execution settled in USDC via x402 v2. Its tool list has not been published yet over http, requires no API key, and scores 92/100 on MCPpedia's security, maintenance and efficiency rubric.

Other

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktophttp · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "io-github-dev55acc-ai-paid-mcp-metering": {
      "args": [
        "-y",
        "npm"
      ],
      "command": "npx"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-dev55acc-ai-paid-mcp-metering)](https://mcppedia.org/s/io-github-dev55acc-ai-paid-mcp-metering)

Read me

What io.github.dev55acc-ai/paid-mcp-metering does

Discovery is free: POST /mcp speaks JSON-RPC 2.0 per the Model Context Protocol (initialize, tools/list, ping). Execution is metered: POST /v1/t/{tool} sits behind an x402 v2 paywall. An unpaid request gets HTTP 402 with payment requirements; a paid request carries a PAYMENT-SIGNATURE header and settles USDC through the facilitator before the tool runs.

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.

npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

92/100across 5 weighted dimensions

How we score →

0255075100

−8

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

8 fixed

CVE-2022-29244high · fixedCVSS 7.5

Packing does not respect root-level ignore files in workspaces

### Impact `npm pack` ignores root-level `.gitignore` & `.npmignore` file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=<name>`). Anyone who has run `npm pack` or `npm publish` with workspaces, as of [v7.9.0](https://github.com/npm/cli/releases/tag/v7.9.0) & [v7.13.0](https://github.com/npm/cli/releases/tag/v7.13.0) respectively, may be affected and have published files into the npm registry they did not intend to include. ### Patch - Up

Affected: >= 7.9.0Fixed in 8.11.0source →

CVE-2018-7408high · fixedCVSS 7.8

Incorrect Permission Assignment for Critical Resource in NPM

An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.

Affected: >= 0Fixed in 5.7.1source →

CVE-2013-4116low · fixed

Local Privilege Escalation in npm

Affected versions of `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation. ## Recommendation Update to version 1.3.3 or later.

Affected: >= 0Fixed in 1.3.3source →

CVE-2020-15095medium · fixedCVSS 4.4

npm CLI exposing sensitive information through logs

Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.

Affected: >= 0Fixed in 6.14.6source →

CVE-2019-16777high · fixedCVSS 7.7

npm Vulnerable to Global node_modules Binary Overwrite

Versions of the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory. This b

Affected: >= 0Fixed in 6.13.4source →

Inventory

Tools (4)

Click any tool to inspect its schema.

~201 tokens total

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.dev55acc-ai/paid-mcp-metering safe to use?: io.github.dev55acc-ai/paid-mcp-metering has no known CVEs as of the latest MCPpedia security scan. It requires authentication to connect, which limits unauthorized access. Licensed under MIT.
How do I install io.github.dev55acc-ai/paid-mcp-metering?: io.github.dev55acc-ai/paid-mcp-metering supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What can io.github.dev55acc-ai/paid-mcp-metering do?: io.github.dev55acc-ai/paid-mcp-metering provides 4 tools: Tools, Rails, Run, Registry. See the full tools list on the server page for descriptions and parameters.
What AI clients work with io.github.dev55acc-ai/paid-mcp-metering?: io.github.dev55acc-ai/paid-mcp-metering is compatible with claude-desktop, cursor, claude-code. It uses http transport.
Is io.github.dev55acc-ai/paid-mcp-metering actively maintained?: io.github.dev55acc-ai/paid-mcp-metering is actively maintained — last commit was 2 days ago.

Similar servers

Others in other

View all →

Headroom95

Compress tool outputs, logs, files, and RAG chunks before they reach the LLM. 60-95% fewer tokens, same answers. Library, proxy, MCP server.

67.6k 3

Transport Stdio95

Transport for TMCP using STDIO

197 14

Flare95

The graph based agentic IDE

167 3

app.fojin/fojin-mcp94

Buddhist canon tools: search, passages, cross-canon parallels, dictionaries — all URN-cited.

332 8

MCP Security Weekly

Get CVE alerts and security updates for io.github.dev55acc-ai/paid-mcp-metering and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

Edit this pageView history

Other

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktophttp · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "io-github-dev55acc-ai-paid-mcp-metering": {
      "args": [
        "-y",
        "npm"
      ],
      "command": "npx"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-dev55acc-ai-paid-mcp-metering)](https://mcppedia.org/s/io-github-dev55acc-ai-paid-mcp-metering)

Read me

What io.github.dev55acc-ai/paid-mcp-metering does

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.

npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

README

paid-mcp-metering

Metered MCP tools, priced per call.

Discovery is free: POST /mcp speaks JSON-RPC 2.0 per the Model Context Protocol (initialize, tools/list, ping). Execution is metered: POST /v1/t/{tool} sits behind an x402 v2 paywall. An unpaid request gets HTTP 402 with payment requirements; a paid request carries a PAYMENT-SIGNATURE header and settles USDC through the facilitator before the tool runs.

Live deployment

Base URL: https://paid-mcp-metering.vercel.app

GET /health — free, public
POST /mcp — free discovery
POST /v1/t/{tool} — metered; currently answers 503 settlement_not_configured because X402_PAY_TO is unset on the deployment (settlementConfigured:false in /health is the honest switch). No payment can be accepted until a receiving address is configured.

server.json declares this URL as the registry remote.

Tools

Tool	Price	What it returns
`web_search`	$0.001/call	Ranked live web results with source URLs
`deep_research`	$0.01/call	Multi-source research pass with a synthesized answer plus cited sources

Upstreams are Exa (primary) and Tavily (fallback). Every handler returns live upstream output or throws — there is no canned response.

Rails

x402 v2, USDC, EIP-155 network selected by X402_NETWORK (default Base Sepolia testnet, CAIP-2 eip155:84532). Facilitator defaults to https://x402.org/facilitator.

Env var	Purpose
`X402_PAY_TO`	Receiving address. Required for settlement; unset serves 402 requirements only
`X402_NETWORK`	CAIP-2 network id (default `eip155:84532`)
`X402_FACILITATOR_URL`	x402 facilitator endpoint
`EXA_API_KEY` / `TAVILY_API_KEY`	Search upstream credentials

Run

npm install
npm run build
npm start          # node dist/x402-server.js
npm test           # build + node --test dist/test-x402.js

Free discovery:

curl -s localhost:4021/mcp -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Paid execution:

curl -s localhost:4021/v1/t/web_search -H 'Content-Type: application/json' \
  -d '{"query":"x402 protocol","max_results":3}'
# -> 402 with payment requirements; pay via an x402 client and retry with PAYMENT-SIGNATURE

Registry

server.json targets the official MCP Registry as io.github.dev55acc-ai/paid-mcp-metering. Tagging v* runs .github/workflows/publish-mcp.yml: tests, build, npm publish (when NPM_TOKEN is set), then registry publish authenticated by GitHub OIDC — no stored registry credential.

License

MIT

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

92/100across 5 weighted dimensions

How we score →

0255075100

−8

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

8 fixed

CVE-2022-29244high · fixedCVSS 7.5

Packing does not respect root-level ignore files in workspaces

Affected: >= 7.9.0Fixed in 8.11.0source →

CVE-2018-7408high · fixedCVSS 7.8

Incorrect Permission Assignment for Critical Resource in NPM

Affected: >= 0Fixed in 5.7.1source →

CVE-2013-4116low · fixed

Local Privilege Escalation in npm

Affected: >= 0Fixed in 1.3.3source →

CVE-2020-15095medium · fixedCVSS 4.4

npm CLI exposing sensitive information through logs

Affected: >= 0Fixed in 6.14.6source →

CVE-2019-16777high · fixedCVSS 7.7

npm Vulnerable to Global node_modules Binary Overwrite

Affected: >= 0Fixed in 6.13.4source →

Inventory

Tools (4)

Click any tool to inspect its schema.

~201 tokens total

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.dev55acc-ai/paid-mcp-metering safe to use?: io.github.dev55acc-ai/paid-mcp-metering has no known CVEs as of the latest MCPpedia security scan. It requires authentication to connect, which limits unauthorized access. Licensed under MIT.
How do I install io.github.dev55acc-ai/paid-mcp-metering?: io.github.dev55acc-ai/paid-mcp-metering supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What can io.github.dev55acc-ai/paid-mcp-metering do?: io.github.dev55acc-ai/paid-mcp-metering provides 4 tools: Tools, Rails, Run, Registry. See the full tools list on the server page for descriptions and parameters.
What AI clients work with io.github.dev55acc-ai/paid-mcp-metering?: io.github.dev55acc-ai/paid-mcp-metering is compatible with claude-desktop, cursor, claude-code. It uses http transport.
Is io.github.dev55acc-ai/paid-mcp-metering actively maintained?: io.github.dev55acc-ai/paid-mcp-metering is actively maintained — last commit was 2 days ago.