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

maxcv

https://maxcv.ai

Registry code: 31021cce08d18d7d

api record

MaxCV assesses and tailors supplied CV text against a job posting. Use score_cv for a source-only assessment; tailor_cv generates and assesses actual before/after documents. Do not add facts; AI can make mistakes, so have the user review every change. Scores are not employer ATS scores or hiring probabilities. Text only: no saved-account access, PDF export or application submission. Per-network limits: 10 assessments/hour and 2 tailorings/day; global limits also apply.

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 2h ago). It answered 99% of checks over the last 30 days.
Is maxcv free to use?
Yes — the hub reached it with no key and no payment.
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
98.8%

90 days 99.6%· all time 99.6%

latency
1,105ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 515 checks · signed record
  • degraded → live
  • live → degraded· fetch failed
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • score a cv against a job posting
  • tailor a cv to a job posting
takes → gives
text, documents → text
tools
2 reads
_ 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 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 12h ago

    Assess the supplied CV only (assessmentKind=source_only), without generating a document or predicted after score. With v2b, method=offer-phrase-coverage-v1 measures exact positive coverage of frozen phrases copied from offer requirements and duties, with phrase counts and matched/missing lists; an empty inventory scores zero. phraseCount (not requirementCount) is the denominator; the inventory is extracted once per exact offer text and reused (assessment.inventoryHash); nested phrases count once. Other engines retain method=jev-probability-v1 with semantic per-requirement probabilities. Neither is an employer ATS score or hiring probability. Use tailor_cv for actual before/after documents.

    mcp-tool

    {
      "type": "object",
      "required": [
        "cvText",
        "jobDescription"
      ],
      "properties": {
        "cvText": {
          "type": "string",
          "maxLength": 20000,
          "minLength": 80,
          "description": "Relevant CV or resume text, at least 80 characters after trimming. Omit contact details and sensitive identifiers."
        },
        "jobDescription": {
          "type": "string",
          "maxLength": 20000,
          "minLength": 80,
          "description": "The job posting as plain text, at least 80 characters after trimming. The CV and job posting together must fit in 20000 UTF-8 bytes when encoded as JSON, including JSON syntax and escapes."
        }
      }
    }
    arguments 21 lines
  • tailor_cv reads unknown 12h ago

    Tailor a supplied CV/resume to a specific job posting. A successful tailoring returns the actual tailored CV and before/after assessments, plus role-fit notes, interview preparation and a cover letter when available. A role mismatch or a finding of possible added or omitted facts can prevent delivery of a tailored CV. AI can make mistakes; review every change. Text input/output only; does not access saved accounts, export PDFs or submit applications. Limited to 2 calls per day per network.

    mcp-tool

    {
      "type": "object",
      "required": [
        "cvText",
        "jobDescription"
      ],
      "properties": {
        "cvText": {
          "type": "string",
          "maxLength": 20000,
          "minLength": 80,
          "description": "Relevant CV or resume text, at least 80 characters after trimming. Omit contact details and sensitive identifiers."
        },
        "jobDescription": {
          "type": "string",
          "maxLength": 20000,
          "minLength": 80,
          "description": "The job posting as plain text, at least 80 characters after trimming. The CV and job posting together must fit in 20000 UTF-8 bytes when encoded as JSON, including JSON syntax and escapes."
        }
      }
    }
    arguments 21 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.