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

ai-portal

https://www.ai-portal.ai

Registry code: 8d6345ab7de36399

api record

Read-only tools over AI-Portal data (https://www.ai-portal.ai): AI model releases, AI regulations, a GenAI glossary, and daily curated GenAI news. Use list_releases for "when did model X ship / what did provider Y release", list_regulations for AI compliance status, search_glossary for term definitions, and get_latest_news for current GenAI headlines.

endpoint
https://www.ai-portal.ai/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 ai-portal live?
Yes — it answered the hub's last check (checked 2h ago). It answered 98% of checks over the last 30 days.
Is ai-portal free to use?
Yes — the hub reached it with no key and no payment.
What tools does ai-portal have?
4 tools: search_glossary, list_regulations, get_latest_news, list_releases.
Is ai-portal 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
98%

90 days 98.3%· all time 98.4%

latency
924ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 535 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
search & web news
used for
  • get latest generative ai news
  • list ai model releases
  • check ai regulation status
  • look up an ai term
takes → gives
text → data
tools
4 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 4 tools
4 open 4 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.

  • search_glossary reads open 13h ago

    Search AI-Portal's glossary of AI/GenAI terms. Returns term, definition, category, and a usage example.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "description": "Search text, matched against term, abbreviation, and definition"
    },
    "category": {
      "enum": [
        "fundamentals",
        "architecture",
        "training",
        "deployment",
        "safety",
        "agents",
        "evaluation"
      ],
      "type": "string"
    }
  }
}
    arguments 24 lines
  • list_regulations reads open 23h ago

    List AI regulations and their compliance status (EU AI Act, ISO 42001, and more), including jurisdiction, effective dates, key requirements, and fines.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "status": {
      "enum": [
        "In Force",
        "Transitional",
        "Draft",
        "Proposed"
      ],
      "type": "string",
      "description": "Filter by status"
    },
    "jurisdiction": {
      "type": "string",
      "description": "Jurisdiction substring, e.g. \"european\", \"israel\""
    }
  }
}
    arguments 19 lines
  • get_latest_news reads open 23h ago

    Latest curated GenAI news items from AI-Portal, refreshed every weekday morning.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "number",
      "description": "Max items to return (default 10, max 30)"
    }
  }
}
    arguments 9 lines
  • list_releases reads open 23h ago

    List AI model and product releases tracked by AI-Portal, newest first. Filter by category, provider, year, or landmark releases only.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "year": {
      "type": "string",
      "description": "Four-digit year, e.g. \"2026\""
    },
    "limit": {
      "type": "number",
      "description": "Max items to return (default 25, max 100)"
    },
    "category": {
      "enum": [
        "llm",
        "multimodal",
        "image",
        "video",
        "tool",
        "framework"
      ],
      "type": "string",
      "description": "Release category"
    },
    "provider": {
      "type": "string",
      "description": "Provider name substring, e.g. \"anthropic\", \"google\""
    },
    "landmark_only": {
      "type": "boolean",
      "description": "Only landmark (major) releases"
    }
  }
}
    arguments 33 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 8d6345ab7de36399.

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