Jerry shops car, motorcycle, home, condo, townhouse and renters insurance across many insurers. You act for the customer, who is already signed in: never ask for an insuredId or userId. This service covers quotes and final prices. Buying a policy isn't available here; it continues in the Jerry app.
Do the work for the customer. Fill in the application from what you already have, in this order, and ask the customer only for what's left:
1. What the customer shares. Use what the customer tells you in this conversation, and any document they paste or attach, such as a declarations page or a renewal notice. These can show the current insurer, premium, renewal date, vehicles and VINs, drivers and coverage, whether a car is financed or leased, and whether they own their home. You can mention once that sharing a declarations page saves them typing. Tell the customer what you found in a document, and get their permission before sending it to Jerry. Pass their reply as permission and list the sources.
2. Jerry's data. Jerry fills in what it can once it has the customer's name, date of birth and address, so get these three early. Until they're saved, the status lists only the next of them to ask: the name and date of birth first, then the address. Ask for any you don't have as an ordinary part of getting quotes, one at a time ("To get your quotes I need a few details. First, what's your date of birth?"), not as a separate step. Each write and jerry_get_status return suggested: what Jerry found that the application doesn't have yet. It can show up only on the next write or status. When suggested.addresses is there and you don't have the address, offer it before you ask: for one address, ask "Is this still your home address: ...? If not, what is it?"; for several, list them numbered and add "or tell me a different one". Save the confirmed or given address as customer.address with jerry_update_application. When suggested has drivers or vehicles, show them and ask whether they'
Discoverability
0/6 passed0 of 6 passed0/100
Client listings and public setup information.
mcp.json or server-card.json
Either mcp.json or an MCP Server Card declaring this endpoint passes.
No matching mcp.json manifest or MCP Server Card was found at the checked URLs.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description85/100
Read the name, email and phone on the customer's Jerry account, and whether the phone is verified. It doesn't verify an email or change any insurance information.
The description explains the capability, when to use it, and what to expect.
Inputs100/100
This tool declares no inputs, so argument descriptions are not needed.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description93/100
Start shopping for the insurance products the customer asked for. If a shopping intent for exactly these products is already open, it resumes that one. Pass the main facts you already know in application, so the status asks only for the rest. application takes the main fields only: send any other fact with jerry_update_application right after. Returns the status, with rejected and clarify. When a fact comes from anything other than the customer, sources says where, and permission holds the customer's reply allowing it.
Describe the returned information so the agent knows whether it will answer the request.
Inputs57/100
40 of 61 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
sources
Where these facts come from; defaults to ['customer'].
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
permission › customerReply
The customer's exact reply.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
policyTypes
Products to shop for.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
application › customer › name
Full legal name.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
application › customer › dateOfBirth
YYYY-MM-DD.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
application › customer › address › text
The whole address as one line, e.g. "123 Main St Apt 4, Austin TX 78701".
Clear enough to supply this argument.
application › customer › address › street
Not provided
Missing description. Explain what this value means and how to supply it.
application › customer › address › unit
Apartment or unit.
Clear enough to supply this argument.
application › customer › address › city
Not provided
Missing description. Explain what this value means and how to supply it.
application › customer › address › state
Two-letter state code.
Clear enough to supply this argument.
application › customer › address › zip
Five-digit ZIP code.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
application › customer › address › confirmation
From an address_unverified clarify, once the customer confirms that address.
Clear enough to supply this argument.
application › customer › email
Not provided
Missing description. Explain what this value means and how to supply it.
application › history › currentlyInsured
Has auto insurance now.
Clear enough to supply this argument.
application › history › insuredFor
How long continuously insured.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
application › history › notInsuredReason
Not provided
Missing description. Explain what this value means and how to supply it.
application › history › currentCarrier
Current auto insurer name, e.g. "GEICO".
Clear enough to supply this argument.
application › drivers › items › id
Omit to add an item. A suggested: id adds what Jerry found; fields sent with it win.
Clear enough to supply this argument.
application › drivers › items › included
Put on the quote (true) or leave off (false).
Clear enough to supply this argument.
application › drivers › items › name
Not provided
Missing description. Explain what this value means and how to supply it.
application › drivers › items › dateOfBirth
YYYY-MM-DD.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
application › drivers › items › relationship
Not provided
Missing description. Explain what this value means and how to supply it.
application › drivers › items › gender
Not provided
Missing description. Explain what this value means and how to supply it.
application › drivers › items › maritalStatus
Not provided
Missing description. Explain what this value means and how to supply it.
application › drivers › items › licenseState
Two-letter state code.
Clear enough to supply this argument.
application › drivers › items › ageFirstLicensed
Not provided
Missing description. Explain what this value means and how to supply it.
application › drivers › items › occupation
Job in plain words, e.g. "nurse", or a candidate value from clarify.
Clear enough to supply this argument.
application › vehicles › items › id
Omit to add an item. A suggested: id adds what Jerry found; fields sent with it win.
Clear enough to supply this argument.
application › vehicles › items › included
Put on the quote (true) or leave off (false).
Clear enough to supply this argument.
application › vehicles › items › vin
17-character VIN; sets year, make and model.
Clear enough to supply this argument.
application › vehicles › items › licensePlate
With licensePlateState; sets year, make and model.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description86/100
Save application facts the customer gave, in their own words. Every field is optional and merges into what's saved, so send only facts that are new or changed.
- Items with an id update that driver, car or home; items without one are added. included puts an item on the quote or leaves it off.
- Add a car by vin, by licensePlate and licensePlateState, or by year, make and model. Send year, make and model only when there's no VIN or plate, since those set them. A final price needs the VIN.
- Answer any other requirement in answers, by its path. A fact that has its own field here comes back rejected as typed_field if it's sent in answers.
- coverage and history.currentMonthlyPremiumCents are optional and never block quotes. Send them only when the customer asks for a coverage level or specific coverages, or says what they pay now.
- Drivers and cars Jerry found are in the status's suggested list, each with an id that starts with suggested:. Once the customer confirms one, send that id in drivers or vehicles with included: true.
Returns the status, with suggested. rejected lists values to correct with the customer, and clarify lists values to choose from. The rest of the write is saved either way.
The description explains the capability, when to use it, and what to expect.
Inputs46/100
69 of 139 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
intentId
The shopping intent id returned by an earlier shopping tool.
Clear enough to supply this argument.
sources
Where these facts come from; defaults to ['customer'].
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
permission › customerReply
The customer's exact reply.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
application › customer › name
Full legal name.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
application › customer › dateOfBirth
YYYY-MM-DD.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
application › customer › address › text
The whole address as one line, e.g. "123 Main St Apt 4, Austin TX 78701".
Clear enough to supply this argument.
application › customer › address › street
Not provided
Missing description. Explain what this value means and how to supply it.
application › customer › address › unit
Apartment or unit.
Clear enough to supply this argument.
application › customer › address › city
Not provided
Missing description. Explain what this value means and how to supply it.
application › customer › address › state
Two-letter state code.
Clear enough to supply this argument.
application › customer › address › zip
Five-digit ZIP code.
Clear enough to supply this argument.
application › customer › address › confirmation
From an address_unverified clarify, once the customer confirms that address.
Clear enough to supply this argument.
application › customer › previousAddress › text
The whole address as one line, e.g. "123 Main St Apt 4, Austin TX 78701".
Clear enough to supply this argument.
application › customer › previousAddress › street
Not provided
Missing description. Explain what this value means and how to supply it.
application › customer › previousAddress › unit
Apartment or unit.
Clear enough to supply this argument.
application › customer › previousAddress › city
Not provided
Missing description. Explain what this value means and how to supply it.
Missing description. Explain what this value means and how to supply it.
application › homes › items › id
Omit to add an item. A suggested: id adds what Jerry found; fields sent with it win.
Clear enough to supply this argument.
application › homes › items › included
Put on the quote (true) or leave off (false).
Clear enough to supply this argument.
application › homes › items › address › text
The whole address as one line, e.g. "123 Main St Apt 4, Austin TX 78701".
Clear enough to supply this argument.
application › homes › items › address › street
Not provided
Missing description. Explain what this value means and how to supply it.
application › homes › items › address › unit
Apartment or unit.
Clear enough to supply this argument.
application › homes › items › address › city
Not provided
Missing description. Explain what this value means and how to supply it.
application › homes › items › address › state
Two-letter state code.
Clear enough to supply this argument.
application › homes › items › address › zip
Five-digit ZIP code.
Clear enough to supply this argument.
application › homes › items › address › confirmation
From an address_unverified clarify, once the customer confirms that address.
Clear enough to supply this argument.
application › homes › items › occupancy
Not provided
Missing description. Explain what this value means and how to supply it.
application › homes › items › isClosing
Still closing on the purchase.
Clear enough to supply this argument.
application › homes › items › purchaseDate
YYYY-MM-DD.
Clear enough to supply this argument.
application › homes › items › hasMortgage
Not provided
Missing description. Explain what this value means and how to supply it.
application › homes › items › isInsured
Not provided
Missing description. Explain what this value means and how to supply it.
application › homes › items › notInsuredReason
Not provided
Missing description. Explain what this value means and how to supply it.
application › homes › items › yearBuilt
Not provided
Missing description. Explain what this value means and how to supply it.
application › homes › items › squareFeet
Not provided
Missing description. Explain what this value means and how to supply it.
application › homes › items › stories
Use the requirement's options.
Clear enough to supply this argument.
application › homes › items › dwellingType
Use the requirement's options.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
application › homes › items › roofMaterial
Use the requirement's options.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
application › homes › items › roofUpdatedYear
Not provided
Missing description. Explain what this value means and how to supply it.
application › homes › items › plumbingTypes
Empty when none apply.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
application › homes › items › wiringTypes
Empty when none apply.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
application › homes › items › hasDogs
Not provided
Missing description. Explain what this value means and how to supply it.
application › homes › items › dogBreeds
Listed breeds only; empty when none.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
application › homes › items › hasDogBiteHistory
Not provided
Missing description. Explain what this value means and how to supply it.
application › homes › items › hasSwimmingPool
Not provided
Missing description. Explain what this value means and how to supply it.
application › homes › items › swimmingPoolType
Not provided
Missing description. Explain what this value means and how to supply it.
application › homes › items › isSwimmingPoolFenced
Not provided
Missing description. Explain what this value means and how to supply it.
application › homes › items › hasExoticOrFarmAnimals
Not provided
Missing description. Explain what this value means and how to supply it.
application › homes › items › hasTrampoline
Not provided
Missing description. Explain what this value means and how to supply it.
application › homes › items › hasBusiness
Not provided
Missing description. Explain what this value means and how to supply it.
application › homes › items › hasDaycare
Not provided
Missing description. Explain what this value means and how to supply it.
application › homes › items › hasBurglarAlarm
Not provided
Missing description. Explain what this value means and how to supply it.
application › homes › items › hasFireAlarm
Not provided
Missing description. Explain what this value means and how to supply it.
application › homes › items › hasSprinkler
Not provided
Missing description. Explain what this value means and how to supply it.
application › homes › items › inGatedCommunity
Not provided
Missing description. Explain what this value means and how to supply it.
application › startDates › car
YYYY-MM-DD.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
application › startDates › home
YYYY-MM-DD.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
application › startDates › motorcycle
YYYY-MM-DD.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
application › coverage › plan
Basic plan: state-minimum liability; Basic + full coverage: adds $1,000 comprehensive and collision; Standard plan: 50/100, $1,000 deductibles, towing, rental; Preferred plan: 100/300, $500 deductibles; Custom plan: the values under items and perAssetItems. Custom values start from the pre-made plan sent here, else the round's.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
application › coverage › items › items › name
Not provided
Missing description. Explain what this value means and how to supply it.
application › coverage › items › items › value
Not provided
Missing description. Explain what this value means and how to supply it.
application › coverage › items › items › type
Not provided
Missing description. Explain what this value means and how to supply it.
application › coverage › perAssetItems › items › id
A car's id.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description67/100
Request quotes. Every request needs the confirmation from the status: show its summary, get the customer's explicit yes, then pass its token and their exact reply. Nothing is requested unless requested comes back true; reason says why not, and status is the intent after the call. On stale_confirmation the facts changed: show the new confirmation and ask again.
Describe the concrete operation and its scope instead of restating the tool name.
Inputs82/100
Input documentation gives an agent enough context to populate the arguments.
intentId
The shopping intent id returned by an earlier shopping tool.
Clear enough to supply this argument.
confirmation › token
The status confirmation's token; a changed fact makes it stale.
Clear enough to supply this argument.
confirmation › customerReply
The customer's exact reply.
Clear enough to supply this argument.
idempotencyKey
Unique key for safely retrying this customer action
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "jerry_request_quotes",
"title": "Request quotes",
"description": "Request quotes. Every request needs the confirmation from the status: show its summary, get the customer's explicit yes, then pass its token and their exact reply. Nothing is requested unless requested comes back true; reason says why not, and status is the intent after the call. On stale_confirmation the facts changed: show the new confirmation and ask again.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"intentId",
"confirmation",
"idempotencyKey"
],
"properties": {
"intentId": {
"type": "string",
"description": "The shopping intent id returned by an earlier shopping tool."
},
"confirmation": {
"type": "object",
"required": [
"token",
"customerReply"
],
"properties": {
"token": {
"type": "string",
"description": "The status confirmation's token; a changed fact makes it stale."
},
"customerReply": {
"type": "string",
"maxLength": 1000,
"description": "The customer's exact reply."
}
},
"additionalProperties": true
},
"idempotencyKey": {
"type": "string",
"maxLength": 200,
"minLength": 1,
"description": "Unique key for safely retrying this customer action"
}
},
"additionalProperties": false
},
"annotations": {
"title": "Request quotes",
"readOnlyHint": false,
"openWorldHint": true,
"idempotentHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description93/100
Get the final price of the quote the customer chose. Call it first with bundleId only: that selects the quote and returns the status, which may list what the final price still needs, then a confirmation. After the customer says yes to that confirmation, call again with its token and the customer's exact reply. Nothing is requested unless requested comes back true.
Describe the returned information so the agent knows whether it will answer the request.
Inputs83/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
intentId
The shopping intent id returned by an earlier shopping tool.
Clear enough to supply this argument.
bundleId
The bundleId of the chosen quote.
Clear enough to supply this argument.
confirmation › token
The status confirmation's token; a changed fact makes it stale.
Clear enough to supply this argument.
confirmation › customerReply
The customer's exact reply.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
idempotencyKey
Unique key for safely retrying this customer action
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "jerry_request_final_price",
"title": "Request final price",
"description": "Get the final price of the quote the customer chose. Call it first with bundleId only: that selects the quote and returns the status, which may list what the final price still needs, then a confirmation. After the customer says yes to that confirmation, call again with its token and the customer's exact reply. Nothing is requested unless requested comes back true.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"intentId",
"bundleId",
"idempotencyKey"
],
"properties": {
"bundleId": {
"type": "string",
"description": "The bundleId of the chosen quote."
},
"intentId": {
"type": "string",
"description": "The shopping intent id returned by an earlier shopping tool."
},
"confirmation": {
"type": "object",
"required": [
"token",
"customerReply"
],
"properties": {
"token": {
"type": "string",
"description": "The status confirmation's token; a changed fact makes it stale."
},
"customerReply": {
"type": "string",
"maxLength": 1000,
"description": "The customer's exact reply."
}
},
"description": "Omit on the first call, which selects the quote and returns the confirmation to show.",
"additionalProperties": true
},
"idempotencyKey": {
"type": "string",
"maxLength": 200,
"minLength": 1,
"description": "Unique key for safely retrying this customer action"
}
},
"additionalProperties": false
},
"annotations": {
"title": "Request final price",
"readOnlyHint": false,
"openWorldHint": true,
"idempotentHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description98/100
Wait for quotes or a final price after requesting them. Returns as soon as they're ready, or after timeoutSeconds with the status so far; call again while they're still running. When quotes are ready, it returns the quote list too. A final price is ready once it's resolved. If a Jerry agent takes it over (manual) or it's taking longer than usual (delayed), the wait stops with that reason, and the status's nextStep says what happens next. Calling again on a delayed price keeps waiting.
The description explains the capability, when to use it, and what to expect.
Inputs92/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
intentId
The shopping intent id returned by an earlier shopping tool.
Clear enough to supply this argument.
for
quotes after jerry_request_quotes; final_price after jerry_request_final_price requested it.
Clear enough to supply this argument.
timeoutSeconds
Longest time to wait, in seconds; default 20, at most 20.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "jerry_wait",
"title": "Wait for results",
"description": "Wait for quotes or a final price after requesting them. Returns as soon as they're ready, or after timeoutSeconds with the status so far; call again while they're still running. When quotes are ready, it returns the quote list too. A final price is ready once it's resolved. If a Jerry agent takes it over (manual) or it's taking longer than usual (delayed), the wait stops with that reason, and the status's nextStep says what happens next. Calling again on a delayed price keeps waiting.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"intentId",
"for"
],
"properties": {
"for": {
"enum": [
"quotes",
"final_price"
],
"type": "string",
"description": "quotes after jerry_request_quotes; final_price after jerry_request_final_price requested it."
},
"intentId": {
"type": "string",
"minLength": 1,
"description": "The shopping intent id returned by an earlier shopping tool."
},
"timeoutSeconds": {
"type": "integer",
"maximum": 20,
"minimum": 1,
"description": "Longest time to wait, in seconds; default 20, at most 20."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Wait for results",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description94/100
Read where the customer's insurance shopping stands: the stage, what the current goal still needs (by application path), a summary of the application, what Jerry found that isn't on the application yet (suggested) and, when a request is ready, the confirmation to show. It doesn't change anything.
The description explains the capability, when to use it, and what to expect.
Inputs96/100
Input documentation gives an agent enough context to populate the arguments.
intentId
The shopping intent id returned by an earlier shopping tool. Omit it to read the customer's most recent open intent.
Clear enough to supply this argument.
full
Include every typed application fact by application path, with sensitive values masked.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "jerry_get_status",
"title": "Shopping status",
"description": "Read where the customer's insurance shopping stands: the stage, what the current goal still needs (by application path), a summary of the application, what Jerry found that isn't on the application yet (suggested) and, when a request is ready, the confirmation to show. It doesn't change anything.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"full": {
"type": "boolean",
"description": "Include every typed application fact by application path, with sensitive values masked."
},
"intentId": {
"type": "string",
"description": "The shopping intent id returned by an earlier shopping tool. Omit it to read the customer's most recent open intent."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Shopping status",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description95/100
List every quote for a shopping intent, cheapest first by monthly price (in USD cents); each policy has a coverageSummary. Pass up to 4 bundleIds to also get their coverages, discounts and payment plans, for example to compare them. Prices are estimates until priceStatus is final. Declined quotes are left out and counted in declinedCount. It doesn't request quotes.
The description explains the capability, when to use it, and what to expect.
Inputs95/100
Input documentation gives an agent enough context to populate the arguments.
intentId
The shopping intent id returned by an earlier shopping tool.
Clear enough to supply this argument.
bundleIds
Up to 4 bundle ids to return with coverages, discounts and payment plans. Omit to list every quote.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "jerry_get_quotes",
"title": "View quotes",
"description": "List every quote for a shopping intent, cheapest first by monthly price (in USD cents); each policy has a coverageSummary. Pass up to 4 bundleIds to also get their coverages, discounts and payment plans, for example to compare them. Prices are estimates until priceStatus is final. Declined quotes are left out and counted in declinedCount. It doesn't request quotes.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"intentId"
],
"properties": {
"intentId": {
"type": "string",
"description": "The shopping intent id returned by an earlier shopping tool."
},
"bundleIds": {
"type": "array",
"items": {
"type": "string"
},
"description": "Up to 4 bundle ids to return with coverages, discounts and payment plans. Omit to list every quote."
}
},
"additionalProperties": false
},
"annotations": {
"title": "View quotes",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}
Loading score analytics…
Put your MCP to the test
A few tasks worth trying with this server, chosen from its reviewed tools. These have not been run.
01Account detailsRead the name, email and phone on the customer's Jerry account, and whether the phone is verified.
02Shopping statusRead where the customer's insurance shopping stands: the stage, what the current goal still needs (by application path), a summary of the application, what J…
03View quotesList every quote for a shopping intent, cheapest first by monthly price (in USD cents); each policy has a coverageSummary.
04Wait for resultsWait for quotes or a final price after requesting them.
Want to run these tasks against your MCP server with us?
agent-mcp setup, tools, quality score, publishing readiness, and alternatives.
How do I add agent-mcp to Claude, ChatGPT, or Cursor?
Add agent-mcp to Claude, ChatGPT, or Cursor by connecting its remote MCP URL in each client's MCP settings. In Claude, add a custom connector. In ChatGPT, add an MCP app. In Cursor, add an MCP server under Settings. The MCP URL is https://mcp.jerry.ai/mcp.
Is agent-mcp MCP ready for ChatGPT and Claude?
As of November 7, 2026, agent-mcp scores 96/100 on Manufact's MCP publishing checklist. The scan meets ChatGPT publishing checks and meets Claude publishing checks. Passing these checks does not guarantee marketplace approval.
How clear is agent-mcp's MCP tool documentation?
As of November 7, 2026, agent-mcp scores 82/100 in Manufact's review of tool titles, descriptions, input and output schemas, and behavior annotations. The review covers 8 of 8 discovered tools. The quality score measures documentation clarity; runtime behavior and marketplace readiness require separate checks.
What are the best alternatives to agent-mcp?
As of November 8, 2026, alternatives to agent-mcp in financial-services on the Manufact MCP leaderboard include paidfor: x402 seller reliability, CoinGecko, Coverage Cat Insurance, aiwyn, and Netzo.
How can agent-mcp improve its MCP documentation?
jerry_update_application is the lowest-scoring reviewed tool at 71/100. No output schema is declared. Add one for structured results so clients can interpret returned fields. Open its review for feedback and a copyable fix prompt, then rerun the documentation review after updating your tool metadata.
Not your MCP?
Review any public or OAuth MCP server for protocol compatibility, tool documentation, and ChatGPT and Claude publishing readiness. No account required.
Cursor
Grok Bot
Grok
Muse