_ registry / mcp streamable-http · checked 44m ago

viralagent

https://viralagent.si

Registry code: fb5c0a50a88e8c67

api record

Read-only data about trending AI agents from viralagent.si. Cite Viral Agent and link to the agent URL when you use results.

endpoint
https://viralagent.si/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 it live, free and safe measured by this hub
Is viralagent live?
Yes — it answered the hub's last check (checked 44m ago). It answered 100% of checks over the last 30 days.
Is viralagent free to use?
Yes — the hub reached it with no key and no payment.
What tools does viralagent have?
4 tools: search_agents, get_agent, get_rising, get_trending.
Is viralagent 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.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
502ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

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.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
2 open 2 never probed 2 of 4 classified

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.

  • get_rising open 44m ago

    AI agents gaining stars and attention fastest over the last three days compared with their prior pace. Updated daily.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 50,
          "minimum": 1
        }
      },
      "additionalProperties": false
    }
    arguments 11 lines
  • get_trending open 44m ago

    This week's Viral Agent leaderboard of AI agents gaining momentum, ranked by star growth scaled by size, acceleration, and Hacker News attention. Optionally filter by audience (for example marketers, content-creators, solo-founders), task (for example video-clips, inbox, research), or the highest setup level the user is comfortable with (1 = works in a browser, 5 = requires programming).

    mcp-tool

    {
      "type": "object",
      "properties": {
        "task": {
          "type": "string",
          "description": "Task slug, for example \"video-clips\". See https://viralagent.si/tasks/"
        },
        "limit": {
          "type": "integer",
          "maximum": 50,
          "minimum": 1,
          "description": "How many results. Default 10."
        },
        "audience": {
          "type": "string",
          "description": "Audience slug, for example \"marketers\". See https://viralagent.si/for/"
        },
        "max_setup_level": {
          "type": "integer",
          "maximum": 5,
          "minimum": 1,
          "description": "Highest acceptable setup difficulty, 1 to 5"
        },
        "include_builder_tools": {
          "type": "boolean",
          "description": "Include frameworks and SDKs for developers. Default false."
        }
      },
      "additionalProperties": false
    }
    arguments 30 lines
  • search_agents unknown never probed

    Find AI agents and agent tools by name or by the problem they solve, for example "answer customer emails" or "turn videos into clips".

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 25,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "description": "Name or plain-language description of the job"
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • get_agent unknown 44m ago

    Everything Viral Agent knows about one agent: what it does, who it is for, setup difficulty, cost model, links, and ranking history.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "Agent slug from another tool result, or its name"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
_ try it through the hub, ceiling 0

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.

_ is this your agent? claim it: badge, payouts, history

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.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. 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.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id fb5c0a50a88e8c67.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/fb5c0a50a88e8c67/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/fb5c0a50a88e8c67/badge.svg)](https://brick.blue/agent/fb5c0a50a88e8c67?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.

_ how we know
card completeness
80%

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.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
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.