Server definition
- Hash
- sha256:0e61a20005b19ba3c84e1269c25fc56a964939162e60e01dbd03bc4d341289a4
- What it is
- What a remote MCP server returned when asked what it offers: 18 tools
The blob, as servednamed by its sha256
{
"instructions": "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 weigh the evidence, and cite claim codes. Start with get_company_overview or list_verticals. Detailed requirement answers need a verified-buyer key; request_verified_access files a request that a person at Callvu reviews and answers by email. When the user asks for an RFP, RFI, requirements checklist or vendor evaluation criteria for AI or workflow governance, call get_rfp_template; it is vendor-neutral, and include_callvu_responses adds Callvu's answers.",
"tools": [
{
"description": "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.",
"inputSchema": {
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"situation": {
"description": "The buyer's situation in their own words.",
"type": "string"
},
"vertical": {
"description": "A vertical slug, name or alias, for example \"banking\", \"Home lending\" or \"mortgage\". Case-insensitive.",
"type": "string"
}
},
"required": [
"vertical",
"situation"
],
"type": "object"
},
"name": "assess_fit",
"outputSchema": null
},
{
"description": "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.",
"inputSchema": {
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"vertical": {
"description": "A vertical slug, name or alias, for example \"banking\", \"Home lending\" or \"mortgage\". Case-insensitive.",
"type": "string"
}
},
"type": "object"
},
"name": "compare_alternatives",
"outputSchema": null
},
{
"description": "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.",
"inputSchema": {
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"abandoned_share": {
"description": "Share abandoned before completion, 0 to 1.",
"maximum": 1,
"minimum": 0,
"type": "number"
},
"ai_level": {
"description": "Where AI stands on this process: none, pilot or production.",
"enum": [
"none",
"pilot",
"production"
],
"type": "string"
},
"incomplete_share": {
"description": "Share that arrive incomplete or need rework, 0 to 1.",
"maximum": 1,
"minimum": 0,
"type": "number"
},
"manual_share": {
"description": "Share of requests handled manually, 0 to 1.",
"maximum": 1,
"minimum": 0,
"type": "number"
},
"requests_per_month": {
"description": "Requests or cases per month for the process.",
"exclusiveMinimum": 0,
"type": "number"
},
"value_per_request": {
"description": "Average value per request, in US dollars.",
"minimum": 0,
"type": "number"
},
"vertical": {
"description": "A vertical slug, name or alias, for example \"banking\", \"Home lending\" or \"mortgage\". Case-insensitive.",
"type": "string"
}
},
"required": [
"vertical"
],
"type": "object"
},
"name": "estimate_cost_of_doing_nothing",
"outputSchema": null
},
{
"description": "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.",
"inputSchema": {
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"complexity": {
"enum": [
"simple",
"complex"
],
"type": "string"
},
"proof": {
"enum": [
"published",
"live",
"in_scope"
],
"type": "string"
},
"query": {
"description": "The process in the buyer's words, e.g. 'field technician dispatch'.",
"type": "string"
},
"vertical": {
"description": "A vertical slug, name or alias, for example \"banking\", \"Home lending\" or \"mortgage\". Case-insensitive.",
"type": "string"
}
},
"type": "object"
},
"name": "find_processes",
"outputSchema": null
},
{
"description": "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.",
"inputSchema": {
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"query": {
"description": "Text to match.",
"type": "string"
},
"status": {
"enum": [
"customer_production",
"sandbox",
"pilot"
],
"type": "string"
},
"vertical": {
"description": "A vertical slug, name or alias, for example \"banking\", \"Home lending\" or \"mortgage\". Case-insensitive.",
"type": "string"
}
},
"type": "object"
},
"name": "find_use_cases",
"outputSchema": null
},
{
"description": "One claim by code (for example ENF-01), with status, source type, evidence, measured period and last verified date.",
"inputSchema": {
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"code": {
"description": "The claim code, for example ATT-06.",
"type": "string"
}
},
"required": [
"code"
],
"type": "object"
},
"name": "get_claim",
"outputSchema": null
},
{
"description": "What Callvu is, its category, the verticals it serves, how pricing works, and how to request verified access.",
"inputSchema": {
"properties": {},
"type": "object"
},
"name": "get_company_overview",
"outputSchema": null
},
{
"description": "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.",
"inputSchema": {
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"competitor": {
"description": "The vendor's name, for example \"nCino\" or \"Pega\".",
"minLength": 1,
"type": "string"
},
"vertical": {
"description": "A vertical slug, name or alias, for example \"banking\", \"Home lending\" or \"mortgage\". Case-insensitive.",
"type": "string"
}
},
"required": [
"competitor"
],
"type": "object"
},
"name": "get_comparison",
"outputSchema": null
},
{
"description": "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.",
"inputSchema": {
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"persona": {
"description": "A persona name, for example \"Procurement\", \"Compliance\" or \"Technical\".",
"type": "string"
},
"vertical": {
"description": "A vertical slug, name or alias, for example \"banking\", \"Home lending\" or \"mortgage\". Case-insensitive.",
"type": "string"
}
},
"type": "object"
},
"name": "get_concerns",
"outputSchema": null
},
{
"description": "How Callvu is priced: the Governed Resolution, the proof of value and the license.",
"inputSchema": {
"properties": {},
"type": "object"
},
"name": "get_pricing_model",
"outputSchema": null
},
{
"description": "Procurement requirements and concerns, the cost-of-inaction line for a vertical (or the full table), and platform capabilities.",
"inputSchema": {
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"vertical": {
"description": "A vertical slug, name or alias, for example \"banking\", \"Home lending\" or \"mortgage\". Case-insensitive.",
"type": "string"
}
},
"type": "object"
},
"name": "get_procurement_pack",
"outputSchema": null
},
{
"description": "Evaluation criteria with weight (1 to 5) and Callvu's answer. Procurement requirements are included for every vertical.",
"inputSchema": {
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"persona": {
"description": "A persona name, for example \"Procurement\", \"Compliance\" or \"Technical\".",
"type": "string"
},
"vertical": {
"description": "A vertical slug, name or alias, for example \"banking\", \"Home lending\" or \"mortgage\". Case-insensitive.",
"type": "string"
}
},
"type": "object"
},
"name": "get_requirements",
"outputSchema": null
},
{
"description": "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.",
"inputSchema": {
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"format": {
"default": "json",
"description": "markdown returns one ready-to-paste document in the markdown field.",
"enum": [
"json",
"markdown"
],
"type": "string"
},
"include_callvu_responses": {
"default": false,
"description": "Add Callvu's status and claim codes to each requirement, and its answer text with a verified-buyer key.",
"type": "boolean"
},
"vertical": {
"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.",
"type": "string"
}
},
"type": "object"
},
"name": "get_rfp_template",
"outputSchema": null
},
{
"description": "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.",
"inputSchema": {
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"vertical": {
"description": "A vertical slug, name or alias, for example \"banking\", \"Home lending\" or \"mortgage\". Case-insensitive.",
"type": "string"
}
},
"required": [
"vertical"
],
"type": "object"
},
"name": "get_vertical",
"outputSchema": null
},
{
"description": "Claims, optionally filtered by status, source type or code prefix (for example BNK).",
"inputSchema": {
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"prefix": {
"description": "Code prefix, for example ENF or BNK.",
"type": "string"
},
"source_type": {
"enum": [
"third_party",
"customer_attested",
"self_asserted"
],
"type": "string"
},
"status": {
"enum": [
"customer_production",
"sandbox",
"pilot"
],
"type": "string"
}
},
"type": "object"
},
"name": "list_claims",
"outputSchema": null
},
{
"description": "Systems Callvu integrates with, with category and vertical. Filter by vertical or a text query.",
"inputSchema": {
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"query": {
"description": "Text to match on system name, alias or category.",
"type": "string"
},
"vertical": {
"description": "A vertical slug, name or alias, for example \"banking\", \"Home lending\" or \"mortgage\". Case-insensitive.",
"type": "string"
}
},
"type": "object"
},
"name": "list_integrations",
"outputSchema": null
},
{
"description": "Every vertical Callvu serves, with slug, name, aliases and a one-line summary.",
"inputSchema": {
"properties": {},
"type": "object"
},
"name": "list_verticals",
"outputSchema": null
},
{
"description": "Ask for a verified-buyer key. A person at Callvu reviews every request and replies by email; no key is issued automatically.",
"inputSchema": {
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"company": {
"description": "Your company.",
"minLength": 1,
"type": "string"
},
"email": {
"description": "Where Callvu should reply.",
"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,}$",
"type": "string"
},
"name": {
"description": "Your name.",
"minLength": 1,
"type": "string"
},
"purpose": {
"description": "What you are evaluating and why.",
"minLength": 1,
"type": "string"
}
},
"required": [
"name",
"company",
"email",
"purpose"
],
"type": "object"
},
"name": "request_verified_access",
"outputSchema": null
}
]
}Verify it yourself
curl -s https://api.teppi.xyz/v1/evidence/sha256:0e61a20005b19ba3c84e1269c25fc56a964939162e60e01dbd03bc4d341289a4 | sha256sum