_ registry / mcp streamable-http · checked 17m ago

jobctl

https://app.jobctl.app

Registry code: a5762d661328a44c

api record

Job application tracker for developers - AI agents write over MCP, you review in a dashboard.

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

endpoint
https://app.jobctl.app/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 jobctl live?
Yes — it answered the hub's last check (checked 17m ago). It answered 99% of checks over the last 30 days.
Is jobctl free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does jobctl have?
11 tools: add_note, update_application, attach_analysis, get_planned, list_applications, add_application, log_interview, attach_file, ….
Is jobctl 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.1%

90 days 99.5%· all time 99.5%

latency
77ms

last good check

priced tools
0

of 11 tools

_ answered our checks, 90 days 372 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
productivity & business hr & recruiting
used for
  • track a job application
  • log an interview for an application
  • attach a cv or cover letter
  • list applications due today
  • add notes to an application
takes → gives
text, documents → data
tools
4 reads7 changes data
_ 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 11 tools
11 auth-required 11 of 11 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.

  • add_note changes data auth-required never probed

    Append a free-text note to an application timeline — recruiter call summaries, interview instructions, pasted messages. Multiline markdown is fine. Example: `add_note({application_id: "…", text: "Recruiter: team of 5, on-call rotation, offer range 85-95k"})`.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "application_id",
    "text"
  ],
  "properties": {
    "text": {
      "type": "string",
      "minLength": 1
    },
    "application_id": {
      "type": "string",
      "format": "uuid",
      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    }
  }
}
    arguments 19 lines
  • update_application changes data auth-required never probed

    Update fields of an application (get the id from list_applications). Status changes are logged to the timeline automatically. Example: `update_application({id: "…", status: "interview", next_action: "prepare system design", next_action_due: "2026-07-20"})`.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "format": "uuid",
      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    },
    "url": {
      "type": "string",
      "description": "Link to the job posting"
    },
    "role": {
      "type": "string"
    },
    "remote": {
      "enum": [
        "remote",
        "hybrid",
        "onsite",
        "unknown"
      ],
      "type": "string"
    },
    "source": {
      "type": "string",
      "description": "LinkedIn, referral, recruiter, Easy Apply…"
    },
    "status": {
      "enum": [
        "started_apply",
        "waiting_referral",
        "applied",
        "waiting",
        "interview",
        "offer",
        "accepted",
        "rejected",
        "no_response",
        "on_hold",
        "withdrawn",
        "archived"
      ],
      "type": "string"
    },
    "company": {
      "type": "string"
    },
    "location": {
      "type": "string"
    },
    "priority": {
      "enum": [
        "A",
        "B",
        "C"
      ],
      "type": "string",
      "description": "A = top priority"
    },
    "applied_at": {
      "type": "string",
      "description": "ISO date YYYY-MM-DD"
    },
    "cv_variant": {
      "type": "string",
      "description": "Which CV was sent: DE, EN, AI-focused…"
    },
    "match_notes": {
      "type": "string",
      "description": "Markdown match assessment: why the candidate fits this role — strengths vs requirements, gaps, level/salary advice, process notes. Save your vacancy analysis here so it is not lost; shown as an expandable section in the dashboard."
    },
    "next_action": {
      "type": "string",
      "description": "e.g. \"follow-up\", \"thank-you email\""
    },
    "remote_note": {
      "type": "string",
      "description": "e.g. \"2 days office\""
    },
    "salary_asked": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": -9007199254740991,
      "description": "What the candidate asked for — yearly gross EUR as a plain number, e.g. 110000"
    },
    "salary_range": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": -9007199254740991,
      "description": "Posting salary range upper bound — yearly gross EUR, plain number"
    },
    "next_action_due": {
      "type": "string",
      "description": "ISO date YYYY-MM-DD"
    },
    "salary_range_min": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": -9007199254740991,
      "description": "Posting salary range lower bound — yearly gross EUR, plain number"
    },
    "next_interview_at": {
      "type": "string",
      "description": "ISO datetime, e.g. 2026-07-20T14:00:00+02:00"
    }
  }
}
    arguments 112 lines
  • attach_analysis changes data auth-required never probed

    Attach a markdown company analysis (research you produced) to an application. Single document per application — a new call REPLACES the previous one. Max 100000 bytes (~100 KB) of utf-8. The user reads it in the dashboard, e.g. before an interview. Example: `attach_analysis({application_id: "…", markdown: "# Bosch\n\n## Culture…"})`.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "application_id",
    "markdown"
  ],
  "properties": {
    "markdown": {
      "type": "string",
      "minLength": 1,
      "description": "The analysis as markdown"
    },
    "application_id": {
      "type": "string",
      "format": "uuid",
      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    }
  }
}
    arguments 20 lines
  • get_planned reads auth-required 3h ago

    What is actually SCHEDULED: interviews with their time, attendees and meeting links, plus the actions falling due, for today, tomorrow, or the next seven days. Use this whenever the user asks what is planned, what the day or week looks like, or before proposing a time to anyone — get_due only knows action deadlines and is blind to booked interviews. Example: `get_planned({range: "tomorrow"})`.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "range": {
      "enum": [
        "today",
        "tomorrow",
        "week"
      ],
      "type": "string",
      "description": "today (default), tomorrow, or week (today plus the next 6 days)"
    }
  }
}
    arguments 15 lines
  • list_applications reads auth-required 3h ago

    List job applications. Filter by view (active = default working set, archive = rejected/withdrawn/no-response), status list, priority, or free-text search in company/role. Example: `list_applications({view: "active"})`, `list_applications({q: "bosch"})`.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "q": {
      "type": "string",
      "description": "Search in company/role"
    },
    "view": {
      "enum": [
        "active",
        "interviewing",
        "waiting",
        "archive",
        "all"
      ],
      "type": "string"
    },
    "limit": {
      "type": "integer",
      "maximum": 500,
      "minimum": 1
    },
    "status": {
      "type": "string",
      "description": "Comma-separated: started_apply, waiting_referral, applied, waiting, interview, offer, accepted, rejected, no_response, on_hold, withdrawn, archived"
    },
    "priority": {
      "enum": [
        "A",
        "B",
        "C"
      ],
      "type": "string"
    }
  }
}
    arguments 37 lines
  • add_application changes data auth-required never probed

    Track a new job application. Pass either a single `raw` line — `add_application({raw: "Bosch, Tech Lead, prio A, due friday, remote, via LinkedIn"})` — or structured fields (`company` and `role` required then). Returns the created application and possible-duplicate warnings; if duplicates are listed, tell the user instead of creating again.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "raw": {
      "type": "string",
      "description": "Free-form line: \"Company, Role, prio A|B|C, due <date>, remote|hybrid|onsite, via <source>, https://…, in <location>, applied <date>\""
    },
    "url": {
      "type": "string",
      "description": "Link to the job posting"
    },
    "role": {
      "type": "string"
    },
    "remote": {
      "enum": [
        "remote",
        "hybrid",
        "onsite",
        "unknown"
      ],
      "type": "string"
    },
    "source": {
      "type": "string",
      "description": "LinkedIn, referral, recruiter, Easy Apply…"
    },
    "status": {
      "enum": [
        "started_apply",
        "waiting_referral",
        "applied",
        "waiting",
        "interview",
        "offer",
        "accepted",
        "rejected",
        "no_response",
        "on_hold",
        "withdrawn",
        "archived"
      ],
      "type": "string"
    },
    "company": {
      "type": "string"
    },
    "location": {
      "type": "string"
    },
    "priority": {
      "enum": [
        "A",
        "B",
        "C"
      ],
      "type": "string",
      "description": "A = top priority"
    },
    "applied_at": {
      "type": "string",
      "description": "ISO date YYYY-MM-DD"
    },
    "cv_variant": {
      "type": "string",
      "description": "Which CV was sent: DE, EN, AI-focused…"
    },
    "match_notes": {
      "type": "string",
      "description": "Markdown match assessment: why the candidate fits this role — strengths vs requirements, gaps, level/salary advice, process notes. Save your vacancy analysis here so it is not lost; shown as an expandable section in the dashboard."
    },
    "next_action": {
      "type": "string",
      "description": "e.g. \"follow-up\", \"thank-you email\""
    },
    "remote_note": {
      "type": "string",
      "description": "e.g. \"2 days office\""
    },
    "salary_asked": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": -9007199254740991,
      "description": "What the candidate asked for — yearly gross EUR as a plain number, e.g. 110000"
    },
    "salary_range": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": -9007199254740991,
      "description": "Posting salary range upper bound — yearly gross EUR, plain number"
    },
    "next_action_due": {
      "type": "string",
      "description": "ISO date YYYY-MM-DD"
    },
    "salary_range_min": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": -9007199254740991,
      "description": "Posting salary range lower bound — yearly gross EUR, plain number"
    },
    "next_interview_at": {
      "type": "string",
      "description": "ISO datetime, e.g. 2026-07-20T14:00:00+02:00"
    }
  }
}
    arguments 108 lines
  • log_interview changes data auth-required never probed

    Log an interview for an application (max 10 per application): when it takes place, its status (planned or done), who attends (each with an optional profile link), related links (prep materials the company sent, meeting URL), and a short recap of what was discussed. Also keeps the application's next-interview date in sync. Example: `log_interview({application_id: "…", scheduled_at: "2026-07-20T14:00:00+02:00", status: "planned", attendees: [{name: "Anna Weber (HR)", url: "https://linkedin.com/in/annaweber"}], links: [{label: "Prep materials", url: "https://company.com/interview-prep"}], recap: "System design round"})`.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "application_id",
    "scheduled_at"
  ],
  "properties": {
    "links": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "url"
        ],
        "properties": {
          "url": {
            "type": "string"
          },
          "label": {
            "type": "string",
            "description": "e.g. \"Prep materials\", \"Meeting link\""
          }
        }
      },
      "description": "Related links: prep materials, meeting URL, docs"
    },
    "recap": {
      "type": "string",
      "description": "Short recap of what was discussed"
    },
    "status": {
      "enum": [
        "planned",
        "done"
      ],
      "type": "string",
      "description": "planned (default) or done"
    },
    "attendees": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "name"
        ],
        "properties": {
          "url": {
            "type": "string",
            "description": "Profile link, e.g. LinkedIn"
          },
          "name": {
            "type": "string"
          }
        }
      },
      "description": "Who attends, each with an optional profile link"
    },
    "scheduled_at": {
      "type": "string",
      "description": "ISO datetime with offset, e.g. 2026-07-20T14:00:00+02:00"
    },
    "application_id": {
      "type": "string",
      "format": "uuid",
      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    }
  }
}
    arguments 69 lines
  • attach_file changes data auth-required never probed

    Attach or replace a file on an application so the user sees it in the dashboard: a CV/resume (kind: 'cv') or a cover letter (kind: 'cover_letter'). Pass the file bytes as base64 in data_base64. One file per (application, kind) - a new call REPLACES the previous one. Max ~5 MB; pdf/doc/docx/txt/md (MIME is inferred from the filename if you omit it). Call this whenever you generate a tailored CV or cover letter for an application. Example: `attach_file({application_id: "…", kind: "cv", filename: "CV_Cursor.pdf", data_base64: "JVBERi0…"})`.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "application_id",
    "kind",
    "filename",
    "data_base64"
  ],
  "properties": {
    "kind": {
      "enum": [
        "cv",
        "cover_letter"
      ],
      "type": "string"
    },
    "mime": {
      "type": "string",
      "description": "Optional; inferred from the filename extension when omitted"
    },
    "filename": {
      "type": "string",
      "maxLength": 300,
      "minLength": 1
    },
    "data_base64": {
      "type": "string",
      "minLength": 1,
      "description": "Base64-encoded file bytes"
    },
    "application_id": {
      "type": "string",
      "format": "uuid",
      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    }
  }
}
    arguments 38 lines
  • get_due reads auth-required 3h ago

    What is burning today: applications with next_action_due today or overdue. Call this when the user asks "what should I do today?" about their job search.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • get_application reads auth-required 17m ago

    Full detail of one application: all fields, contacts, recent timeline events, and whether a company analysis is attached (fetch it via the dashboard or attach_analysis to replace).

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "format": "uuid",
      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    }
  }
}
    arguments 14 lines
  • attach_interview_file changes data auth-required never probed

    Attach prep material to a specific interview so the user sees it next to that round in the dashboard: the prep document you wrote, the job description, a deck, notes the company sent. Max 3 files per interview, 20000000 bytes (20 MB) each; pass the bytes as base64. Get interview ids from get_application. Example: `attach_interview_file({application_id: "…", interview_id: "…", filename: "prep-round2.md", data_base64: "IyBQcmVw…"})`.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "application_id",
    "interview_id",
    "filename",
    "data_base64"
  ],
  "properties": {
    "mime": {
      "type": "string",
      "description": "Optional; inferred from the filename extension when omitted"
    },
    "filename": {
      "type": "string",
      "maxLength": 300,
      "minLength": 1
    },
    "data_base64": {
      "type": "string",
      "minLength": 1,
      "description": "Base64-encoded file bytes"
    },
    "interview_id": {
      "type": "string",
      "format": "uuid",
      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    },
    "application_id": {
      "type": "string",
      "format": "uuid",
      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    }
  }
}
    arguments 36 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 a5762d661328a44c.

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