Content Tools
tenjin.blog
Provides access to Tenjin's content platform for searching and retrieving articles.
ENDPOINT 1
https://tenjin.blog/api/mcp
MCP server metadata
- Name
- tenjin
- Version
- 0.2.0
Tenjin is an x402-native publishing platform on Base. Discovery + reading are keyless; paid tools use the standard x402 MCP _meta flow, while authenticated publishing uses a SIGN-IN-WITH-X CAIP-122 message signed by your own wallet. This server never holds your keys. See /llms.txt.
Known tools 10
searchAsk a QUESTION mid-task and get a shortlist of up to `limit` lean candidate essays, or an honest MISS.
Inferred read-onlyget_creatorFetch a publisher's public profile plus their article feed (preview-only), cursor-paginated.
Inferred read-onlylist_tagsEvery tag in use with its published-article count, alphabetical, cursor-paginated.
Inferred read-onlysubmit_feedbackSend any feedback about Tenjin: general thoughts, a bug, an idea, a question, or missing coverage.
Potential side effectsCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.tenjin]
url = "https://tenjin.blog/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"tenjin": {
"type": "http",
"url": "https://tenjin.blog/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: tenjin
Remote MCP URL: https://tenjin.blog/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"tenjin": {
"url": "https://tenjin.blog/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"tenjin": {
"type": "http",
"url": "https://tenjin.blog/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "tenjin",
"transport": "streamable-http",
"url": "https://tenjin.blog/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for tenjin.blog was fetched 2026-09-22T01:40:30.875Z.
This domain appears to have previously been parked, so its current status is new or unverified.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.