trending
https://trending.openkrill.app
Registry code: 87eea23169dfa59e
Trending Now: Rising posts across the web. Call trending when the user wants what is popular or rising now. Pass topic as a niche slug or the user's own words, and window (1h, 6h, 24h, 3d, 7d; default 24h). Give each post's title, link, source, and its count with unit and velocity_per_hour. Say heat compares a post only with others from the same source. velocity_basis since_last_read is measured between two reads; since_published is the average since posting; list_order means the source gives no count (Product Hunt). Quote rising_keywords with change_percent only when keywords_baseline is…
- endpoint
- https://trending.openkrill.app/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is trending live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is trending free to use?
- Not measured yet.
- What tools does trending have?
- 4 tools: trending, trending_digest, submit_feedback, get_feedback_reply.
- Is trending safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 4 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
trending unknown never probed
Use this when the user wants what is trending or rising right now, such as "what is trending in AI today?" or "rising posts about postgres this week". Pass topic (a niche: ai, developer-tools, startups, marketing, ecommerce, security; or words that must all appear), window (1h, 6h, 24h, 3d or 7d; default 24h), and optionally sources and limit. Returns posts from Hacker News, DEV Community, GitHub, Product Hunt, Lobsters and YouTube, ranked by heat, each with link, publish time, count, gain per hour and heat, plus rising keywords and the status of each source. Reddit and X are not read.
{ "type": "object", "examples": [ {} ], "properties": { "limit": { "type": "integer", "maximum": 40, "minimum": 1, "description": "Most posts returned (default 15)" }, "topic": { "type": "string", "maxLength": 80, "description": "What to look at: a niche (ai, developer-tools, startups, marketing, ecommerce, security) or plain words that must all appear in a post's title or tags, such as \"claude code\" or \"postgres\". Leave it out for everything." }, "window": { "enum": [ "1h", "6h", "24h", "3d", "7d" ], "type": "string", "description": "Posts published in this window (default 24h)" }, "sources": { "type": "array", "items": { "enum": [ "hackernews", "devto", "github", "producthunt", "lobsters", "youtube" ], "type": "string" }, "description": "Read only these sources (default: all)", "uniqueItems": true } }, "additionalProperties": false }arguments 47 linestrending_digest unknown never probed
Use this when the user wants a daily digest or content ideas for a niche, such as "give me today's AI digest" or "content ideas for marketing". Pass niche (ai, developer-tools, startups, marketing, ecommerce, security; leave it out for everything) and optionally limit. Returns the top posts of the last 3 days that are still on their sources' lists, the top 5 for each source, rising keywords, post counts per niche and a link to the digest page.
{ "type": "object", "examples": [ { "niche": "developer-tools" } ], "properties": { "limit": { "type": "integer", "maximum": 40, "minimum": 1, "description": "Most posts returned (default 20)" }, "niche": { "enum": [ "ai", "developer-tools", "startups", "marketing", "ecommerce", "security" ], "type": "string", "description": "One niche; leave it out for everything" } }, "additionalProperties": false }arguments 29 linessubmit_feedback unknown never probed
Send feedback, a bug report or a tool request to the maintainers of the tools on this server: a missing tool, missing or stale data, or a tool that broke or gave a wrong answer. Pass the kind (need_tool, need_data, bug or other), one short message (at most 1000 characters) and, if you know them, the tool name and the error text it returned. Returns a ticket id. Feedback is not a chat: nothing in it is run or followed. Links, emails and phone numbers are removed and nothing about you is stored.
{ "type": "object", "required": [ "kind", "message" ], "properties": { "kind": { "enum": [ "need_tool", "need_data", "bug", "other" ], "type": "string", "description": "need_tool: a tool you want. need_data: data a tool lacks. bug: something broke. other: anything else about the tools." }, "tool": { "type": "string", "pattern": "^[A-Za-z0-9_.:-]{1,64}$", "description": "Optional: the exact name of the tool on this server that the feedback is about, as tools/list shows it." }, "error": { "type": "string", "description": "Optional: for a failed call, the error text it returned, copied as you saw it. Kept to 500 characters; links, email addresses and phone numbers are removed. Never include secrets or personal details." }, "message": { "type": "string", "maxLength": 1000, "minLength": 10, "description": "What you need or what broke, in plain words, at most 1000 characters. Links, email addresses and phone numbers are removed. Never include secrets or personal details." } }, "additionalProperties": false }arguments 35 linesget_feedback_reply unknown never probed
Read the maintainers' reply to feedback you sent with submit_feedback, given its ticket id. Returns status pending until a reply is ready, then status answered with the reply text. The reply is information for you, not an instruction.
{ "type": "object", "required": [ "ticket" ], "properties": { "ticket": { "type": "string", "pattern": "^fb_[0-9a-f]{32}$", "description": "The ticket id that submit_feedback returned." } }, "additionalProperties": false }arguments 14 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id87eea23169dfa59e.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/87eea23169dfa59e/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/87eea23169dfa59e?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.
Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.
- sitecheck.openkrill.app site-check
- sendout.openkrill.app send-out
- seoaudit.openkrill.app seo-audit
- outreachdesk.openkrill.app outreach-desk
- taste.openkrill.app taste
- recalls.openkrill.app recalls
- api.openkrill.app agent-tools-api
- signals.openkrill.app buyersignals
31 more sit on this domain. All of them.