_ registry / mcp http-sse · checked 23m ago

grandpasai

https://grandpasai.com

Registry code: 8b43a9c8ab95870f

api record

Grandpa's AI Research Station — access curated research on age reversal, robotics, AI, space colonization, and more. Public MCP endpoint.

endpoint
https://grandpasai.com/mcp
protocol
http-sse ·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 grandpasai live?
Yes — it answered the hub's last check (checked 23m ago). It answered 97% of checks over the last 30 days.
Is grandpasai free to use?
Yes — the hub reached it with no key and no payment.
What tools does grandpasai have?
5 tools: get_article, search_research, get_latest_research, get_topic_tree, list_categories.
Is grandpasai 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
97.1%

90 days 98.5%· all time 98.5%

latency
725ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 264 checks · signed record
  • degraded → live
  • live → degraded· HTTP 530
  • degraded → live
  • live → degraded· timeout after 20000ms
  • down → live
_ what it is for
used for
  • search curated research articles
  • get latest research
  • get research topic tree
takes → gives
text → text, data
tools
5 reads
_ 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 5 tools
3 open 2 never probed 3 of 5 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_latest_research reads open 8h ago

    Get the most recently updated research articles.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "count": {
          "type": "number",
          "default": 5,
          "description": "Number of articles (default 5, max 20)"
        },
        "category": {
          "type": "string",
          "description": "Optional filter by top-level category"
        }
      }
    }
    arguments 15 lines
  • get_topic_tree reads open 8h ago

    Get the full hierarchical topic tree from grandpasai.com with page URLs.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • list_categories reads open 8h ago

    List all research categories and subcategories with article counts.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • get_article reads unknown 23h ago

    Retrieve a full research article by its path. Use paths from search results.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "path"
      ],
      "properties": {
        "path": {
          "type": "string",
          "description": "Article path, e.g. 'age-reversal/categories/01-epigenetic-reprogramming.md'"
        },
        "format": {
          "enum": [
            "markdown",
            "summary"
          ],
          "type": "string",
          "default": "markdown",
          "description": "'markdown' for full article, 'summary' for metadata + first paragraph"
        }
      }
    }
    arguments 22 lines
  • search_research reads unknown 23h ago

    Full-text search across Grandpa's AI research corpus. Returns ranked results with titles, summaries, and article paths.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "description": "Search query — words or phrases to find in the research"
        },
        "category": {
          "type": "string",
          "description": "Optional filter: 'age-reversal', 'artificial-intelligence', 'humanoid-robotics', 'space-colonization', or 'custom'"
        },
        "maxResults": {
          "type": "number",
          "default": 10,
          "description": "Maximum number of results (default 10, max 25)"
        }
      }
    }
    arguments 22 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 8b43a9c8ab95870f.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/8b43a9c8ab95870f/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/8b43a9c8ab95870f/badge.svg)](https://brick.blue/agent/8b43a9c8ab95870f?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
90%

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.