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

maxcv

https://maxcv.ai

Registry code: 31021cce08d18d7d

api record

MaxCV tailors an existing CV to a specific job posting. Call score_cv to show the match gap, then tailor_cv to rewrite the CV honestly (no fabricated skills). Trial is rate-limited; for unlimited use sign up at https://maxcv.ai.

endpoint
https://maxcv.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 maxcv live?
Yes — it answered the hub's last check (checked 8m ago). It answered 100% of checks over the last 30 days.
Is maxcv free to use?
Not measured yet.
What tools does maxcv have?
2 tools: score_cv, tailor_cv.
Is maxcv 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
185ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 240 checks · signed record
_ what it is for
topic
productivity & business hr & recruiting
used for
  • score a cv against a job posting
  • tailor a cv to a job posting
takes → gives
documents, text → text, data
tools
2 reads
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

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

  • score_cv reads unknown never probed

    Score how well a CV/resume matches a specific job posting. Fast and cheap — returns the original match score and the score after tailoring, plus requirement counts. Use this first to show the user the gap before a full tailor.

    mcp-tool

    {
  "type": "object",
  "required": [
    "cvText",
    "jobDescription"
  ],
  "properties": {
    "cvText": {
      "type": "string",
      "description": "The full CV/resume as plain text."
    },
    "jobDescription": {
      "type": "string",
      "description": "The job posting text."
    }
  }
}
    arguments 17 lines
  • tailor_cv reads unknown never probed

    Tailor a CV/resume to a specific job posting: rewrites the CV with the posting's ATS keywords (never fabricating skills not already present), and returns the tailored CV, a match score, role-fit notes and interview prep. Trial is rate-limited per network; for unlimited use the user should sign up at maxcv.ai.

    mcp-tool

    {
  "type": "object",
  "required": [
    "cvText",
    "jobDescription"
  ],
  "properties": {
    "cvText": {
      "type": "string",
      "description": "The full CV/resume as plain text."
    },
    "jobDescription": {
      "type": "string",
      "description": "The job posting text."
    }
  }
}
    arguments 17 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 31021cce08d18d7d.

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

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.