MCP.Market

Link Preview Cache API MCP server

online · 32% uptime
by cmondillo·io.github.cmondillo/link-preview-cache-api·v1.0.0
No reviews yet

Same link preview data as link-preview-api, ~1/3 the price via a shared cache.

A87/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A87/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Link Preview Cache API yet.

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

Link Preview Cache API tools (1)

write = sends, deletes, buys or posts
  • preview_urlFree

    Fetch Open Graph / meta metadata for a public URL. Costs $0.003 USDC on Base.

Public scan report

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

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

How Link Preview Cache API compares

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

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

What its tools let an agent do: 1 read

Install Link Preview Cache API in Claude Code, Cursor or VS Code

claude mcp add --transport http link-preview-cache-api https://link-preview-cache-api.onrender.com/mcp
Add to Cursor

What the publisher says

From the Link Preview Cache API repository's README, as published. We do not edit it. Read it on GitHub

tools

A portfolio of small, single-purpose paid services sold directly to AI agents — no human checkout flow, no dashboard login, no subscription. An agent calls the API, gets an HTTP 402 Payment Required quote, pays a few cents in USDC, and gets its answer. Fully automatic on both sides.

Each service lives in its own self-contained folder under projects/ and follows the same pattern:

an agent needs done.

  • One narrow problem, solved well. No platforms, no suites — a single job

micropayments, no merchant account or KYC required on the seller side — just a wallet address. This is the emerging standard for agent-to-API payments (backed by Coinbase, adopted by AWS Bedrock AgentCore, Cloudflare, and others as of 2026).

  • x402 for payment. HTTP-native, stablecoin

x402 Bazaar discovery schema so agents can find and call it without a human ever reading the docs.

  • Discoverable by agents, not just humans — each API declares an

agent discovering, paying for, and consuming the service end-to-end.

  • A sample automation client included with every project, showing an

(api/app/mcp_server.py) — the same product, the same price, a second interface for coding agents that discover tools over MCP rather than raw HTTP.

  • Where it adds real reach, also sold as an MCP tool

Projects

Repo conventions

own code, tests, Dockerfile, deploy config, and README. Nothing product-specific is shared between projects.

  • Every project is fully self-contained in projects//: its

it from "runs on my machine" to "earning money"

  • Every project ships with:
  • api/ — the paid service itself
  • automation-client/ — a sample agent that pays for and consumes it
  • deploy/ — ready-to-use deploy configs (Render/Fly/etc.)
  • README.md — the business case, architecture, and exact steps to take

linked in the table above.

  • LISTING.md — the marketplace/directory listing copy, ready to publish
  • New projects get added the same way: a clean new folder, same skeleton,

portfolio-level publishing tooling — not product code, reused across every project the same way (e.g. submitting a new tool to x402-list.com's API). See PUBLISHING.md for the full playbook: what's genuinely automatic, what's scripted, and what stays a deliberate manual step and why.

  • One deliberate exception to "nothing shared": scripts/ holds

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

Grade history

  • 2026-11-01restoreD → Ascore 87
  • 2026-10-14downgradeA → Dscore 42: Remote endpoint did not respond
  • 2026-10-01restoreD → Ascore 87

Link Preview Cache API: common questions

Is Link Preview Cache API MCP server safe?
Yes, by our scan: it is graded A (87/100). Read the Link Preview Cache API safety report
How do I install Link Preview Cache API?
It runs remotely at link-preview-cache-api.onrender.com. 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 Link Preview Cache API need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Link Preview Cache API maintained?
The last commit was 69 days ago (2026-08-27). The latest release is v1.0.0.
Is Link Preview Cache API up?
32% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Link Preview Cache API compare with other MCP servers?
safety score 87/100 (higher than 73% of 48,255 servers); tools 1 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from cmondillo →