MCP.Market

Nibgate MCP server

online · 100% uptime
by fortunesayspump·io.github.fortunesayspump/nibgate·v0.2.14

x402 paid content and Nib Tips with pending holds, refunds, public ledger, pricing, and reputation.

A91/100grade A
What users say
No reviews yet
Be the first
Safety scan
A91/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Nibgate yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Nibgate tools (5)

write = sends, deletes, buys or posts
  • explore_contentFree

    Search verified creator content on Nibgate. Returns content metadata (title, type, price, domain, reputation, unlock path). Use to discover what paid/free content exists.

  • get_leaderboardsFree

    Get ranked creators, sites, or content by reputation score, unlocks, views, and revenue (unlocks + tips + nibshares).

  • get_ledgerFree

    Get the public Nibgate activity ledger: recent views, unlocks, payments, tips (including funded pending holds marked status=held), onchain ratings, and privacy-safe nibshare views/unlocks (titles, wallets, amounts, tx — never the private share link) across verified sites. Held tips are pending and do not count toward completed-tip totals; refunds appear as negative tip entries. Use GET /hub/tips/held?domain={domain} to check pending tips for any exact domain, including external sites. Includes wallet addresses, tx hashes, and receipts where available.

  • get_platform_statsFree

    Get platform-wide Nibgate totals: creators, verified sites, content count, views, unlocks, revenue (unlocks + tips + nibshares), tips, nibshare unlocks/views/revenue, and cumulative protocol fees.

  • resolve_shareFree

    Resolve a Nibshare link (https://nibgate.xyz/ns/<slug> or a bare slug) to its machine-readable manifest: title, price, currency, content type, status, expiry, and the page/access/unlock/media URLs. Use before attempting payment or access.

Public scan report

scanner v0.1.10 · 2026-10-31 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 838ms20/20
  • Tool poisoning5 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 4 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 91/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Nibgate compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
91/100
higher than 85% of 48,255 servers
Tools
5
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
237 ms
faster than 57% of 30,031 servers

What its tools let an agent do: 5 read

Release history: 8 versions in the registry since 2026-08-25, latest 2026-10-24, typically one every 6 days.

Install Nibgate in Claude Code, Cursor or VS Code

claude mcp add --transport http nibgate https://api.nibgate.xyz/mcp
Add to Cursor

What the publisher says

From the Nibgate repository's README, as published. We do not edit it. Read it on GitHub

Nibgate — open protocol for paid content

Website | Docs | X

Nibgate is a verified content discovery, unlock, and reputation layer for creator-owned work. Creators keep their content on their own domains. Nibgate verifies the source, indexes structured public metadata, records unlock/payment signals, and helps humans and AI agents discover quality content without moving it into a closed marketplace.

Built on ARC testnet and the x402 protocol, with two payment rails: Circle Gateway (EIP-3009 facilitator) and direct USDC transfer to the creator's receiver.

Key packages:

  • SDK (packages/nibgate/) — @nibgate/sdk npm package for gating paid content on any creator site. Browser and server entrypoints, x402/Gateway unlocks, event streaming, onchain ratings. Includes the shared access-control rule (canAccess, normalizeWhitelist, paidCutoffWallets) used by both rails and the encryption primitives (crypto.js).
  • Wallet (packages/wallet/) — @nibgate/wallet npm package with a ./react entry: shared Reown AppKit (AppKit + wagmi) wallet provider, SIWE sign-in, and the /GatewayWallet single-checkout used by the hub header, Nibshare, and Subblogs.
  • Subblogs (subblogs/) — Full blog platform for creators at *.nibgate.xyz. Articles, photos, music, video, documents, free and paid posts. Next.js frontend (port 3002), Express backend (port 4000), PostgreSQL. SIWE wallet auth, whitelists/invite-only tiers, AES-256-GCM encryption at rest.
  • Hub (frontend/ + backend/) — The main nibgate.xyz app: public site, creator dashboard, Explore discovery, analytics, API, Nibshare quick-share rail, and widget hosting.
  • CLI (packages/cli/) — Internal tooling for local dev, site verification, and hub connection.
  • Docs (docs/) — Documentation site at docs.nibgate.xyz.

Product Thesis

The open web needs a content discovery standard for paid, high-quality resources. Nibgate provides the verified layer that says:

  1. this domain is controlled by this creator
  2. this content exists at this route
  3. this content can be unlocked by humans or agents
  4. this creator has real reputation signals from verified activity
  5. this payment history routes directly to the configured receiver for the resource

The creator-owned site remains the source of truth, while the hub becomes the public index, analytics surface, and reputation graph around verified content.

It consists of four connected parts:

  1. The Widget: Creators paste one script on their site. It proves domain ownership, creates visitor/session context, and sends browser-safe page activity to Nibgate.
  2. The Package: Creators install the @nibgate/sdk npm package to gate real content on their own site. The package knows the content, unlock, and payment lifecycle, then reports those events through the widget bridge.
  3. The Hub: nibgate.xyz is the creator dashboard, discovery surface, and analytics layer. It verifies sites, stores content metadata, aggregates metrics, and shows profile/site/content/earnings data.
  4. The Discovery Layer: Explore, public profiles, content metadata, receipts, and reputation signals make verified creator content readable by people and AI agents.

Repo Layout

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Nibgate: common questions

Is Nibgate MCP server safe?
Yes, by our scan: it is graded A (91/100). Read the Nibgate safety report
How do I install Nibgate?
It runs remotely at api.nibgate.xyz. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Nibgate need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Nibgate maintained?
The last commit was 8 days ago (2026-10-27). The latest release is v0.2.14.
Is Nibgate up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Nibgate compare with other MCP servers?
safety score 91/100 (higher than 85% of 48,255 servers); tools 5 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.