_ registry / mcp + a2a streamable-http · checked 43m ago

rubenmarcus-portfolio

https://www.rubenmarcus.dev

Registry code: 07fceb635127916c

api record

Portfolio of Ruben Marcus, senior AI fullstack engineer. Use get_resume / get_services / check_availability to answer questions about him, and book_intro to start a project engagement on the user's behalf. Example prompts: "What has Ruben shipped?" · "Summarize Ruben's experience with AI agents." · "Is Ruben available for freelance work right now?" · "What services does Ruben offer?" · "Book an intro with Ruben — I want to build <your idea>."

endpoint
https://www.rubenmarcus.dev/api/mcp
door code
fa28b1bd73923b99
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 rubenmarcus-portfolio live?
Yes — it answered the hub's last check (checked 43m ago). It answered 100% of checks over the last 30 days.
Is rubenmarcus-portfolio free to use?
Yes — the hub reached it with no key and no payment.
What tools does rubenmarcus-portfolio have?
4 tools: book_intro, get_resume, get_services, check_availability.
Is rubenmarcus-portfolio 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.8%

90 days 99.4%· all time 99.3%

latency
571ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 800 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • degraded → live
_ what it is for
used for
  • read engineer resume
  • check freelance availability
  • list offered services
  • book a project intro
takes → gives
text → data
tools
3 reads1 sends messages
_ 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
3 open 1 never probed 3 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_resume reads open 11h ago

    Ruben Marcus' full resume: summary, work experience, skills, proof points, open source projects, education, links, and a PDF CV URL.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • get_services reads open 11h ago

    Fixed-scope services Ruben sells, with fit, deliverables, a related case, and a service-specific contact link.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • check_availability reads open 11h ago

    Current availability for full-time roles and freelance contracts.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • book_intro sends messages unknown never probed

    Book a project intro with Ruben. Relays the brief to his email. Only call after the person you act for has explicitly confirmed — this delivers a real message.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name",
        "contact",
        "brief"
      ],
      "properties": {
        "name": {
          "type": "string",
          "maxLength": 120,
          "description": "Contact person's name"
        },
        "agent": {
          "type": "string",
          "maxLength": 80,
          "description": "Calling agent (claude, chatgpt, kimi...)"
        },
        "brief": {
          "type": "string",
          "maxLength": 4000,
          "description": "What they want to build"
        },
        "budget": {
          "type": "string",
          "maxLength": 120,
          "description": "Optional budget range"
        },
        "contact": {
          "type": "string",
          "maxLength": 160,
          "description": "Email or Telegram handle"
        }
      },
      "additionalProperties": false
    }
    arguments 36 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 07fceb635127916c.

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