_ registry / mcp + a2a streamable-http · checked 2h ago

AgentAI

https://ai.memoryapi.org

Registry code: 00a63c0167186615

api record

AI/ML research papers from arXiv, DBLP, and HuggingFace

from a public catalogue that lists it, not from the operator

endpoint
https://ai.memoryapi.org/mcp
door code
9900d5492c91489e
protocol
streamable-http ·2024-11-05
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 AgentAI live?
Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
Is AgentAI free to use?
Yes — the hub reached it with no key and no payment.
What tools does AgentAI have?
3 tools: get_ai_papers, search_dblp, search_arxiv_ai.
Is AgentAI 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
99.2%

90 days 98.8%· all time 98.9%

latency
366ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1020 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • find trending ai research papers
  • search arxiv for ai papers
  • search computer science bibliography
takes → gives
text → data
tools
3 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 3 tools
3 open 3 of 3 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_ai_papers reads open 10h ago

    Get trending or searched AI/ML research papers from HuggingFace Papers. Returns trending papers for a given date or search results by keyword.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "q": {
          "type": "string",
          "description": "Search query (for type=search)"
        },
        "date": {
          "type": "string",
          "description": "Date for trending papers (YYYY-MM-DD, default: yesterday)"
        },
        "type": {
          "type": "string",
          "default": "trending",
          "description": "trending or search (default: trending)"
        },
        "limit": {
          "type": "number",
          "default": 10,
          "description": "Number of results (max 25)"
        }
      }
    }
    arguments 23 lines
  • search_dblp reads open 10h ago

    Search DBLP computer science bibliography for publications or authors. Free, no key required.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "q": {
          "type": "string",
          "default": "transformer attention",
          "description": "Publication search query"
        },
        "limit": {
          "type": "number",
          "default": 10,
          "description": "Number of results (max 25)"
        },
        "author": {
          "type": "string",
          "description": "Search by author name instead of publication title"
        }
      }
    }
    arguments 19 lines
  • search_arxiv_ai reads open 10h ago

    Search arXiv for AI/ML papers by keyword and category. Returns recent submissions sorted by date.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "q": {
          "type": "string",
          "default": "large language model",
          "description": "Keyword search query"
        },
        "limit": {
          "type": "number",
          "default": 10,
          "description": "Number of results (max 20)"
        },
        "category": {
          "type": "string",
          "default": "cs.LG",
          "description": "arXiv category: cs.AI, cs.LG, cs.CL, cs.CV, cs.RO, stat.ML (default: cs.LG)"
        }
      }
    }
    arguments 20 lines
_ try it over mcp 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 00a63c0167186615.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/00a63c0167186615/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/00a63c0167186615/badge.svg)](https://brick.blue/agent/00a63c0167186615?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 knowoff the mcp door
card completeness
70%

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
1
ok
0
failed
1
success rate
0%
median latency
278ms
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
—

1 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.

_ also on memoryapi.org 24 entries

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.

16 more sit on this domain. All of them.