Skip to main content
Glama
inde-x

PaperSprocket MCP server

by inde-x
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to PaperSprocket MCP server

No user-submitted related servers found.

    Related Servers

    • AskAIs AI Receipt Generator

      MiniCodeTeam
      A
      license
      Not graded
      quality
      C
      maintenance
      Lets MCP clients create professional receipt PDFs, return structured receipt data, and check prepaid API credit through a remote endpoint.
      1
      MIT

    • bigapi

      BiGapi-2026
      A
      license
      A
      quality
      A
      maintenance
      Deterministic file operations for AI agents: 40 operations over plain HTTPS. PDF merge, split, redact, sanitize, OCR, Office and PDF to Markdown, RAG chunking, charts, QR codes, C2PA AI labelling. find_tool suggests the right one. $0.01 per operation, 100 free, no signup, credits never expire.
      5
      600 npm
      MIT

    • agentpay-gateway

      Rumblingb
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides a single MCP endpoint for 90+ tools across 42 backend servers (search, legal, domain, etc.) with per-call credit billing and a single API key.
      1
      MIT

    • DocumentKit

      504532934
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients to render any URL or raw HTML into PDF files or PNG/JPEG/WebP screenshots over MCP stdio or Streamable HTTP. Output stays in memory with SSRF protection, bounded concurrency, and configurable size and timeout limits.
      10 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one performs the core rendering action and the other retrieves account balance information. There is no overlap or ambiguity in when to use each tool.

    Naming Consistency5/5

    Both tools follow a consistent snake_case verb_noun pattern (render_html_to_pdf, check_balance). The convention is predictable and readable.

    Tool Count3/5

    With only two tools, the surface feels thin for a server that wraps a rendering API. While each tool earns its place, the set is minimal and may leave agents wanting more operations.

    Completeness4/5

    The core workflow of rendering HTML to PDF and checking balance is covered, but there are minor gaps such as retrieving render history, checking render status, or managing account details. These gaps are unlikely to block basic usage.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources