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

Michael Vereb

https://www.michaelvereb.com

Registry code: 81e717ad2118a4e5

api record

Query portfolio case studies, verified developer tools, and the AI-UI design system.

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

endpoint
https://www.michaelvereb.com/mcp
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 Michael Vereb live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is Michael Vereb free to use?
Yes — the hub reached it with no key and no payment.
What tools does Michael Vereb have?
7 tools: get_case_study, list_contact, search_articles, get_tools, get_portfolio, get_ai_ui, get_testimonials.
Is Michael Vereb 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
133ms

last good check

priced tools
0

of 7 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 7 tools
3 open 4 never probed 3 of 7 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_portfolio open 1h ago

    Retrieves client case studies and engineering projects. Supports optional search query (by company name or topic) and limit parameter.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "limit": {
      "type": "integer",
      "description": "Maximum number of works to return (default: 10, max: 50)."
    },
    "query": {
      "type": "string",
      "description": "Optional company name, client name, or project keyword (e.g., Arbor, Morgenlevering, JobQualified, Northwind)."
    }
  }
}
    arguments 14 lines
  • get_ai_ui open 1h ago

    Overview of the AI-UI design system (20 accessible Astro components for AI reasoning, execution pipelines, and streaming chat), package install instructions, and pointer to the dedicated sub-MCP server at https://www.michaelvereb.com/ai-ui/mcp.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {}
}
    arguments 5 lines
  • get_testimonials open 1h ago

    Retrieves verified client reviews, leadership testimonials, and stakeholder endorsements with author names, roles, and review quotes.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "platform": {
      "type": "string",
      "description": "Optional platform filter (e.g., website, linkedin) to filter testimonials."
    }
  }
}
    arguments 10 lines
  • get_case_study unknown never probed

    Retrieves detailed architecture, technical deliverables, and impact metrics for a specific client case study by company slug.

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "Unique URL slug identifier of the case study (e.g., arbor, morgenlevering, jobqualified)."
    }
  }
}
    arguments 12 lines
  • list_contact unknown never probed

    Retrieves verified contact channels, email address, LinkedIn profile, timezone, and direct scheduling links.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {}
}
    arguments 5 lines
  • search_articles unknown never probed

    Searches published technical articles, design system guides, and AI/SEO strategy posts by keyword.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "description": "Search term or topic keywords to search across articles and guides (e.g., SEO, AI, design system)."
    }
  }
}
    arguments 12 lines
  • get_tools unknown never probed

    Retrieves developer tools, open-source packages, and AI infrastructure created and maintained by Michael Vereb.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {}
}
    arguments 5 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 81e717ad2118a4e5.

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

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.