Alpaca Trading API integration for Model Context Protocol (MCP)
Nothing to run from here
Texas Insurance is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
8
tools declared
remote
at its publisher
—
calls last 7d
What it does
Auto insurance prices for Texas drivers, from rates the state publishes.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http texas-insurance-mcp https://texasautoquotes.com/mcp
# 2 — ask your agent for something these tools do
# check_eligibility, get_quotes, pull_requests and 5 more
Texas Insurance costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
TEAll 2 servers
texasautoquotes2 servers
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http texas-insurance-mcp https://texasautoquotes.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Check whether we can return quotes for a state before any personal details are collected. Call this first. Returns the states we are licensed in, what we can do in each, and how many licensed agents can take a request there.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| state | string | no | Two-letter US state code, e.g. NV |
| product | string | yes | — |
Return indicative auto insurance prices from multiple carriers, where this entity is licensed to show them. Takes rating facts only — no name, phone, email, SSN or licence number is required for an indicative price. Where we are not licensed to show prices, the request is still registered and a quote_id returned so licensed agents can quote it. If facts are missing the server asks for exactly what
| Parameter | Type | Required | Notes |
|---|---|---|---|
| garaging_zip | string | yes | Five-digit ZIP where the vehicle is kept |
| date_of_birth | string | yes | — |
| years_licensed | integer | no | — |
| vehicle_year | integer | yes | — |
| vehicle_make_model | string | yes | — |
| annual_mileage | integer | no | — |
| violations_3yr | integer | no | — |
| coverage | string | yes | — |
| prior_continuous | boolean | no | — |
| state | string | no | Optional; derived from the ZIP when absent |
Drain the queue of pool records routed to you. Requires your buyer key. Metered buyers receive an x402 payment requirement (status 402, accepts[]) until a payment is supplied. Records are projected to the scope the consumer granted — never wider.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| buyer_key | string | yes | — |
| payment | string | no | x402 X-PAYMENT payload |
| credential | string | no | MPP credential (the base64url JSON that would follow "Authorization: Payment") |
| mandate | string | no | AP2 Payment Mandate |
What happens to anything you send us: who receives it, for what purpose, how long it is kept, how your human revokes it, and the exact consent wording to present before request_agent_contact. Machine readable so you can evaluate the exchange before making it.
No parameter schema on file.
Connect the consumer with licensed insurance agents who can quote firm and bind. Needs the quote_id from get_quotes, the consumer's name and phone, and the consumer's explicit consent to be contacted — granted by the human, presented by you, or confirmed by the human directly at the consent URL the elicitation returns. Under scope contact_consumer up to 4 licensed agents receive the request and co
| Parameter | Type | Required | Notes |
|---|---|---|---|
| quote_id | string | yes | From get_quotes |
| full_name | string | yes | — |
| phone_number | string | yes | US mobile or landline |
| email_address | string | no | — |
| preferred_channel | string | no | — |
| best_time | string | no | — |
| street_address | string | no | Optional. Lets a licensed agent answer firm. |
| verify_token | string | no | Optional. From POST /v1/verify/check after the consumer enters the code texted to them. A verified number sells at the verified price and is contacted first. |
| consent | object | yes | — |
For an AI working for a licensed insurance agency: register the agency to receive consented consumer requests in its states. Needs the agency name, the producer NPN (National Producer Number) and its state, the states it is appointed in, the licensed contact's name, email and mobile, and how leads should arrive (email, webhook, or pull by key). The licensed contact confirms by a link sent to their
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agency_name | string | yes | — |
| npn | string | yes | NPN (National Producer Number). Your NPN is on your licence and at nipr.com. Digits only. |
| npn_state | string | yes | Two-letter state that issued the licence |
| states | array | no | Two-letter states the agency is appointed in; defaults to npn_state |
| contact_name | string | yes | The licensed contact, who confirms by email |
| contact_email | string | yes | — |
| contact_phone | string | yes | US mobile |
| rail | string | no | How leads arrive: email, an https webhook (HMAC-signed), or pull by key over MCP/REST |
| webhook_url | string | no | — |
| website | string | no | — |
| verify_token | string | no | Optional: from POST /v1/verify/check after the contact enters the code texted to them |
| handoff | boolean | no | Optional standing order. When true, and the licence record places this agency in a city we publish, the agency becomes the one agency a consumer in that city is handed to by name: it is named in the c |
The qualified demand dataset contains only requests backed by a cryptographically or IP-verified agent, or a phone-verified consumer outcome. User-agent claims, legacy rows, probes and impostors are quarantined and unavailable for sale. Qualified rows are de-identified (age band, ZIP3, vehicle, coverage, mileage band, prices shown, door, verified agent identity and outcome). Never a name, phone, e
| Parameter | Type | Required | Notes |
|---|---|---|---|
| state | string | no | — |
| since | string | no | — |
| until | string | no | — |
| door | string | no | — |
| vendor | string | no | — |
| limit | integer | no | — |
| offset | integer | no | — |
| buyer_key | string | no | A prepaid buyer key |
| payment | string | no | x402 X-PAYMENT payload |
| credential | string | no | MPP credential |
| mandate | string | no | AP2 Payment Mandate |
For a registered agency: its states, rail, terms, founding period, queued and delivered counts, credit balance, and whether the licence was verified. Requires the buyer key issued at confirmation.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| buyer_key | string | yes | Issued to the licensed contact at confirmation |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Texas Insurance or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.0.0 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 1 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest71eee62cf910682eb8488303294090d6a66383dd8ed19f595056518314aea72a
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| check_eligibility | no tags | |
| get_quotes | no tags | |
| pull_requests | state-write | state-write: declares readOnlyHint: false |
| data_use_terms | no tags | |
| request_agent_contact | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| register_agency | external-sink | external-sink: parameter "webhook", declares readOnlyHint: false, openWorldHint: true |
| market_data | no tags | |
| agency_status | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest71eee62cf910682e
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Texas Insurance can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.