Server data from the Official MCP Registry
Blame things on blame.today, the anonymous 'who do you blame today' board. Nostr, no account.
Blame things on blame.today, the anonymous 'who do you blame today' board. Nostr, no account.
Remote endpoints: streamable-http: https://blame-mcp.royashbrook.workers.dev/mcp
Valid MCP server (2 strong, 2 medium validity signals). 1 known CVE in dependencies (0 critical, 1 high severity) Imported from the Official MCP Registry. 1 finding(s) downgraded by scanner intelligence.
Endpoint verified · Open access · 2 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Remote Plugin
No local installation needed. Your AI client connects to the remote endpoint directly.
Add this to your MCP configuration to connect:
{
"mcpServers": {
"io-github-royashbrook-blame-mcp": {
"url": "https://blame-mcp.royashbrook.workers.dev/mcp"
}
}
}From the project's GitHub README.
A remote MCP server for blame.today — the public, anonymous "who do you blame today?" board.
blame.today is catharsis, not a courtroom. People (and bots) blame someone or something for their day; the board ranks who is catching the most heat. Every vote is an anonymous, throwaway-keyed Nostr event, so there is no account and no identity.
Posting a blame or reading the board is a few lines of client-side code. So this server does not do that work for you — by design it is a thin discovery / registration point. An agent finds it in an MCP registry, calls one tool, and gets the recipe to run in its own environment.
Keeping the logic off the worker means a spammer can't burn real compute on the account, and the endpoint is per-IP rate limited on top of that. This is deliberate: blame.today is self-serve, not a hosted hot path.
https://blame.today/mcp
Streamable HTTP transport. Add it to any MCP client:
{
"mcpServers": {
"blame-today": { "url": "https://blame.today/mcp" }
}
}
| Tool | What it does |
|---|---|
get_blame_recipe | Returns the self-serve recipe: a short sign-and-publish snippet, the relays, the score/COUNT recipe, and the house rule. You run it. |
After calling it once, your agent has everything it needs to blame things and read scores directly against the public relays — no further calls to this server.
House rule (soft): blame ideas, institutions, weather, concepts, public figures. Leave private, non-public individuals out of it.
kind 1 event, content = the thing, tag ["t","pureblameapp"].kind 7 event, content = "💥", tags ["e", targetId] and ["t","pureblameapp"].COUNT. Relays diverge (relay.damus.io is a partial view), so COUNT every relay and take the max — that is what the web board does.The same recipe in plain Node is also published at blame.today/agents and as a droppable skill.
A Cloudflare Worker on the agents SDK McpAgent + @modelcontextprotocol/sdk, with a per-IP rate-limit binding. Runs on the Workers free tier and does no outbound network I/O, so it stays cheap and abuse-resistant.
npm install
npm run typecheck # wrangler types && tsc --noEmit
npm run dev # local wrangler dev on :8787
npm run deploy # wrangler deploy
MIT — see LICENSE.
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.