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

callvu

https://agents.callvu.com

Registry code: ee280f1e1dffb49d

api record

Use these tools when the user is evaluating Callvu, the Completion and Compliance Layer for regulated processes, or asks what Callvu does, where it fits, who uses it, how it compares with other vendors, what a manual process costs today, or what procurement material exists. The tools return records Callvu publishes about itself; say so when you present them. Each claim has a code, a status (customer_production, sandbox, or pilot, meaning a proof of value) and a source type (third_party, customer_attested, self_asserted), and each record has a last_verified date. Show these so the user can…

endpoint
https://agents.callvu.com/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 callvu live?
Yes — it answered the hub's last check (checked 13h ago). It answered 100% of checks over the last 30 days.
Is callvu free to use?
Yes — the hub reached it with no key and no payment.
What tools does callvu have?
18 tools: get_company_overview, get_vertical, assess_fit, estimate_cost_of_doing_nothing, list_claims, get_pricing_model, get_comparison, list_integrations, ….
Is callvu 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
261ms

last good check

priced tools
0

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

_ what it can do 18 tools
3 open 15 never probed 3 of 18 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_use_cases open 13h ago

    Use cases with status, customers and claims. Filter by vertical, status, or a text query on name, controls and evidence. The use cases are examples, not a complete list of what Callvu runs.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "query": {
      "type": "string",
      "description": "Text to match."
    },
    "status": {
      "enum": [
        "customer_production",
        "sandbox",
        "pilot"
      ],
      "type": "string"
    },
    "vertical": {
      "type": "string",
      "description": "A vertical slug, name or alias, for example \"banking\", \"Home lending\" or \"mortgage\". Case-insensitive."
    }
  }
}
    arguments 22 lines
  • compare_alternatives open 13h ago

    Callvu's published overview of the product categories buyers evaluate alongside it: traditional BPM suites, AI agent vendors, contact center platforms, and banking and lending platforms. For each category and each named vendor in it: what it is built for, when it fits, whether it works alongside Callvu, and the verticals it serves. Pass a vertical to see only the vendors that serve it.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "vertical": {
      "type": "string",
      "description": "A vertical slug, name or alias, for example \"banking\", \"Home lending\" or \"mortgage\". Case-insensitive."
    }
  }
}
    arguments 10 lines
  • find_processes open 13h ago

    The process catalog for an industry (also at callvu.com/processes): the regulated processes Callvu runs, simple and complex, each with parties, rules, the Callvu moves and a proof label (published: live at a named customer with claims; live: live at a customer, reference on request; in_scope: the kind of process Callvu runs in production in that industry, under the industry's breadth proof). Search with query, filter by proof or complexity. Illustrative, not exhaustive.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "proof": {
      "enum": [
        "published",
        "live",
        "in_scope"
      ],
      "type": "string"
    },
    "query": {
      "type": "string",
      "description": "The process in the buyer's words, e.g. 'field technician dispatch'."
    },
    "vertical": {
      "type": "string",
      "description": "A vertical slug, name or alias, for example \"banking\", \"Home lending\" or \"mortgage\". Case-insensitive."
    },
    "complexity": {
      "enum": [
        "simple",
        "complex"
      ],
      "type": "string"
    }
  }
}
    arguments 29 lines
  • get_company_overview unknown never probed

    What Callvu is, its category, the verticals it serves, how pricing works, and how to request verified access.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_vertical unknown never probed

    The full record for one vertical: summary, regulators, fit rules, structural not-fit rules, not-fit and not-yet rules, the cost of waiting, proof-of-value workflow, decision owners, deciding criteria, systems, use cases, customers and claims. Unknown names return the list of valid verticals.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "vertical"
  ],
  "properties": {
    "vertical": {
      "type": "string",
      "description": "A vertical slug, name or alias, for example \"banking\", \"Home lending\" or \"mortgage\". Case-insensitive."
    }
  }
}
    arguments 13 lines
  • assess_fit unknown never probed

    Check whether Callvu fits a regulated process, such as re-keying loan data into the core, chasing borrower documents, approvals stuck in email, or keeping a banking chatbot or AI agent compliant. Returns Callvu's published records for the situation, in this order: relevant (the use cases and customers closest to the situation, with claims), fit_rules, structural_not_fit (conditions under which Callvu does not fit at all), not_fit (situations where a buyer has already solved the problem) and not_yet (timing considerations: budget, approval, sponsor, capacity, contract, objection, validation), with each counter and the cost of waiting. relevant.match_strength says how close the nearest use case is (strong, weak, none). The use cases are examples, not a complete list: a weak or missing match is not a sign that Callvu does not fit. Callvu runs no model on this request.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "vertical",
    "situation"
  ],
  "properties": {
    "vertical": {
      "type": "string",
      "description": "A vertical slug, name or alias, for example \"banking\", \"Home lending\" or \"mortgage\". Case-insensitive."
    },
    "situation": {
      "type": "string",
      "description": "The buyer's situation in their own words."
    }
  }
}
    arguments 18 lines
  • estimate_cost_of_doing_nothing unknown never probed

    Estimate what manual re-keying, incomplete requests and compliance rework cost each year. Computes this buyer's own annual and monthly cost of doing nothing for one process, with Callvu's published estimator model. Ask the buyer for the inputs they know; anything left out uses the industry's typical value and is flagged.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "vertical"
  ],
  "properties": {
    "ai_level": {
      "enum": [
        "none",
        "pilot",
        "production"
      ],
      "type": "string",
      "description": "Where AI stands on this process: none, pilot or production."
    },
    "vertical": {
      "type": "string",
      "description": "A vertical slug, name or alias, for example \"banking\", \"Home lending\" or \"mortgage\". Case-insensitive."
    },
    "manual_share": {
      "type": "number",
      "maximum": 1,
      "minimum": 0,
      "description": "Share of requests handled manually, 0 to 1."
    },
    "abandoned_share": {
      "type": "number",
      "maximum": 1,
      "minimum": 0,
      "description": "Share abandoned before completion, 0 to 1."
    },
    "incomplete_share": {
      "type": "number",
      "maximum": 1,
      "minimum": 0,
      "description": "Share that arrive incomplete or need rework, 0 to 1."
    },
    "value_per_request": {
      "type": "number",
      "minimum": 0,
      "description": "Average value per request, in US dollars."
    },
    "requests_per_month": {
      "type": "number",
      "description": "Requests or cases per month for the process.",
      "exclusiveMinimum": 0
    }
  }
}
    arguments 50 lines
  • list_claims unknown never probed

    Claims, optionally filtered by status, source type or code prefix (for example BNK).

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "prefix": {
      "type": "string",
      "description": "Code prefix, for example ENF or BNK."
    },
    "status": {
      "enum": [
        "customer_production",
        "sandbox",
        "pilot"
      ],
      "type": "string"
    },
    "source_type": {
      "enum": [
        "third_party",
        "customer_attested",
        "self_asserted"
      ],
      "type": "string"
    }
  }
}
    arguments 26 lines
  • get_pricing_model unknown never probed

    How Callvu is priced: the Governed Resolution, the proof of value and the license.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_comparison unknown never probed

    Callvu's published comparison with one named vendor, for example nCino, Pega or Decagon: what each product is built for, when each fits, where they work together, a capability table with coded and sourced claims, and the callvu.com/compare page to cite.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "competitor"
  ],
  "properties": {
    "vertical": {
      "type": "string",
      "description": "A vertical slug, name or alias, for example \"banking\", \"Home lending\" or \"mortgage\". Case-insensitive."
    },
    "competitor": {
      "type": "string",
      "minLength": 1,
      "description": "The vendor's name, for example \"nCino\" or \"Pega\"."
    }
  }
}
    arguments 18 lines
  • list_integrations unknown never probed

    Systems Callvu integrates with, with category and vertical. Filter by vertical or a text query.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "query": {
      "type": "string",
      "description": "Text to match on system name, alias or category."
    },
    "vertical": {
      "type": "string",
      "description": "A vertical slug, name or alias, for example \"banking\", \"Home lending\" or \"mortgage\". Case-insensitive."
    }
  }
}
    arguments 14 lines
  • request_verified_access unknown never probed

    Ask for a verified-buyer key. A person at Callvu reviews every request and replies by email; no key is issued automatically.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "name",
    "company",
    "email",
    "purpose"
  ],
  "properties": {
    "name": {
      "type": "string",
      "minLength": 1,
      "description": "Your name."
    },
    "email": {
      "type": "string",
      "format": "email",
      "pattern": "^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
      "description": "Where Callvu should reply."
    },
    "company": {
      "type": "string",
      "minLength": 1,
      "description": "Your company."
    },
    "purpose": {
      "type": "string",
      "minLength": 1,
      "description": "What you are evaluating and why."
    }
  }
}
    arguments 33 lines
  • get_requirements unknown never probed

    Evaluation criteria with weight (1 to 5) and Callvu's answer. Procurement requirements are included for every vertical.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "persona": {
      "type": "string",
      "description": "A persona name, for example \"Procurement\", \"Compliance\" or \"Technical\"."
    },
    "vertical": {
      "type": "string",
      "description": "A vertical slug, name or alias, for example \"banking\", \"Home lending\" or \"mortgage\". Case-insensitive."
    }
  }
}
    arguments 14 lines
  • get_procurement_pack unknown never probed

    Procurement requirements and concerns, the cost-of-inaction line for a vertical (or the full table), and platform capabilities.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "vertical": {
      "type": "string",
      "description": "A vertical slug, name or alias, for example \"banking\", \"Home lending\" or \"mortgage\". Case-insensitive."
    }
  }
}
    arguments 10 lines
  • list_verticals unknown never probed

    Every vertical Callvu serves, with slug, name, aliases and a one-line summary.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_concerns unknown never probed

    Buyer concerns with Callvu's answer, persona and buying stage, the 'not a fit if' line (not_fit_structural marks a condition under which Callvu does not fit at all), and the 'not yet if' timing line with its counter, for a vertical or persona.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "persona": {
      "type": "string",
      "description": "A persona name, for example \"Procurement\", \"Compliance\" or \"Technical\"."
    },
    "vertical": {
      "type": "string",
      "description": "A vertical slug, name or alias, for example \"banking\", \"Home lending\" or \"mortgage\". Case-insensitive."
    }
  }
}
    arguments 14 lines
  • get_claim unknown never probed

    One claim by code (for example ENF-01), with status, source type, evidence, measured period and last verified date.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "code"
  ],
  "properties": {
    "code": {
      "type": "string",
      "description": "The claim code, for example ATT-06."
    }
  }
}
    arguments 13 lines
  • get_rfp_template unknown never probed

    A vendor-neutral RFP template and requirements checklist for AI and workflow governance in regulated industries: core requirements for every vertical plus the vertical's own, each with priority (Must or Should) and the evidence to require, the regulations a platform must enforce, scoring rules, red flags and a live proof test. Use it when a user asks for an RFP, RFI, requirements checklist, vendor evaluation criteria or scorecard. Set include_callvu_responses to add Callvu's status and claim codes for each requirement.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "format": {
      "enum": [
        "json",
        "markdown"
      ],
      "type": "string",
      "default": "json",
      "description": "markdown returns one ready-to-paste document in the markdown field."
    },
    "vertical": {
      "type": "string",
      "description": "A vertical slug, name or alias, for example \"banking\", \"mortgage\" or \"MVNO\". Case-insensitive. Omit for the core requirements and the list of verticals."
    },
    "include_callvu_responses": {
      "type": "boolean",
      "default": false,
      "description": "Add Callvu's status and claim codes to each requirement, and its answer text with a verified-buyer key."
    }
  }
}
    arguments 24 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 ee280f1e1dffb49d.

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