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

oaki

https://www.oaki.io

Registry code: 7dbea24e2017b8f7

api record

Oaki AI matches a resume to live job postings from Oaki's index of jobs posted on company career sites. Call find_jobs_for_resume when the user shares their resume (pasted text or an attached file you can read) and asks for jobs that fit it. Pass the resume as plain text. Before matching, Oaki removes the name line, email addresses, phone numbers, profile links and street addresses, and it does not store the resume. Each result has a fit score from 0 to 100, a one-line reason and a link to the posting on the employer's site.

endpoint
https://www.oaki.io/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 oaki live?
Yes — it answered the hub's last check (checked 24h ago). It answered 100% of checks over the last 30 days.
Is oaki free to use?
Yes — the hub reached it with no key and no payment.
What tools does oaki have?
1 tool: find_jobs_for_resume.
Is oaki 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
854ms

last good check

priced tools
0

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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 1 tools
1 never probed 0 of 1 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.

  • find_jobs_for_resume unknown 24h ago

    Finds live jobs that fit a resume, from Oaki AI's index of jobs posted on company career sites. Use it when the user shares a resume and wants matching job openings. Input is the resume as plain text, plus optional country, US state or Canadian province, and remote-only filters. Returns up to 10 jobs ranked by fit, each with title, company, location, date posted, pay when the posting lists it, a fit score from 0 to 100, a short reason, and a link to apply on the employer's site. Read-only: it does not apply to jobs, create an account or store the resume; the name line and contact details are removed before matching. Limits: English-language resumes work best, results only include jobs in Oaki's index, and each address can run a few searches a minute.

    mcp-tool

    {
      "type": "object",
      "required": [
        "resume_text"
      ],
      "properties": {
        "region": {
          "enum": [
            "AL",
            "AK",
            "AZ",
            "AR",
            "CA",
            "CO",
            "CT",
            "DE",
            "DC",
            "FL",
            "GA",
            "HI",
            "ID",
            "IL",
            "IN",
            "IA",
            "KS",
            "KY",
            "LA",
            "ME",
            "MD",
            "MA",
            "MI",
            "MN",
            "MS",
            "MO",
            "MT",
            "NE",
            "NV",
            "NH",
            "NJ",
            "NM",
            "NY",
            "NC",
            "ND",
            "OH",
            "OK",
            "OR",
            "PA",
            "RI",
            "SC",
            "SD",
            "TN",
            "TX",
            "UT",
            "VT",
            "VA",
            "WA",
            "WV",
            "WI",
            "WY",
            "AB",
            "BC",
            "MB",
            "NB",
            "NL",
            "NS",
            "NT",
            "NU",
            "ON",
            "PE",
            "QC",
            "SK",
            "YT"
          ],
          "type": "string",
          "description": "Optional US state or Canadian province code to search in, for example \"TX\" for Austin or \"ON\" for Toronto; remote jobs are kept too. It sets the country to US or CA when country is left out. Cities are not supported, so pass the state or province."
        },
        "country": {
          "enum": [
            "US",
            "CA",
            "GB",
            "IE",
            "AU",
            "IN",
            "DE",
            "FR",
            "NL",
            "ES",
            "PL",
            "SG",
            "BR",
            "MX",
            "JP"
          ],
          "type": "string",
          "description": "Two-letter code of the country to search. Leave it out to use the country written at the top of the resume; if the resume names none, every country in the index is searched."
        },
        "remote_only": {
          "type": "boolean",
          "description": "Set to true to return only remote jobs. Defaults to false."
        },
        "resume_text": {
          "type": "string",
          "maxLength": 30000,
          "description": "The full text of the resume (work history, skills, education). At least a few lines; contact details may be left out."
        }
      },
      "additionalProperties": false
    }
    arguments 109 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 7dbea24e2017b8f7.

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

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.