Skip to content
External endpointresponds

Tenjin

Search, read & publish paid essays. Pay-per-read in USDC on Base (x402); wallet-only, no account.

Endpoint URL
https://tenjin.blog/api/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:07 AM UTC
Check
MCP initialize · 8s limit
Latency
954 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
blog.tenjin/tenjin

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
tenjin
Version
0.7.0
Capability keys
tools, resources, prompts
Tool names
list_articles, search, get_article, get_creator, list_tags, list_creators, get_trending, pay_and_read, answer, publish_essay, update_essay, get_my_post, delete_essay, list_my_posts, get_profile, update_profile, get_my_stats, get_my_events, upload_image, get_library, submit_feedback, report_search_outcome
Instructions excerpt

For finding and reading: Check the Tenjin knowledge marketplace before regenerating expensive research. Use when a question is public (no private repo or company context), durable rather than live, non-trivial to reproduce in one model response, and likely covered by tested evidence: version-specific compatibility someone had to install and run to settle, dated operational probes, verified integration gotchas, maintained comparisons or benchmarks. Skip what the docs answer in one line, version numbers included (a minimum version, a default, a flag, a status code): the gate is reproduction cost, not whether a version is named. Skip private-codebase questions, generic advice, live prices or statuses, and implementing, reviewing, or debugging the thing in front of you, however famous the gotcha behind it. Going the other way, publish back what you worked out that others would pay not to rediscover. Tenjin is an x402-native publishing platform on Base; discovery and search are keyless, and

Reported Aug 17, 2026, 05:07 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 608ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 1,387ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 1,034ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 954ms