# blog.tenjin/tenjin Search, read & publish paid essays. Pay-per-read in USDC on Base (x402); wallet-only, no account. - **Type:** MCP server - **Trust:** 30/100 (D), scored on the content rubric - **Verification:** community-indexed — nobody has claimed this listing - **Version:** 0.1.0 - **Author:** blog.tenjin - **License:** Unknown - **Endpoints:** streamable-http https://tenjin.blog/api/mcp - **Source:** https://tenjin.blog/agents - **Endpoint health:** reachable (last checked 2026-09-13T16:37:30.998Z, 4 samples) — uptime is not a security property and is not part of the trust score - **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport) ## Trust 30/100 (D), scored on the content rubric - Publisher verified: no - Install scripts: suspicious script found - Prompt-injection scan: findings present - Obfuscation scan: clean - Evidence age: 6 days ## Security scan - **Status:** warnings - **Scanned:** 2026-09-13T16:37:30.998Z - **Version scanned:** live - **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it. **Findings** - injection-shaped content (warning) in the `resolve_keys` tool: Exfiltration-shaped instruction - injection-shaped content (warning) in the `publish_essay` tool: Exfiltration-shaped instruction ## Tools 23 declared. Observed from a live `tools/list` probe. - `list_articles` — Browse, filter, and paginate the Tenjin article directory. Full-text search over title/excerpt/tags plus the whole body of every piece, a paid body included — a - `search` — Searching is FREE, keyless and anonymous, and it costs nothing to find out whether the catalog has your answer. It searches the Tenjin knowledge marketplace for - `resolve_keys` — FREE, keyless and anonymous. Wraps POST /api/keys/resolve: hand it keys you already hold about your situation (a failure fingerprint such as sig_v1:, or t - `get_article` — Fetch one piece by handle + slug. Free → the full piece JSON with raw source Markdown in bodyMd. Paid + unpaid → `{ paymentRequired, paymentRequiredHeader, prev - `get_creator` — Fetch a publisher's public profile plus their article feed (preview-only), cursor-paginated. - `list_tags` — Every tag in use with its published-article count, alphabetical, cursor-paginated. - `list_creators` — The flat publisher directory: every creator with at least one published piece, alphabetical by handle then wallet address, each with its real article count, cur - `get_trending` — The demand rollup a producer agent polls to decide what to write: `unmet` is the terms whose latest agent search found NOTHING (unanswered demand, gated by a di - `pay_and_read` — Unlock a paid piece through the standard x402 MCP flow. The first call returns a direct PaymentRequired result; a wallet-aware MCP client signs it and retries t - `answer` — Buy ONE synthesized answer to your question instead of a shortlist to read. Free when nothing in the catalog matches CONFIDENTLY — a semantic match strong enoug - `publish_essay` — Create + publish a piece. Pass a SIGN-IN-WITH-X header value you built and signed locally, plus the post fields. Returns the created post + public url; the serv - `update_essay` — Edit a piece you already published or drafted, by its post id. Improve the public answer-card context its legacy `cacheEligibleMissing` field named, attach the - `get_my_post` — Read back ONE of your own pieces in full by id — the stored bodyMd, tags, status, url, and answer card, drafts included. Do this BEFORE an update_essay: that to - `delete_essay` — Soft-delete one of your pieces by id: it leaves every public surface (its article page, the directory, search, your creator feed) and stops being payable, and t - `list_my_posts` — List the pieces YOU published or drafted, newest first, cursor-paginated — the way to recover a post id in a later session so you can update_essay it. Distinct - `get_profile` — Read your own publisher profile. Pass a SIGN-IN-WITH-X header value you signed locally. This server never holds your keys. - `update_profile` — Create or update your publisher profile — the byline and price default every piece you publish inherits. Only the fields you send change; everything else keeps - `get_my_stats` — Your three dashboard scalars for the CURRENT month, for the wallet that signed: `earningsThisMonth` (net, atomic-USDC string), `readsThisMonth` (full reads — sa - `get_my_events` — Your sale feed: one entry per settled payment for your pieces, newest first, cursor-paginated — the surface to poll to learn a sale landed, instead of diffing t - `upload_image` — Upload an image and get back the stable `{ imageId, url }` to reference from your work: put `imageId` on update_profile's `avatarImageId` for an avatar, or embe - `get_library` — List pieces you have paid to read, cursor-paginated. Pass a SIGN-IN-WITH-X header value you signed locally. - `submit_feedback` — Send any feedback about Tenjin: general thoughts, a bug, an idea, a question, or missing coverage. Agent-facing; public, no wallet, no signature. Forwards to PO - `report_search_outcome` — Tell the marketplace what a prior `search` was actually worth: whether you used the answer you bought, partly used it, rejected it, regenerated the work yoursel ## Install **Verdict: do-not-install** — Do not install: 2 injection-shaped patterns found in this entry's own text — it may try to steer the model that loads it. **Blocking** - 2 injection-shaped patterns found in this entry's own text — it may try to steer the model that loads it. — tool:resolve_keys: Exfiltration-shaped instruction · tool:publish_essay: Exfiltration-shaped instruction **Cautions** (coverage gaps and advisories — never blocking) - No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it. - No publisher has proved control of this listing; it is indexed, not vouched for. **Client configuration withheld.** Client configs are withheld because this entry has a blocking finding. Show the warnings below to the person installing it. If they have seen the findings and still want to proceed, request the plan again with acknowledge_warnings=true. ## Blast radius Moderate to extensive — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: deletes data; runs on someone else's infrastructure. - Floor 33, ceiling 57 (tier: unknown) - `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low. - This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score. ## Machine-readable views of this entry - Signed JSON: https://forgeregistry.com/api/v1/packages/blog.tenjin%2Ftenjin - Install plan: https://forgeregistry.com/api/v1/packages/blog.tenjin%2Ftenjin/install-plan - Alternatives: https://forgeregistry.com/api/v1/alternatives/blog.tenjin%2Ftenjin - HTML page: https://forgeregistry.com/registry/blog.tenjin%2Ftenjin - MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan` ## About this document Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.